agentleFS
Sign inStart free
venus2099venus2099/codex-game-studios/.agents/skills/design-review/SKILL.md

design-review

Skill1 starsChanged 29 days agoMITView on GitHub

Reviews one design document for completeness, internal consistency, implementability, and design standards. Before handing to programmers.

164 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brief-to-tasks.

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.
  • 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 137 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .claude/skills/design-review/SKILL.md in full before doing anything else.

    line 15
  2. Very specific:

    If it has lines starting with ` !

    line 16
  3. Very specific:

    Follow the skill exactly, translating Claude Code vocabulary with the "Codex compatibility" table in AGENTS.md.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 137 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
<!-- Generated by codex-port/convert_to_codex.py; edits here are overwritten. -->

design-review

Arguments: [path-to-design-doc] [--review full|lean|solo] (take them from the user's message).

This is the Codex entry point for the upstream skill .claude/skills/design-review/SKILL.md, which stays the single source of truth.

  1. Read .claude/skills/design-review/SKILL.md in full before doing anything else.

  2. If it has lines starting with !`, they are startup commands. Run each one from the repository root with ${CLAUDE_SKILL_DIR} = .claude/skills/design-review and treat the output as the config block the skill says is "resolved above". At the time of porting these were:

    bash ".claude/hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow,system_overrides
  3. Follow the skill exactly, translating Claude Code vocabulary with the "Codex compatibility" table in AGENTS.md. In particular, every AskUserQuestion means: ask in chat with numbered options, then stop and wait for the user's reply.

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.

Check your setup, free