quick-design

Draft markdown quick design specs for small game changes.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill quick-design-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-design
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/quick-design
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill quick-design-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a compact, structured alternative to full Game Design Documents for small changes, avoiding the overhead of full GDD authoring while ensuring rationale, acceptance criteria, and traceability are recorded.

Core Features & Use Cases

  • Classification: Automatically categorizes a request as Tuning, Tweak, Addition, or New Small System and prompts for clarification when needed.
  • Context Scan: Locates and reads relevant design/gdd files, systems index, prior quick specs, and asset data to avoid conflicts.
  • Spec Drafting & Filing: Produces a focused Quick Design Spec in a consistent markdown format with rationale, new rules or values, acceptance criteria, and a recommended filename; optionally writes the file to design/quick-specs when approved.
  • Use Case: Increase an ability value, add a small mechanic tweak, or add a minor standalone system without invoking the full design pipeline.

Quick Start

Draft a quick design spec for increase jump height from 5 to 6 units classifying it as a Tuning change, reference the relevant GDD sections, and list acceptance criteria.

Frequently Asked Questions about quick-design

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

FAQPage Schema
How do I draft a quick design spec for small game tuning changes?

Drafting a quick design spec involves classifying the change, scanning existing GDD files for conflicts, and producing a markdown spec with rationale and acceptance criteria. This approach avoids full Game Design Document overhead for small tweaks under one week.

What is the best way to document minor game mechanic additions without a full GDD?

Documenting minor additions uses a lightweight quick-spec format to record rationale, new rules, and acceptance criteria. It categorizes the change as an Addition or New Small System and checks existing design files to prevent conflicts.

Does writing quick-specs require scanning existing game design documents first?

Writing quick-specs requires scanning existing design/gdd files, systems index, and prior quick specs. This context scan ensures the new tuning or tweak avoids conflicts with currently established game mechanics and asset data.

How do I format tuning changes in markdown for game design?

Formatting tuning changes in markdown requires a structured spec containing classification, rationale, new values, and acceptance criteria. The file is optionally written to the design/quick-specs directory using a prescribed filename convention.

When should I use a quick design specification instead of a full Game Design Document?

Use a quick design specification for tuning, tweaks, additions, or new small systems taking under one week or four hours. Full GDD authoring is unnecessary for these minor changes, making lightweight specs more efficient for tracking rationale and acceptance criteria.

Can quick-specs automatically file my game balance tweaks into the design directory?

Quick-specs can optionally write the finalized markdown spec to the design/quick-specs directory using a prescribed filename convention. This filing occurs when approved, ensuring balance tweaks and tuning changes are properly archived.