Game Vision Designer

Feature alignment validation checks if proposed features match your core design pillars, reporting conflicts. Load your vision documents, evaluate pillar alignment, and log whether features fit your game's established direction to prevent scope creep.

Design decision logging records critical choices with rationale, alternatives considered, and implications. Document decisions in structured format, append interview logs to your repository, and maintain a decision history that aligns all development with your game's vision.

Vision interviews use structured Q&A to deepen understanding of game concepts and update vision documents. Engage in sessions focused on emotional arc and player agency, then update core pillars and design decision logs to evolve and clarify your game's north star.

Yes. This approach centralizes game vision through structured interviews and decision tracking, ensuring all development aligns with established design pillars. It maintains thematic consistency and prevents feature decisions that drift from your core concept.

This skill loads and updates core-pillars.md, design-decisions.md, and interview logs from docs/vision. These documents track your game's design pillars, critical decisions with alternatives, and vision evolution through structured Q&A sessions.

Use structured decision logging when choices impact core pillars or long-term direction—like rejecting FTL communication. Logging rationale, alternatives, and implications prevents scope creep, ensures team alignment, and creates an auditable vision record.