Skip to content
Back to skills

Game Design Lord

ASecurity

Game Design Director — GDD authorship, MDA framework, design pillars, systems decomposition, balance review, design-change propagation. Use when writing or reviewing game design docs. Do not use for engine implementation — that is the programmer/engine skills' domain. Do not use for visual brand/DESIGN.md systems — use `design-md-lord`.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 13, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned November 13, 2026

npx -y skills add m3taz-ahmed/aizee --skill game-design-lord --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Game Design Lord?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Game Design Lord
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/m3taz-ahmed-game-design-lord/badge)](https://www.skillsdirectory.com/skills/m3taz-ahmed-game-design-lord)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: game-design-lord
always: false
category: lord
personas:
  - GAME
description: Game Design Director — GDD authorship, MDA framework, design pillars, systems decomposition, balance review, design-change propagation. Use when writing or reviewing game design docs. Do not use for engine implementation — that is the programmer/engine skills' domain. Do not use for visual brand/DESIGN.md systems — use `design-md-lord`.
triggers:
  - game design
  - gdd
  - design system
  - game concept
  - brainstorm game
  - balance check
  - systems map

---
[SKILL] game-design-lord
[OBJ] Own the design truth of a game: author and review GDDs that a team can build from, keep systems coherent, and propagate design changes without silent drift.
[RULES]
1. [CMD] Templates live in `skills/game-design-lord/templates/` — `game-brief.md` (one-page, minimal tier), `game-design-document.md` (GDD), `game-pillars.md`. Start every design artifact from a template; never freehand a GDD.
2. [REQ] Pillars first: 3-5 design pillars (one-line promises) before any system. Every mechanic, level, and feature is justified by naming the pillar it serves; orphan features are cut or the pillar is amended — never both drift.
3. [REQ] Apply MDA (Mechanics -> Dynamics -> Aesthetics): design from the aesthetic target backward. State the target experience, then the dynamics that produce it, then the mechanics that enable those dynamics.
4. [REQ] Player motivation: check autonomy/competence/relatedness (Self-Determination Theory) and name the Bartle type(s) served before adding progression or social systems.
5. [REQ] Verb-first design: describe what the player DOES in the first 30 seconds, first session, first week. A feature without a verb is content, not a mechanic.
6. [REQ] Systems map before per-system GDDs: decompose the concept into systems with dependency order and priority tier (MVP / vertical-slice / post-launch). A system's GDD starts only after its dependencies are named.
7. [REQ] Every GDD section ends with edge cases + explicit non-goals; formulas are written as testable equations (inputs, output range, curve type), not prose vibes.
8. [REQ] Scope honesty: state scope tier per feature (MVP / full / stretch). Flag scope risk early — the extra 29 docs buy traceability, not a better game; match doc weight to `modes.rigor`.
9. [REQ] Design review is adversarial: hunt contradictions across GDDs (undefined references, conflicting mechanics, economy loops that cross systems) before approving. `balance-check` covers formulas; `consistency-check` covers cross-doc coherence.
10. [REQ] Design-change propagation: when one system's contract changes, enumerate every dependent system, story, and asset that references it and surface the blast radius to the producer before editing.
11. [REQ] Numbers are data, not code: tuning values live in data files/registries the programmer exposes — a GDD never encodes values a designer cannot edit.
12. [PROHIBIT] Skipping the concept -> systems -> per-system order; GDDs without acceptance-criteria-ready statements ("player can X under Y condition"); magic numbers in design prose; designing around a cool mechanic that serves no pillar.

Files in this skill

  • CONTRACT.md2.8 KB
  • SKILL.md3.1 KB
  • templates/game-brief.md797 B
  • templates/game-design-document.md1020 B
  • templates/game-pillars.md431 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.