agentleFS
Sign inStart free
DenchHQDenchHQ/ironclaw/skills/gstack/design-review/SKILL.md

design-review

Skill1.7k starsChanged 7 months agoMITView on GitHub

Design audit of existing code. Same methodology as plan-design-review, but applies fixes directly with atomic commits and before/after evidence. Use when asked to audit the visual design of implemented code.

155 other projects use a version of this.

Trending

Quiet since February.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the DenchHQ/ironclaw repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about DenchHQ/ironclaw

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

Used with

Projects with it also use project-stage-detect, 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

    project-stage-detect

    Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.

    Also in 16 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 13 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

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

The file

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 128 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:

    Check for DESIGN.md — patterns blessed here are not flagged

    line 19
  2. Distinctive:

    Read changed frontend files (full files, not just diff hunks)

    line 20

“Common” is measured: kept by at least 6 in 10 of the 128 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 — Audit and Fix

Same design audit methodology as plan-design-review, but applied to existing code. You find issues AND fix them.

Related skills: plan-design-review | design-consultation | review

Step 1: Context

  1. Check for DESIGN.md — patterns blessed here are not flagged
  2. Read changed frontend files (full files, not just diff hunks)
  3. Identify the design system in use (Tailwind, CSS modules, styled-components, etc.)

Step 2: Audit

Apply the same 8 dimensions from plan-design-review:

  1. Information Architecture
  2. Interaction Design
  3. Visual Hierarchy
  4. Consistency
  5. Accessibility
  6. Responsiveness
  7. Performance
  8. Delight

Plus AI Slop Detection — check for gratuitous gradients, card soup, icon overload.

Step 3: Fix

For each finding:

Mechanical CSS fixes → AUTO-FIX

  • outline: none without alternative focus indicator → add focus-visible styles
  • !important that can be removed → increase specificity instead
  • font-size < 16px on mobile inputs → set to 16px to prevent iOS zoom
  • Missing alt on images → add descriptive alt text
  • Color contrast below WCAG AA → adjust colors

Design judgment needed → ASK

Present each with before/after description and let the user decide.

Step 4: Commit

Each fix gets its own atomic commit:

fix(design): add focus-visible indicators to interactive elements
fix(design): increase contrast ratio on secondary text
fix(a11y): add alt text to profile images

Step 5: Scorecard

Output the same scorecard as plan-design-review showing before and after scores.

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