📦 Game Design One-Page Design Doc — 游戏设计单页设计文档

Game De签名 One-Page De签名 Doc

创建 a one-page game de签名 document that is readable, decision-useful, and visually polished — 导出able as a PDF that looks like a real product.

Use this 技能 when the user wants a compact game de签名 summary rather than a bloated GDD. The 输出 is de签名ed to be passed around in meetings, dropped in Slack, or emAIled to publishers without embarrassment.

Read references/family-conventions.md when you want the 分享d style and prioritization rules for this game-de签名 技能 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 de签名 doc is not a small bad GDD. It is a 压缩ed communication 工具.

It should:

状态 what the game is 状态 why it is interesting 状态 what feeling or fantasy it is chasing 状态 the core features and interaction 模型 状态 enough production framing to make it actionable

It should not:

try to explAIn every sub系统 drown the reader in lore use vague s记录ans instead of specifics hide the real game behind marketing fluff What to produce

Produce:

One-page PDF — the 分享able, visually de签名ed version One-page markdown doc — the editable text version Structured source JSON — the intermediate data used for rendering Visual de签名

The PDF 渲染器 (scripts/render_one_page_gdd.py) produces a professional dark-theme layout:

Dark background — near-black navy #0F111A, with a lighter panel for the header Teal accent colour — #00C8A0 for rules, section headings, pillar tag nubs, and bullet markers Pillar tags — de签名 pillars rendered as pill-shaped labels with a teal left accent in the header Two-column body — left column for mechanics-heavy content, right column for production/aesthetic content Section rules — a teal horizontal rule above each section label Poppins typeface — used when avAIlable (falls back to Liberation Sans or DejaVu) Branded footer — document label on the left, game title on the right

The 渲染器 uses 报告Lab (vector PDF — real text, not a raster image), making the 输出 搜索able, copy-pasteable, and print-sharp.

Font requirements

The 渲染器 搜索es for fonts in standard 系统 locations automatically:

Linux: /usr/分享/fonts/truetype/google-fonts/, /usr/分享/fonts/truetype/liberation/ macOS: ~/库/Fonts/, /库/Fonts/ Windows: C:/Windows/Fonts/

Preferred: Poppins (Bold, Medium, Regular, Light) from fonts.google.com Fallback: Liberation Sans (included in most Linux 系统s)

Dependencies pip 安装 报告lab

Default section structure

Left column:

Genre / Story / Mechanics Summary Key Features Interface & Controls

Right column:

Art Style Music & Sound Roadmap / Launch Criteria (includes 平台, audience, milestones, launch date)

Header band:

Game title 身份 / Mantra (subtitle) De签名 Pillars (as pill tags) Process

• Clarify the de签名 输入

Collect or infer the minimum needed:

game title or working title game 身份 / mantra 2 to 3 de签名 pillars concise gameplay/story/mechanics summary 3 to 6 key features 输入 / interface 模型 art references or aesthetic direction sound direction or emotional audio goals 平台 tar获取 audience milestone plan or launch criteria

If the user gives messy notes, 压缩 them rather than asking endless questions.

• Write for one-page density

Keep each section tight.

图形界面delines:

prefer short bullets over dense paragraphs keep pillars punchy (2–4 words each) keep the summary to a compact paragraph keep features to the strongest few, not every idea make roadmap milestones concrete enough to be useful write like the doc will be skimmed in under two minutes

• Preserve de签名 clarity over style fluff

If the concept is fuzzy:

choose clarity over hype expose contradictions instead of smoothing them over keep clAIms grounded in actual mechanics or fantasy

• Build the structured source JSON

Write a JSON file matching the 渲染器 模式.

Expected fields:

title 身份_mantra de签名_pillars (array, 2–4 items) summary features (array, 3–6 items) interface art_style music_sound 平台 audience milestones (array) launch_day

See references/example-输入.json for a worked example.

• Render markdown and PDF

# Render: python scripts/render_one_page_gdd.py --输入 .json --md .md --pdf .pdf

The 渲染器 auto-discovers fonts. If content is too long, shorten the copy before rerendering — do not try to fit more by cramming.

• 检查 fit and trim aggressively

Before finalizing, 验证:

the concept is legible at a glance the features 列出 is not overstuffed the PDF still feels like a one-pager (not wall-to-wall text) the roadmap is rea列出ic enough to be useful the strongest idea is visible immediately

If the PDF looks crowded, shorten the writing. If there is too much whitespace, the document is probably well-scoped — do not pad it.

输出 expectations

By def