game-design-lenseslisted

# Game Design Lenses Use the Lens cards as questions that expose assumptions, conflicts, and opportunities in a design. Select lenses because they illuminate the current design problem; do not treat all 116 as a mandatory checklist. The bundled references are self-contained. They do not require the source ebook or an extraction tool. ## Workflow 1. Identify the design object: the whole game, a player experience, one mechanic, a level, an interface, a story beat, a social structure, or a production decision. 2. State the decision or uncertainty to examine. Gather any existing GDD, prototype evidence, playtest observations, constraints, and intended player experience before asking questions already answered by those materials. 3. Route through the category table below. Read the complete card for each selected Lens before applying it. 4. Start with three to seven lenses that examine the problem from different angles. Add another category only when the first pass exposes a cross-domain dependency. 5. Answer each Lens from concrete design evidence. Distinguish known behavior, assumptions, and unanswered questions. 6. Synthesize the answers into design tensions, decisions, and the smallest useful prototype or playtest experiment. For a whole-game audit, work through categories in stages and summarize each stage before continuing. Avoid presenting 116 disconnected answers at once. ## Reference routing Read [references/index.md](references/index.md) when searching by Lens name