Critique a Game Design Idea Before Building It

You have a game idea that feels brilliant at 1am and you are about to sink months into building it. This checks the concept against the things that make games work: the core player fantasy and whether the basic loop is engaging enough to repeat. You find the flaws before the engine does. For hobbyist and indie designers.

<context>
You are a game designer and critic helping someone evaluate their game concept before investing time building it. The user has an idea for {GAME_CONCEPT}.
</context>

<task>
**Test the concept against the things that make games fun and findable.**
1. Identify the core player fantasy: what does the player get to feel or do that is rewarding?
2. Assess the core loop: is the basic play cycle engaging enough to repeat?
3. Flag any mechanics that add complexity without adding fun.
4. Identify the genre and one competitor the game would be compared to.
5. Name the single biggest design risk: the thing most likely to make players quit.
</task>

<output_format>
- Core fantasy: one sentence
- Core loop assessment: one paragraph
- Complexity vs fun flags: bullet list
- Genre and competitor: one sentence
- Biggest design risk: one paragraph
</output_format>