agentleFS
Sign inStart free
wheslleyrimarwheslleyrimar/BuildCLI-Agents/.claude/skills/design-review/SKILL.md

design-review

Skill3 starsChanged 11 days agoMITView on GitHub

Weigh an architecture decision for scalability, reliability, security, and maintainability before anything gets built.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 121 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No recommendation without a stated tradeoff.

    line 37
  2. Distinctive:

    If the evidence does not support a call, say so and name what would settle it.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 121 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

When to use

Reach for this before implementation, when the decision is expensive to reverse: choosing between two architectures, accepting a tradeoff, or deciding whether a risk is worth carrying.

Context loading (minimal)

Read only:

  1. The shared header — Architecture and Engineering Standards — via .buildcli/runtime/bcx header
  2. The bands the decision actually touches
  3. shape.md from the active blueprint, if one exists

Workflow

  1. State the decision in one sentence, and what happens if it is wrong.
  2. Lay out the viable options — at least two — with their real tradeoffs, not their marketing.
  3. Rank the top risks and pair each with a mitigation someone could actually execute.
  4. Define the acceptance checks that would prove the decision was right.
  5. Recommend one option and say plainly why the others lose.

Output

  • A review memo: decision, options, recommendation
  • A risk matrix: risk, likelihood, impact, mitigation
  • Acceptance checks that make the decision falsifiable

Constraints

  • No recommendation without a stated tradeoff. Every choice costs something.
  • Ground the review in the recorded context, not in generic best practice.
  • If the evidence does not support a call, say so and name what would settle it.

Download now (ZIP)

  • Other versions147 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 147

    1. garrytan/gstack★ 139ksame name
    2. Donchitos/Claude-Code-Game-Studios★ 27ksame name
    3. plugin87/ux-ui-agent-skills★ 3.1ksame name
    4. DenchHQ/DenchClaw★ 1.7ksame name
    5. DenchHQ/ironclaw★ 1.7ksame name
    6. me2resh/apexyard★ 542same name
    7. julianoczkowski/designer-skills★ 536same name
    8. TheDecipherist/claude-code-mastery-project-starter-kit★ 337same name
    9. AndrewDryga/emisar★ 330same name
    10. pixel-cellar/Claude-Code-Game-Studios★ 324same name

    137 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use team-audio, team-level 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-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

    • 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
    • +6 more from lilangMax
  • In this repository19 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.

Check your setup, free