One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill quick-design-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-design
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/quick-design
Command: npx skills add https://github.com/easonlao/jiazi-game --skill quick-design-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you need to make a small game change, creating a full GDD is often overkill and slows implementation.

Core Features & Use Cases

  • Classifies change scope into Tuning, Tweak, Addition, or New Small System to pick the right lightweight workflow.
  • Scans existing design context by locating the relevant GDD entries and checking prior quick specs to avoid contradictions.
  • Generates an implementation-ready Quick Design Spec with a clear structure, mapping to GDD tuning knobs, and testable acceptance criteria.

Quick Start

Use the quick-design skill with a short description of your change, including what you want to adjust and why, and it will draft a Quick Design Spec for writing directly into design/quick-specs/.

Frequently Asked Questions about quick-design

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

FAQPage Schema
How do I write a lightweight game design spec for minor mechanic tweaks without a full GDD?

A lightweight game design spec for minor mechanic tweaks skips full GDD authoring by classifying the change scope and generating a Quick Design Spec with explicit design deltas, tuning knob mapping, and testable acceptance criteria.

What is a Quick Design Spec used for in game development?

A Quick Design Spec is used for small game changes like tuning number values, minor mechanic tweaks, or defining small standalone systems, ensuring outputs include relevant GDD references, explicit design deltas, and concrete acceptance criteria for implementation.

How do I define acceptance criteria for game balance tuning?

To define acceptance criteria for game balance tuning, generate a Quick Design Spec that maps tuning knobs to assets and data, producing concrete, testable acceptance criteria alongside explicit design deltas for implementation readiness.

Does generating a quick spec work for adding small mechanics to an existing game system?

Generating a quick spec works for adding small mechanics by classifying the change scope as an Addition, scanning existing design context for relevant GDD entries to avoid contradictions, and drafting a spec with design deltas and acceptance criteria.

When should I not use a lightweight design specification for game changes?

You should not use a lightweight design specification for game changes that require full GDD authoring, such as defining large-scale core systems, and instead reserve it for tuning values, minor tweaks, adding small mechanics, or defining small standalone systems.