agentleFS
fqmyysjjdfqmyysjjd/agent-feed/.claude/skills/design-review/SKILL.md

design-review

Skill4 starsChanged 6 months agoMITView on GitHub

Use when reviewing design documents, architecture plans, implementation routes, gap analyses, README, AGENTS, rules, domain docs, or skills.

167 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use team-level, team-audio and 10 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-level

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

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

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

    Also in 14 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 11 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 11 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

  • +4 more from lilangMax
  • +3 more from CoralGame

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 5

    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:

    Use this skill after drafting or updating any design, protocol, planning, README, AGENTS, skill, rule, domain, or handoff-document change.

    line 12
  2. Distinctive:

    Do not silently complete unresolved design gaps.

    line 27
  3. Distinctive:

    Before judging readiness, verify result fit:

    line 33
  4. Distinctive:

    If yes, state that the design is ready for the next development step and stop.

    line 41
  5. Distinctive:

    If no, identify the blocking gaps.

    line 43
  6. Very specific:

    When any condition is false, do not fill the gap yourself.

    line 49

“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 Skill

Required Use

Use this skill after drafting or updating any design, protocol, planning, README, AGENTS, skill, rule, domain, or handoff-document change.

Required Reading

  1. .agents/rules/outcome-boundary.md
  2. .agents/domain/README.md
  3. .agents/rules/context-loading.md
  4. .agents/project/architecture-boundaries.md
  5. .agents/rules/development-workflow.md
  6. .agents/rules/review-gates.md
  7. .agents/rules/evidence-gates.md if external research is used.
  8. The document being reviewed.

Core Rule

Do not silently complete unresolved design gaps.

The review's highest-priority question is:

Can the next development step proceed from this design without inventing missing decisions?

Before judging readiness, verify result fit:

  1. The document addresses the user's stated or clearly inferred goal, not just the visible artifact format.
  2. The document explains the real problem, outcome, or workflow it claims to support.
  3. Any missing decision, evidence, boundary, or user assumption that could change the result is called out as a gap.
  4. The document does not hide weak support behind polished wording, broad framing, or generic best practices.
  5. The proposed next action would actually move the user toward the intended result.

If yes, state that the design is ready for the next development step and stop.

If no, identify the blocking gaps. Close a gap directly only when all of these are true:

  1. The answer is already supported by existing source-of-truth files.
  2. The change stays inside the current Task Brief.
  3. The change does not alter public behavior, CLI/API contracts, architecture ownership, adapter behavior, verification gates, source-of-truth boundaries, persistence, security, release scope, or product positioning.

When any condition is false, do not fill the gap yourself. Apply .agents/rules/decision-gates.md and ask for the required decision.

Output

Return readiness judgment, current task boundary, findings or gaps, decision points requiring confirmation, safe next step, documents that should be updated, and whether the document can drive implementation.

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.