agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/design-review/SKILL.md

design-review

Skill9 starsChanged 7 months agoMITView on GitHub

Comprehensive design document review against GDD standards. Checks all required sections, cross-system consistency, formulas, and edge case coverage. Use when reviewing any design doc for quality.

167 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use team-audio, team-level and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 12 projects that use this

  • julianoczkowskiSkill

    brief-to-tasks

    Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

    Also in 7 projects that use this

  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 10 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 10 projects that use this

  • +2 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user which doc(s) to review, OR

    line 13
  2. Very specific:

    Default: review the most recently modified doc in design/gdd/

    line 14
  3. Distinctive:

    Never modify the GDD without user approval.

    line 76

“Common” is measured: kept by at least 6 in 10 of the 139 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/design-review — Design Doc Quality Review

Delegate to: game-designer (with systems-designer assist for technical sections)

Steps

1. Identify Documents to Review

  • Ask the user which doc(s) to review, OR
  • Default: review the most recently modified doc in design/gdd/
  • Multi-doc review: check cross-references and consistency

2. Structural Checks (8 required sections)

For each GDD, verify presence of:

  • Overview & Purpose
  • Core Mechanics (detailed, not just "attacks")
  • Data Schema (DataStore keys, types, defaults)
  • Client-Server Split
  • RemoteEvents/Functions needed
  • Player-Facing UI (description or mockup)
  • Edge Cases & Error States
  • Balancing Parameters (with formulas, not "balanced appropriately")
  • Integration Points

3. Content Quality Checks

  • Specificity: No vague phrases like "balanced appropriately", "calculated correctly"
  • Formulas: Every calculation explicitly written
  • Magic Numbers: All numeric values justified or tunable
  • Edge Cases: Minimum of 5 edge cases documented
  • Integration: Every other system this depends on is named
  • Reading Flow: Sections in logical order; a new reader could understand

4. Cross-System Consistency

  • References to other systems match their actual GDDs
  • Data schema doesn't conflict with existing DataStore schema
  • Remote names align with remotes-manifest
  • UI references match UI style guide

5. Roblox-Specific Checks

  • Security: Server authority respected
  • DataStore: Budget impact considered
  • Performance: Mobile feasibility acknowledged
  • Content policy: Age-appropriate
  • Accessibility: Considered for player interactions

Output

Generate a review report:

# Design Review: [GDD Name]

## Summary
- Total issues: X
- Critical: X (must fix)
- Important: X (should fix)
- Nice-to-have: X (suggestions)

## Critical Issues
1. [Issue description, location, suggested fix]

## Important Issues
1. [...]

## Nice to Have
1. [...]

## Recommended Actions
- [Specific next steps for the author]

Share the report with the user for decision on which fixes to apply. Never modify the GDD without user approval.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.