design-review-garrytan — Claude Code skill: what it does
design-review-garrytan runs a visual audit of your UI, then lands each fix as its own atomic commit. Useful when design debt has piled up and you want it cleared in reviewable pieces.
MIT 221 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill design-review-garrytan -a claude-codeWhat design-review-garrytan does
The skill looks over your interface the way a designer would, writes down what's off, then fixes each item in a commit of its own. Each fix stays separate instead of turning into one sweeping polish patch. It ships inside gstack, Garry Tan's toolkit, and follows the “Designer Who Codes” idea.
It isn't a single file. The skill calls shared tooling that lives under ~/.claude/skills/gstack/bin/…, so upstream installs all of gstack: clone the repo into ~/.claude/skills/gstack, then run ./setup. That script wants Bun 1.3.3 or newer, compiles binaries, pulls Chromium down and adds a Stop hook to your Claude settings; ./setup --no-timeline-stop-hook leaves the hook out. Expect roughly 98 MB of download.
Your working tree has to be clean. The skill offers to commit or stash whatever you have open, since it writes code as it goes. Planning a design before anything exists is a different job, and plan-design-review or design-consultation cover that. A review that must not touch git history won't work here either: the skill edits files and commits.
What it helps with
- audit a screen visually before a release
- split design fixes into separate commits
- rank design debt and start with the worst item
- clear small visual defects without one giant patch
- clean up a page that drifted out of shape
Example prompts for the agent
- Run a design review on the checkout page and fix what you find.
- Do a visual audit of the dashboard, one commit per issue.
- Work through the design debt on the landing page, worst first.
How to install design-review-garrytan
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-review-garrytan -a claude-code2Manually: put the files in place
~/.claude/skills/design-review-garrytan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-review-garrytan/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-review-garrytan -a codex2Manually: put the files in place
.agents/skills/design-review-garrytan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-review-garrytan -a cursor2Manually: put the files in place
.cursor/skills/design-review-garrytan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/design-review-garrytan2Manually: put the files in place
.github/skills/design-review-garrytan/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-review-garrytan -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/design-review-garrytanManually: put the files in place
.devin/skills/design-review-garrytan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-review-garrytan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about design-review-garrytan
How do I install design-review-garrytan in Claude Code?
Run npx skills add podo/design-agent-skills --skill design-review-garrytan -a claude-code; the skill lands at ~/.claude/skills/design-review-garrytan/SKILL.md.
What does design-review-garrytan do?
It audits your interface and then fixes every problem it found in a commit of its own. Design debt gets the same treatment as technical debt: spotted, ranked, closed.
What do I need before running it?
Bun 1.3.3 or newer, Git and Claude. Upstream installs gstack as a whole because the skill leans on its shared tooling, and the setup step also fetches Chromium and registers a Stop hook.
Source text
SKILL.md · MIT
--- name: design-review-garrytan description: | Designer Who Codes: visual audit followed by atomic commits fixing each issue. Garry Tan's design review skill — treats UI like code, identifies and fixes design debt systematically. triggers: - "design review" - "visual audit" - "UI audit" - "design debt" - "fix design issues" das: type: package category: design-review upstream: "https://github.com/garrytan/gstack" upstream_path: "design-review/SKILL.md" version: latest install: false --- # design-review-garrytan > Catalogue stub — part of [garrytan/gstack](https://github.com/garrytan/gstack) (`design-review`) <!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block --> ## Decision tree 1. **Is the full skill already installed?** - `f=~/.claude/skills/gstack/design-review/SKILL.md; [ -e "$f" ] && ! grep -qs "^das:" "$f" && echo "installed" || echo "pointer"` - `installed` → invoke it and proceed - `pointer` → go to step 2 2. **Install** (the skills CLI cannot install this one): This skill is part of gstack and calls gstack's shared tooling (`~/.claude/skills/gstack/bin/…`), so install gstack itself rather than the single skill (`--skill design-review` fails because the CLI only sees gstack's root router, and even with `--full-depth` the copied instructions lack the tooling). `./setup` needs Bun, builds binaries, downloads Chromium and registers a Stop hook in your Claude settings (opt out with `./setup --no-timeline-stop-hook`); ask the user before running it. Upstream's README also tells agents to add a gstack section to CLAUDE.md after setup. ```bash git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack cd ~/.claude/skills/gstack && ./setup ``` **Heads-up** - **Requires:** Bun (setup refuses versions older than 1.3.3; upstream tests 1.4.2+), Git and Claude Code - **License:** MIT - **Download size:** ~98 MB. <!-- das:install:end --> ## Invoke after install - Skill name: `design-review` - Trigger phrases: "design review", "visual audit", "UI audit", "fix design issues" ## What it does "Designer Who Codes" approach: performs a structured visual audit of the UI, then fixes each issue with an atomic commit. Treats design debt like technical debt — identifies it, prioritizes it, and ships fixes. From Garry Tan's gstack, his toolkit for building well-designed products. It expects a clean working tree (it offers to commit or stash your changes first) because every fix lands as its own commit. ## When NOT to use - Planning a design before anything is built — use `plan-design-review` or `design-consultation` - A review that must not touch code or git history — this skill edits files and commits
© podo · MIT · podo/design-agent-skills