quick-design

Generates lightweight design specs for small game changes like tuning and balance tweaks.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill quick-design-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-design
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/quick-design
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill quick-design-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a full Game Design Document for every small change is wasteful, but implementing tuning adjustments or minor mechanics without any written rationale leads to undocumented decisions and contradictions with existing GDDs. This Skill provides a lightweight middle path that produces a Quick Design Spec for changes too small to warrant full GDD authoring. ## Core Features & Use Cases - Change Classification: Categorizes requests as Tuning, Tweak, Addition, or New Small System, and redirects oversized changes to the full design-system pipeline. - Context Scanning: Reads existing GDDs, the systems index, and prior quick specs to avoid contradictions before drafting. - Structured Spec Templates: Produces category-specific Markdown specs with tuning tables, design deltas, acceptance criteria, and GDD update flags, saved to design/quick-specs/. - Use Case: A designer wants to increase jump height from 5 to 6 units. The Skill classifies it as Tuning, checks the relevant GDD tuning knob range, and writes a dated quick spec with old/new values and acceptance criteria. ## Quick Start Ask the assistant to create a quick design spec for increasing the enemy patrol speed by 10 percent in the existing movement system.

Frequently Asked Questions about quick-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a small game balance change without writing a full GDD?

Use a Quick Design Spec, which captures tuning changes in a single table with old values, new values, and rationale. The spec is saved to design/quick-specs/ with a dated filename and embeds directly into story files for implementation.

When should I use a quick design spec instead of a full GDD?

Use a quick spec for tuning, tweaks, small additions, or standalone features under roughly one week of work. Redirect to full GDD authoring when the change introduces cross-system dependencies, alters core rules, or exceeds one week of implementation.

What change types does the quick design workflow support?

It supports four categories: Tuning (number changes only), Tweak (small behavioral change with no new states), Addition (a small mechanic with one or two new states), and New Small System (a standalone feature too small for full GDD tracking).

Does a quick design spec require going through design review?

No. Quick Design Specs bypass the design-review and review-all-gdds pipeline by design, since they cover small, low-risk, well-scoped changes. They should still be validated with story-readiness before implementation begins.

Can a quick spec update an existing GDD?

Yes. If the spec modifies rules in an existing GDD, it flags the required update with the target file and section. The actual GDD edit is only made after showing the exact old versus new text and receiving explicit approval.