design-system

Guides collaborative section-by-section authoring of game system design documents.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill design-system-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/design-system
Command: npx skills add https://github.com/onemanking/the-operator --skill design-system-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a game design document (GDD) for a single system in isolation often leads to contradictions with other systems, missing sections, and lost progress when sessions are interrupted. This Skill structures the entire authoring process so each system GDD is consistent, complete, and incrementally saved. ## Core Features & Use Cases - Context-Aware Authoring: Reads the game concept, systems index, and dependency GDDs before asking any questions, so design decisions respect existing constraints. - Section-by-Section Workflow: Walks through eight required GDD sections (Overview, Player Fantasy, Detailed Design, Formulas, Edge Cases, Dependencies, Tuning Knobs, Acceptance Criteria) with a question-options-decision-draft-approval cycle for each. - Incremental File Writes with Recovery: Writes each approved section to design/gdd/[system-name].md immediately and tracks progress in session state, so interrupted sessions resume exactly where they stopped. - Use Case: After mapping your game's systems with an index, run this Skill to design the combat system — it reads related GDDs, proposes formula approaches, flags cross-system conflicts, and produces a complete reviewed GDD. ## Quick Start Ask the AI to design a game system GDD by providing the system name, for example: design the combat-system GDD.

Frequently Asked Questions about design-system

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

FAQPage Schema
How do I write a game design document for a single system?

Invoke the skill with a system name argument, such as /design-system combat-system. It reads your game concept and systems index first, then walks through each GDD section collaboratively, writing approved content to design/gdd/[system-name].md incrementally.

What sections does a game system GDD need?

The skill enforces eight required sections: Overview, Player Fantasy, Detailed Design, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria. Optional sections for Visual/Audio, UI Requirements, and Open Questions can be added afterward.

What happens if I run design-system without a systems index?

The skill fails with a message telling you to run /map-systems first. It requires both design/gdd/game-concept.md and design/gdd/systems-index.md to exist before starting, since it uses them to gather dependency context.

Can I resume an interrupted GDD writing session?

Yes. The skill writes each approved section to the file immediately and records progress in production/session-state/active.md. On resume, it reads the file, skips completed sections, and continues from the next placeholder.

Does the skill check for conflicts between system designs?

Yes. It reads upstream and downstream dependency GDDs and cross-references formulas, interfaces, and edge cases in every section. Conflicts with existing approved GDDs are flagged rather than silently overwritten.