# Inspiration Page Template Use this exact structure for every game page in `/src/inspiration/`. ## File Naming `src/inspiration/.md` Example: `loom.md`, `beneath-a-steel-sky.md`, `day-of-the-tentacle.md` --- ## Template Structure ```markdown # () [2-3 sentence intro summarizing game, unique mechanics, and why its puzzles matter. Include first citation if applicable.] ## At a Glance | | | |---|---| | **Release Year** | | | **Developer** | | | **Core Mechanic** | | | **What players found enjoyable** | "" — [brief context] []. Additional playthrough notes: "" [] | ![Game overview screenshot — ](./-overview.png) --- ## Puzzle 1: ### Problem [2-3 sentences explaining what must be accomplished. If puzzle involves a riddle or lengthy dialogue, format as blockquote:] > "Exact text from game" [Optional citation for setup details] ![](./-puzzle1.png) ### What Makes It Rewarding [2-3 sentences on mechanical design choice that creates satisfaction. Include direct quote from walkthrough author about the puzzle experience when available:] "" [] [Continue with mechanical analysis — why this isn't trial-and-error, how information was fairly conveyed, etc.] ### Solution [1 sentence on outcome achieved] ### Steps 1. [Specific, mechanical action] 2. [Specific, mechanical action] 3. [Specific, mechanical action] 4. [Continued as needed...] 5. [Final action that completes puzzle] ### Screenshots [](../puzzles/.md) — [1 sentence explicitly connecting this example to the core mechanic of the pattern type, distinguishing from similar types]. --- ## Puzzle 2: ### Problem [same structure as Puzzle 1] ![](./-puzzle2.png) ### What Makes It Rewarding [same structure as Puzzle 1, with direct quote] ### Solution [same structure as Puzzle 1] ### Steps [n numbered specific actions] [](../path/to/pattern.md) — [connection to pattern mechanic]. --- ## Puzzle 3: ### Problem [same structure as Puzzle 1] ![](./-puzzle3.png) ### What Makes It Rewarding [same structure as Puzzle 1, with direct quote] ### Solution [same structure as Puzzle 1] ### Steps [n numbered specific actions] [](../path/to/pattern.md) — [connection to pattern mechanic]. --- ## Other Puzzles | Name | Problem & Solution | Pattern Type | |------|-------------------|--------------| | | [<15-word description>; include inline quote citation like `<"text" >` if memorable] | [](../path/pattern.md) | | | [Description with citation if needed] | [](../path/pattern.md) | | | [Description with citation] | [](../path/pattern.md) | | | [Description] | [](../path/pattern.md) | | | [Description with citation] | [](../path/pattern.md) | | | [Continue to ~8 entries total, or as many notable puzzles as exist] | [](../path/pattern.md) | --- ### References [] Full Author Name, Source Title (Year). URL [] Full Author Name, Source Title (Year). URL [] Full Author Name, Source Title (Year). URL ``` --- ## Word Count Target **~1,000 words total**, broken down as: - Introduction + At a Glance: ~150 words - Each featured puzzle: ~250 words × 3 = ~750 words - Other Puzzles table + References: ~150 words --- ## Critical Requirements Checklist Before committing: - [ ] Exactly 3 featured puzzles with full Problem/Rewarding/Solution/Steps sections - [ ] One screenshot placeholder per puzzle with specific alt text hint describing what to capture - [ ] At least one direct quote formatted as blockquote or inline in each "What Makes It Rewarding" section - [ ] At minimum one direct quote in "What players found enjoyable" field of At a Glance table - [ ] All Pattern Type links point to existing files (verify with `ls src/puzzles/`) - [ ] Filename matches kebab-case of game name - [ ] References section includes full URLs for all cited walkthroughs - [ ] Citation keys match between in-text citations and References section