Design Review
Run a designer-led visual audit on shipped UI, fix issues in atomic commits, and capture before/after screenshots before launch.
Overview
Design Review is an agent skill most often used in Ship (also Launch) that runs a visual UI audit, applies fixes in atomic commits, and documents before/after screenshots.
Install
npx skills add https://github.com/nexu-io/open-design --skill design-reviewWhat is this skill?
- Designer Who Codes workflow: visual audit then targeted code fixes
- Atomic commits so each visual change stays reviewable
- Before/after screenshots for launch-ready evidence
- Curated from Garry Tan gstack creative-direction lineage
- Trigger phrases: design review, visual audit, pre launch design check
Adoption & trust: 857 installs on skills.sh; 61.4k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your app UI is functionally shipped but looks uneven, and you need a repeatable audit-to-fix loop before users see it.
Who is it for?
Solo builders with a coded frontend who want a structured pre-launch visual pass without hiring a separate design reviewer.
Skip if: Greenfield brand identity, full design-system authoring, or teams that only need accessibility/legal compliance audits with no visual fix pass.
When should I use this skill?
User asks for design review, visual audit, before/after proof, or a pre-launch design check on existing UI.
What do I get? / Deliverables
You get tightened visual polish, traceable commits, and screenshot proof suitable for launch checklists or stakeholder review.
- Visual audit notes
- Atomic fix commits
- Before/after screenshot set
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship/review because the workflow is an audit-and-fix pass on existing UI, not net-new feature design. Review matches visual QA, spacing, hierarchy, and polish fixes with evidence (screenshots), not distribution or SEO work.
Where it fits
Run spacing and hierarchy fixes on dashboard screens right after feature freeze.
Capture before/after shots for a Product Hunt or changelog visual story.
Tighten component consistency after a rushed MVP sprint before you tag a release candidate.
How it compares
Use instead of vague “make it prettier” chat requests when you want audit → atomic fixes → screenshots.
Common Questions / FAQ
Who is design-review for?
Indie builders and small teams with shipped or near-shipped web UI who can iterate in code and want designer-grade visual scrutiny.
When should I use design-review?
In Ship when reviewing UI before release, and in Launch when doing a last visual gate—trigger on “design review”, “visual audit”, or “pre launch design check”.
Is design-review safe to install?
Catalog entry points to upstream gstack; review the Security Audits panel on this page and inspect the upstream repo before granting repo write access for fix commits.
SKILL.md
READMESKILL.md - Design Review
# design-review > Curated from Garry Tan (gstack). ## What it does Designer Who Codes: visual audit then fixes with atomic commits and before/after screenshots. Useful for tightening shipped UI before launch. ## Source - Upstream: https://github.com/garrytan/gstack - Category: `creative-direction` ## How to use This catalogue entry advertises the skill in Open Design so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and references, install the upstream bundle into your active agent's skills directory: ```bash # Inspect the upstream README for exact paths open https://github.com/garrytan/gstack ``` Then ask the agent to invoke this skill by name (`design-review`) or with one of the trigger phrases listed in this skill's frontmatter.