Game Design One-Page Design Doc

Create a one-page game design document that is readable, decision-useful, and visually polished — exportable as a PDF that looks like a real product.

Use this skill when the user wants a compact game design summary rather than a bloated GDD. The output is designed to be passed around in meetings, dropped in Slack, or emailed to publishers without embarrassment.

Read references/family-conventions.md when you want the shared style and prioritization rules for this game-design skill family. Read references/source-notes.md when you want the distilled takeaways from the reference template and the GDC talk overview.

Core principle

A one-page design doc is not a small bad GDD. It is a compressed communication tool.

It should:

• state what the game is
• state why it is interesting
• state what feeling or fantasy it is chasing
• state the core features and interaction model
• state enough production framing to make it actionable