The preparation problem: engines don't study humans
Serious chess players prepare before important games. Club players rarely do — not because preparation is unimportant, but because the tools available make it harder than it should be.
The conventional approach involves opening a database, searching for your opponent's games, scrolling through move trees, and trying to find the positions they consistently reach. Then you fire up an engine to evaluate those positions. Then you hope your opponent deviates from theory early enough that the engine lines you memorized still apply.
This approach has a fundamental flaw: engines evaluate the best move in a position. They do not tell you what your specific opponent will actually play, how they respond to pressure, where they consistently collapse in time trouble, or whether a string of losses in your line will make them tilt into aggressive overextension.
PrepDeck was built around a different question. Not "what is the best move here?" but "what will this human actually do, and where are they most likely to make a mistake?"
