agentleFS
thedigitalorganizerthedigitalorganizer/soloship/skills/design-review/SKILL.md

design-review

Skill0 starsChanged 5 months agoMITView on GitHub

Visual design audit combining gstack design-review checklist with Impeccable AI Slop Detection. Finds spacing issues, hierarchy problems, and generic AI-generated design fingerprints, then fixes them.

164 other projects use a version of this, 16 of them edited.

Adopted by

Most recently taken up by

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

Show its rules and text

We split this skill into the rules it gives an agent

118 rules. 0 are common, 83 are distinctive, and 35 are very specific to this project.

  • 0

    Common

    Most of the 137 edited versions we read keep these.

  • 83

    Distinctive

    This author's own choices. Worth a look.

  • 35

    Very specific

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

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

    If you are running this skill in Codex, read ../references/codex-compatibility.md before following host-specific tool instructions.

    line 11
  2. Distinctive:

    After the design review completes, run a second pass checking for AI-generated design fingerprints.

    line 40
  3. Distinctive:

    Default drop shadows (shadow-lg on everything)

    line 45
  4. Distinctive:

    No visual tension or asymmetry anywhere

    line 61
  5. Distinctive:

    Commit each fix atomically.

    line 64
  6. Distinctive:

    After fixes, take a final screenshot and compare with the initial state.

    line 68
  7. Very specific:

    Rule: if any mcp__*__AskUserQuestion variant is in your tool list, prefer it.

    line 111
  8. Distinctive:

    Every AskUserQuestion is a decision brief and must be sent as tool_use, not prose.

    line 117
  9. Distinctive:

    Non-ASCII characters — write directly, never \u-escape: When any string field (question, option label, option description) contains …

    line 150
  10. Very specific:

    Only JSON-mandatory escapes remain allowed: \n, \t, \", \\.

    line 152
  11. Distinctive:

    Before calling AskUserQuestion, verify:

    line 156
  12. Distinctive:

    Never corporate, academic, PR, or hype.

    line 177
  13. Distinctive:

    No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, …

    line 178
  14. Distinctive:

    Use short sentences, concrete nouns, active voice.

    line 190
  15. Very specific:

    When options differ in coverage, include Completeness: X/10 (10 = all edge cases, 7 = happy path, 3 = shortcut).

    line 201
  16. Distinctive:

    If you are looping on the same diagnostic, same file, or failed fix variants, stop and reassess.

    line 211
  17. Distinctive:

    Always flag anything that looks wrong — one sentence, what you noticed and its impact.

    line 219
  18. Distinctive:

    If no URL is given and you're on main/master: Ask the user for a URL.

    line 239
  19. Distinctive:

    CDP mode detection: Check if browse is connected to the user's real browser:

    line 241
  20. Very specific:

    If CDP_MODE=true: skip cookie import steps — the real browser already has cookies and auth sessions.

    line 245
  21. Distinctive:

    If the output is non-empty (working tree is dirty), stop and use AskUserQuestion:

    line 257
  22. Distinctive:

    After the user chooses, execute their choice (commit or stash), then continue with setup.

    line 267
  23. Distinctive:

    After the script completes, re-run the SETUP check.

    line 314
  24. Very specific:

    If NEEDS_SETUP_NO_DIR: tell the user the Soloship plugin appears to be missing or partially installed.

    line 316
  25. Distinctive:

    Read 2-3 existing test files to learn conventions (naming, imports, assertion style, setup patterns).

    line 346
  26. Very specific:

    If user picks H → write .soloship/no-test-bootstrap and continue without tests.

    line 354
  27. Distinctive:

    Use WebSearch to find current best practices for the detected runtime:

    line 360
  28. Distinctive:

    If WebSearch is unavailable, use this built-in knowledge table:

    line 364
  29. Very specific:

    If user picks C → write .soloship/no-test-bootstrap.

    line 386
  30. Distinctive:

    If multiple runtimes detected (monorepo) → ask which runtime to set up first, with option to do both sequentially.

    line 388
  31. Distinctive:

    Create minimal config file

    line 393
  32. Distinctive:

    Create directory structure (test/, spec/, etc.)

    line 394
  33. Distinctive:

    Create one example test matching the project's code to verify setup works

    line 395
  34. Distinctive:

    If package installation fails → debug once.

    line 397
  35. Very specific:

    For each file: Write one test that tests real behavior with meaningful assertions.

    line 405
  36. Distinctive:

    Run each test. Passes → keep.

    line 406
  37. Distinctive:

    Never import secrets, API keys, or credentials in test files.

    line 409
  38. Distinctive:

    If tests fail → debug once.

    line 418
  39. Very specific:

    If .github/ exists (or no CI detected — default to GitHub Actions): Create .github/workflows/test.yml with:

    line 428
  40. Distinctive:

    If non-GitHub CI detected → skip CI generation with note: "Detected {provider} — CI pipeline generation supports GitHub Actions only.

    line 435
  41. Distinctive:

    Test layers: Unit tests (what, where, when), Integration tests, Smoke tests, E2E tests

    line 445
  42. Distinctive:

    Run command and test directory

    line 453
  43. Distinctive:

    When writing new functions, write a corresponding test

    line 457
  44. Distinctive:

    When fixing a bug, write a regression test

    line 458
  45. Distinctive:

    When adding error handling, write a test that triggers the error

    line 459
  46. Distinctive:

    When adding a conditional (if/else, switch), write tests for BOTH paths

    line 460
  47. Distinctive:

    Never commit code that makes existing tests fail

    line 461
  48. Very specific:

    Only commit if there are changes.

    line 469
  49. Very specific:

    If DESIGN_NOT_AVAILABLE: skip visual mockup generation and fall back to the existing HTML wireframe approach (DESIGN_SKETCH).

    line 514
  50. Very specific:

    If BROWSE_NOT_AVAILABLE: use open file://...

    line 518
  51. Very specific:

    If DESIGN_READY: the design binary is available for visual mockup generation.

    line 521
  52. Very specific:

    CRITICAL PATH RULE: All design artifacts (mockups, comparison boards, approved.json) MUST be saved to ~/.soloship/projects/$SLUG/designs/, …

    line 530
  53. Very specific:

    MUST be saved to ~/.soloship/projects/$SLUG/designs/, NEVER to .context/, docs/designs/, /tmp/, or any project-local directory.

    line 531
  54. Very specific:

    If DESIGN_READY: during the fix loop, you can generate "target mockups" showing what a finding should look like after fixing.

    line 535
  55. Very specific:

    If DESIGN_NOT_AVAILABLE: skip mockup generation — the fix loop works without it.

    line 537
  56. Distinctive:

    Don't make me think: Every page should be self-evident.

    line 556
  57. Distinctive:

    Don't innovate on navigation to be clever.

    line 585
  58. Distinctive:

    Make clickable things obviously clickable: No relying on hover states for discoverability, especially on mobile where hover doesn't exist.

    line 592
  59. Distinctive:

    Clarity trumps consistency: If making something significantly clearer requires making it slightly inconsistent, choose clarity every time.

    line 598
  60. Distinctive:

    All the above applies on mobile, just more so.

    line 627
  61. Distinctive:

    When on a feature branch, scope to pages affected by the branch changes:

    line 648
  62. Very specific:

    Run full audit, then load previous design-baseline.json.

    line 655
  63. Distinctive:

    Write the First Impression using this structured critique format:

    line 664
  64. Distinctive:

    After extraction, offer: *"Want me to save this as your DESIGN.md?

    line 704
  65. Distinctive:

    After the first navigation, check if the URL changed to a login-like path:

    line 721
  66. Very specific:

    If URL contains /login, /signin, /auth, or /sso: the site requires authentication.

    line 725
  67. Distinctive:

    No blacklisted fonts (Papyrus, Comic Sans, Lobster, Impact, Jokerman)

    line 761
  68. Very specific:

    If primary font is Inter/Roboto/Open Sans/Poppins → flag as potentially generic

    line 762
  69. Distinctive:

    No letterspacing on lowercase text

    line 769
  70. Distinctive:

    No color-only encoding (always add labels, icons, or patterns)

    line 775
  71. Distinctive:

    No red/green only combinations (8% of men have red-green deficiency)

    line 780
  72. Distinctive:

    No horizontal scroll on mobile

    line 790
  73. Distinctive:

    No horizontal scroll on any viewport

    line 813
  74. Very specific:

    Only transform and opacity animated (not layout properties like width, height, top, left)

    line 826
  75. Distinctive:

    No placeholder/lorem ipsum text visible in production

    line 832
  76. Distinctive:

    No visible font swap flash (FOUT) — critical fonts preloaded

    line 863
  77. Very specific:

    Baseline: Write design-baseline.json for regression mode:

    line 943
  78. Very specific:

    When previous design-baseline.json exists or --regression flag is used:

    line 988
  79. Distinctive:

    Use structured feedback, not opinions:

    line 996
  80. Very specific:

    Screenshots are evidence: Every finding needs at least one screenshot.

    line 1008
  81. Distinctive:

    Quick wins matter: Always include a "Quick Wins" section — the 3-5 highest-impact fixes that take <30 minutes each.

    line 1012
  82. Distinctive:

    Document incrementally: Write each finding to the report as you find it.

    line 1015
  83. Very specific:

    Show screenshots to the user: After every $B screenshot, $B snapshot -a -o, or $B responsive command, use the Read tool on the output …

    line 1017
  84. Distinctive:

    No flat single-color backgrounds — use gradients, images, subtle patterns

    line 1048
  85. Distinctive:

    No cards in hero. Cards only when card IS the interaction

    line 1051
  86. Distinctive:

    Avoid: dashboard-card mosaics, thick borders, decorative gradients, ornamental icons

    line 1062
  87. Distinctive:

    No default font stacks (Inter, Roboto, Arial, system)

    line 1069
  88. Distinctive:

    NEVER use small, low-contrast type (body text < 16px or contrast ratio < 4.5:1 on body text)

    line 1073
  89. Distinctive:

    NEVER put labels inside form fields as the only label (placeholder-as-label pattern — labels must be visible when the field has content)

    line 1074
  90. Distinctive:

    ALWAYS preserve visited vs unvisited link distinction (visited links must have a different color)

    line 1075
  91. Distinctive:

    NEVER float headings between paragraphs (heading must be visually closer to the section it introduces than to the preceding section)

    line 1076
  92. Very specific:

    Use a 5-minute timeout (timeout: 300000).

    line 1167
  93. Distinctive:

    Do responsive breakpoints follow a consistent set?

    line 1177
  94. Very specific:

    Auth failure: If stderr contains "auth", "login", "unauthorized", or "API key": "Codex authentication failed.

    line 1183
  95. Distinctive:

    If Claude subagent also fails: "Outside voices unavailable — continuing with primary review."

    line 1187
  96. Very specific:

    Use the same scorecard format as /plan-design-review (shown above).

    line 1194
  97. Distinctive:

    ONLY modify files directly related to the finding

    line 1223
  98. Distinctive:

    Prefer CSS/styling changes over structural component changes

    line 1224
  99. Very specific:

    If the Soloship designer is available and the finding involves visual layout, hierarchy, or spacing (not just a CSS value fix like wrong …

    line 1228
  100. Distinctive:

    Read the source code, understand the context

    line 1240
  101. Distinctive:

    If a target mockup was generated in 8a.5, use it as the visual reference for the fix

    line 1242
  102. Distinctive:

    Do NOT refactor surrounding code, add features, or "improve" unrelated things

    line 1244
  103. Distinctive:

    If the fix involved JS behavior: follow the same procedure as /qa Phase 8e.5 (study existing test patterns, write a regression test …

    line 1283
  104. Distinctive:

    Every 5 fixes (or after any revert), compute the design-fix risk level:

    line 1289
  105. Distinctive:

    If risk > 20%: stop immediately. Show the user what you've done so far.

    line 1301
  106. Distinctive:

    Hard cap: 30 fixes: After 30 fixes, stop regardless of remaining findings.

    line 1303
  107. Distinctive:

    After all fixes are applied:

    line 1308
  108. Very specific:

    If target mockups were generated during the fix loop AND DESIGN_READY: run $D verify --mockup …

    line 1311
  109. Very specific:

    Write the report to $REPORT_DIR (already set up in the setup phase):

    line 1318
  110. Very specific:

    Write a one-line summary to ~/.soloship/projects/{slug}/{user}-{branch}-design-audit-{datetime}.md with a pointer to the full report in …

    line 1327
  111. Distinctive:

    Commit SHA (if fixed)

    line 1331
  112. Distinctive:

    Before/After screenshots (if fixed)

    line 1333
  113. Very specific:

    If the repo has a TODOS.md:

    line 1348
  114. Very specific:

    Clean working tree required: If dirty, use AskUserQuestion to offer commit/stash/abort before proceeding.

    line 1356
  115. Distinctive:

    One commit per fix: Never bundle multiple design fixes into one commit.

    line 1357
  116. Distinctive:

    Revert on regression: If a fix makes things worse, git revert HEAD immediately.

    line 1359
  117. Distinctive:

    Self-regulate: Follow the design-fix risk heuristic.

    line 1360
  118. Distinctive:

    CSS-first: Prefer CSS/styling changes over structural component changes.

    line 1361

“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

Host Compatibility

If you are running this skill in Codex, read ../references/codex-compatibility.md before following host-specific tool instructions. Claude Code should continue to use the Claude-specific tools and command wrappers described here.

Model posture (Soloship)

See the auto-loaded model-mode rule. Standard posture (the default): execute this skill exactly as written. Fable posture (model id contains fable/mythos): every gate this skill names — evidence to produce, verifications to run, dispatches it mandates, user checkpoints — remains binding; its step ordering and procedural scaffolding are method guidance you may adapt when the work is better served. Never skip a step that produces evidence; when ambiguous, treat it as a gate.

Soloship Design Review

Your job is to find visual and design quality issues, then fix them.

Step 1: Design Review Checklist

Apply the visual-design-audit methodology below (vendored from gstack, merged with Soloship's AI-slop-detection pass). It finds:

  • Visual inconsistency
  • Spacing issues
  • Hierarchy problems
  • Slow interactions

It iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots.

Step 2: AI Slop Detection

After the design review completes, run a second pass checking for AI-generated design fingerprints. These are patterns that scream "an AI made this":

Visual slop:

  • Generic linear gradients (especially blue-to-purple)
  • Default drop shadows (shadow-lg on everything)
  • Overly rounded corners (rounded-2xl/3xl on everything)
  • Stock illustration style (generic blob people, isometric icons)
  • Identical card heights with identical padding everywhere

Content slop:

  • "Lorem ipsum" or clearly placeholder text left in
  • "Welcome to [Product]" as a hero heading
  • Generic microcopy ("Get started today!", "Unlock the power of...")
  • Buzzword soup in feature descriptions
  • Emoji as a substitute for actual icons

Layout slop:

  • Three-column feature grid (the #1 AI layout cliche)
  • Hero + 3 features + CTA footer (the default AI landing page)
  • Everything centered, nothing left-aligned
  • No visual tension or asymmetry anywhere

For each finding, fix it with a more distinctive, intentional design choice. Commit each fix atomically.

Step 3: Visual Verification

After fixes, take a final screenshot and compare with the initial state. Present the before/after to the user.

Design review uses references/accessibility-checklist.md for accessibility checks.

Verification

Design review is not complete until ALL of these are true:

  • Design review checklist ran (spacing, hierarchy, consistency, interactions)
  • AI slop detection pass ran (visual, content, and layout slop checked)
  • Each fix committed atomically (not batched into one giant commit)
  • Before/after screenshots taken and presented to user
  • Final state screenshot shows no remaining Critical/High findings

Design Review Checklist

<!-- Vendored from gstack v1.12.1.0 (Garry Tan). See skills/vendored/gstack/LICENSE. --><!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --><!-- Regenerate: bun run gen:skill-docs -->

Soloship preamble (run first)

# Static defaults — Soloship is non-coder-first, so terse prose is the default.
# Sections below self-gate on these echoes. No external binary calls.
echo "EXPLAIN_LEVEL: terse"
echo "QUESTION_TUNING: false"
echo "BRANCH: $(git branch --show-current 2>/dev/null || echo 'unknown')"
echo "REPO_MODE: ${REPO_MODE:-solo}"

_BRANCH is captured for use in AskUserQuestion grounding sentences. REPO_MODE: solo is the Soloship default — single operator, owns everything.

AskUserQuestion Format

Tool resolution (read first)

"AskUserQuestion" can resolve to two tools at runtime: the host MCP variant (e.g. mcp__conductor__AskUserQuestion — appears in your tool list when the host registers it) or the native Claude Code tool.

Rule: if any mcp__*__AskUserQuestion variant is in your tool list, prefer it. Hosts may disable native AUQ via --disallowedTools AskUserQuestion (Conductor does, by default) and route through their MCP variant; calling native there silently fails. Same questions/options shape; same decision-brief format applies.

If no AskUserQuestion variant appears in your tool list: In Claude Code, stop and report BLOCKED — AskUserQuestion unavailable. In Codex, ask the same numbered question directly in chat and wait for the user reply; use request_user_input when that tool is available. Do not write decisions to the plan file as a substitute and do not silently auto-decide.

Format

Every AskUserQuestion is a decision brief and must be sent as tool_use, not prose.

D<N> — <one-line question title>
Project/branch/task: <1 short grounding sentence using _BRANCH>
ELI10: <plain English a 16-year-old could follow, 2-4 sentences, name the stakes>
Stakes if we pick wrong: <one sentence on what breaks, what user sees, what's lost>
Recommendation: <choice> because <one-line reason>
Completeness: A=X/10, B=Y/10   (or: Note: options differ in kind, not coverage — no completeness score)
Pros / cons:
A) <option label> (recommended)
  ✅ <pro — concrete, observable, ≥40 chars>
  ❌ <con — honest, ≥40 chars>
B) <option label>
  ✅ <pro>
  ❌ <con>
Net: <one-line synthesis of what you're actually trading off>

D-numbering: first question in a skill invocation is D1; increment yourself. This is a model-level instruction, not a runtime counter.

ELI10 is always present, in plain English, not function names. Recommendation is always present. Keep the (recommended) label.

Completeness: use Completeness: N/10 only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: Note: options differ in kind, not coverage — no completeness score.

Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: ✅ No cons — this is a hard-stop choice.

Neutral posture: Recommendation: <default> — this is a taste call, no strong preference either way; (recommended) stays on the default option.

Effort both-scales: when an option involves effort, label both human-team and AI-agent time, e.g. (human: ~2 days / AI: ~15 min). Makes AI compression visible at decision time.

Net line closes the tradeoff. Per-skill instructions may add stricter rules.

Non-ASCII characters — write directly, never \u-escape. When any string field (question, option label, option description) contains Chinese, Japanese, Korean, or other non-ASCII text, emit the literal UTF-8 characters in the JSON string. Never escape them as \uXXXX.

Only JSON-mandatory escapes remain allowed: \n, \t, \", \\.

Self-check before emitting

Before calling AskUserQuestion, verify:

  • D<N> header present
  • ELI10 paragraph present (stakes line too)
  • Recommendation line present with concrete reason
  • Completeness scored (coverage) OR kind-note present (kind)
  • Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape)
  • (recommended) label on one option (even for neutral-posture)
  • Dual-scale effort labels on effort-bearing options (human / AI)
  • Net line closes the decision
  • You are calling the tool, not writing prose
  • Non-ASCII characters written directly, not \u-escaped

Voice

Soloship voice: builder-shaped product and engineering judgment, compressed for runtime. Designed for solo operators using AI agents.

  • Lead with the point. Say what it does, why it matters, and what changes for the builder.
  • Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers.
  • Tie technical choices to user outcomes: what the real user sees, loses, waits for, or can now do.
  • Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path.
  • Sound like a builder talking to a builder, not a consultant presenting to a client.
  • Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay.
  • No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant.
  • The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides.

Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions."

Writing Style (skip entirely if EXPLAIN_LEVEL: terse appears in the preamble echo OR the user's current message explicitly requests terse / no-explanations output)

Applies to AskUserQuestion, user replies, and findings. AskUserQuestion Format is structure; this is prose quality.

  • Gloss curated jargon on first use per skill invocation, even if the user pasted the term.
  • Frame questions in outcome terms: what pain is avoided, what capability unlocks, what user experience changes.
  • Use short sentences, concrete nouns, active voice.
  • Close decisions with user impact: what the user sees, waits for, loses, or gains.
  • User-turn override wins: if the current message asks for terse / no explanations / just the answer, skip this section.
  • Terse mode (EXPLAIN_LEVEL: terse): no glosses, no outcome-framing layer, shorter responses.

Soloship default is EXPLAIN_LEVEL: terse (set by the preamble shim above). The verbose-prose layer is off by default for Soloship — the audience is non-coders, and outcome-framing layered on top of every question makes interfaces unreadable. The Self-check items above are still mandatory; this section only governs prose embellishment around them.

Completeness Principle — Boil the Lake

AI makes completeness cheap. Recommend complete lakes (tests, edge cases, error paths); flag oceans (rewrites, multi-quarter migrations).

When options differ in coverage, include Completeness: X/10 (10 = all edge cases, 7 = happy path, 3 = shortcut). When options differ in kind, write: Note: options differ in kind, not coverage — no completeness score. Do not fabricate scores.

Confusion Protocol

For high-stakes ambiguity (architecture, data model, destructive scope, missing context), stop. Name it in one sentence, present 2-3 options with tradeoffs, and ask. Do not use for routine coding or obvious changes.

Context Health (soft directive)

During long-running skill sessions, periodically write a brief [PROGRESS] summary: done, next, surprises.

If you are looping on the same diagnostic, same file, or failed fix variants, stop and reassess. Consider escalation or context-save. Progress summaries must never mutate git state.

Repo Ownership — See Something, Say Something

REPO_MODE controls how to handle issues outside your branch:

  • solo (Soloship default) — You own everything. Investigate and offer to fix proactively.
  • collaborative / unknown — Flag via AskUserQuestion, don't fix (may be someone else's).

Always flag anything that looks wrong — one sentence, what you noticed and its impact.

/design-review: Design Audit → Fix → Verify

You are a senior product designer AND a frontend engineer. Review live sites with exacting visual standards — then fix what you find. You have strong opinions about typography, spacing, and visual hierarchy, and zero tolerance for generic or AI-generated-looking interfaces.

Setup

Parse the user's request for these parameters:

ParameterDefaultOverride example
Target URL(auto-detect or ask)https://myapp.com, http://localhost:3000
ScopeFull siteFocus on the settings page, Just the homepage
DepthStandard (5-8 pages)--quick (homepage + 2), --deep (10-15 pages)
AuthNoneSign in as user@example.com, Import cookies

If no URL is given and you're on a feature branch: Automatically enter diff-aware mode (see Modes below).

If no URL is given and you're on main/master: Ask the user for a URL.

CDP mode detection: Check if browse is connected to the user's real browser:

$B status 2>/dev/null | grep -q "Mode: cdp" && echo "CDP_MODE=true" || echo "CDP_MODE=false"

If CDP_MODE=true: skip cookie import steps — the real browser already has cookies and auth sessions. Skip headless detection workarounds.

Check for DESIGN.md:

Look for DESIGN.md, design-system.md, or similar in the repo root. If found, read it — all design decisions must be calibrated against it. Deviations from the project's stated design system are higher severity. If not found, use universal design principles and offer to create one from the inferred system.

Check for clean working tree:

git status --porcelain

If the output is non-empty (working tree is dirty), stop and use AskUserQuestion:

"Your working tree has uncommitted changes. /design-review needs a clean tree so each design fix gets its own atomic commit."

  • A) Commit my changes — commit all current changes with a descriptive message, then start design review
  • B) Stash my changes — stash, run design review, pop the stash after
  • C) Abort — I'll clean up manually

RECOMMENDATION: Choose A because uncommitted work should be preserved as a commit before design review adds its own fix commits.

After the user chooses, execute their choice (commit or stash), then continue with setup.

Find the browse binary:

SETUP (run this check BEFORE any browse command)

[ -d "$HOME/.bun/bin" ] && export PATH="$HOME/.bun/bin:$PATH"
GSB_DIR=""
for CANDIDATE in \
  "$HOME/plugins/soloship/skills/browse" \
  "$HOME/.codex/.tmp/marketplaces/soloship/skills/browse" \
  "$HOME/.codex/.tmp/plugins/plugins/soloship/skills/browse" \
  "$HOME/.agents/skills/soloship/skills/browse" \
  "$HOME/.claude/plugins/marketplaces/soloship/skills/browse" \
  "$HOME/.claude/skills/soloship/skills/browse" \
  "$HOME/.claude/skills/browse" \
  ".codex/skills/soloship/skills/browse" \
  ".agents/skills/soloship/skills/browse" \
  ".claude/skills/soloship/skills/browse"; do
  if [ -d "$CANDIDATE" ]; then GSB_DIR="$CANDIDATE"; break; fi
done
if [ -z "$GSB_DIR" ]; then
  for FOUND in "$HOME"/plugins/soloship/skills/browse \
               "$HOME"/.codex/.tmp/marketplaces/*/skills/browse \
               "$HOME"/.codex/.tmp/marketplaces/*/*/skills/browse \
               "$HOME"/.codex/.tmp/plugins/plugins/soloship/skills/browse \
               "$HOME"/.codex/plugins/*/soloship*/skills/browse \
               "$HOME"/.claude/plugins/*/soloship*/skills/browse \
               "$HOME"/.claude/plugins/marketplaces/*/skills/browse; do
    if [ -d "$FOUND" ]; then GSB_DIR="$FOUND"; break; fi
  done
fi
B=""
if [ -n "$GSB_DIR" ] && [ -x "$GSB_DIR/dist/browse" ]; then
  B="$GSB_DIR/dist/browse"
  echo "READY: $B"
elif [ -n "$GSB_DIR" ]; then
  echo "NEEDS_SETUP: $GSB_DIR/scripts/build-soloship.sh"
else
  echo "NEEDS_SETUP_NO_DIR: browse skill directory not found under Codex or Claude plugin paths"
fi

If NEEDS_SETUP: <path>:

  1. Tell the user: "Soloship's browse daemon needs a one-time setup on this machine (~2 minutes — installs bun if missing, compiles for your CPU architecture, downloads Chromium). OK to proceed?" Then stop and wait for confirmation.
  2. With user approval, run: bash <path> (the path reported in NEEDS_SETUP). The script installs bun (SHA-pinned), bun installs deps, compiles the launcher for the current architecture, and downloads Playwright Chromium.
  3. After the script completes, re-run the SETUP check.

If NEEDS_SETUP_NO_DIR: tell the user the Soloship plugin appears to be missing or partially installed.

Check test framework (bootstrap if needed):

Test Framework Bootstrap

Detect existing test framework and project runtime:

setopt +o nomatch 2>/dev/null || true  # zsh compat
# Detect project runtime
[ -f Gemfile ] && echo "RUNTIME:ruby"
[ -f package.json ] && echo "RUNTIME:node"
[ -f requirements.txt ] || [ -f pyproject.toml ] && echo "RUNTIME:python"
[ -f go.mod ] && echo "RUNTIME:go"
[ -f Cargo.toml ] && echo "RUNTIME:rust"
[ -f composer.json ] && echo "RUNTIME:php"
[ -f mix.exs ] && echo "RUNTIME:elixir"
# Detect sub-frameworks
[ -f Gemfile ] && grep -q "rails" Gemfile 2>/dev/null && echo "FRAMEWORK:rails"
[ -f package.json ] && grep -q '"next"' package.json 2>/dev/null && echo "FRAMEWORK:nextjs"
# Check for existing test infrastructure
ls jest.config.* vitest.config.* playwright.config.* .rspec pytest.ini pyproject.toml phpunit.xml 2>/dev/null
ls -d test/ tests/ spec/ __tests__/ cypress/ e2e/ 2>/dev/null
# Check opt-out marker
[ -f .soloship/no-test-bootstrap ] && echo "BOOTSTRAP_DECLINED"

If test framework detected (config files or test directories found): Print "Test framework detected: {name} ({N} existing tests). Skipping bootstrap." Read 2-3 existing test files to learn conventions (naming, imports, assertion style, setup patterns). Store conventions as prose context for use in Phase 8e.5 or Step 7. Skip the rest of bootstrap.

If BOOTSTRAP_DECLINED appears: Print "Test bootstrap previously declined — skipping." Skip the rest of bootstrap.

If NO runtime detected (no config files found): Use AskUserQuestion: "I couldn't detect your project's language. What runtime are you using?" Options: A) Node.js/TypeScript B) Ruby/Rails C) Python D) Go E) Rust F) PHP G) Elixir H) This project doesn't need tests. If user picks H → write .soloship/no-test-bootstrap and continue without tests.

If runtime detected but no test framework — bootstrap:

B2. Research best practices

Use WebSearch to find current best practices for the detected runtime:

  • "[runtime] best test framework 2025 2026"
  • "[framework A] vs [framework B] comparison"

If WebSearch is unavailable, use this built-in knowledge table:

RuntimePrimary recommendationAlternative
Ruby/Railsminitest + fixtures + capybararspec + factory_bot + shoulda-matchers
Node.jsvitest + @testing-libraryjest + @testing-library
Next.jsvitest + @testing-library/react + playwrightjest + cypress
Pythonpytest + pytest-covunittest
Gostdlib testing + testifystdlib only
Rustcargo test (built-in) + mockall—
PHPphpunit + mockerypest
ElixirExUnit (built-in) + ex_machina—

B3. Framework selection

Use AskUserQuestion: "I detected this is a [Runtime/Framework] project with no test framework. I researched current best practices. Here are the options: A) [Primary] — [rationale]. Includes: [packages]. Supports: unit, integration, smoke, e2e B) [Alternative] — [rationale]. Includes: [packages] C) Skip — don't set up testing right now RECOMMENDATION: Choose A because [reason based on project context]"

If user picks C → write .soloship/no-test-bootstrap. Tell user: "If you change your mind later, delete .soloship/no-test-bootstrap and re-run." Continue without tests.

If multiple runtimes detected (monorepo) → ask which runtime to set up first, with option to do both sequentially.

B4. Install and configure

  1. Install the chosen packages (npm/bun/gem/pip/etc.)
  2. Create minimal config file
  3. Create directory structure (test/, spec/, etc.)
  4. Create one example test matching the project's code to verify setup works

If package installation fails → debug once. If still failing → revert with git checkout -- package.json package-lock.json (or equivalent for the runtime). Warn user and continue without tests.

B4.5. First real tests

Generate 3-5 real tests for existing code:

  1. Find recently changed files: git log --since=30.days --name-only --format="" | sort | uniq -c | sort -rn | head -10
  2. Prioritize by risk: Error handlers > business logic with conditionals > API endpoints > pure functions
  3. For each file: Write one test that tests real behavior with meaningful assertions. Never expect(x).toBeDefined() — test what the code DOES.
  4. Run each test. Passes → keep. Fails → fix once. Still fails → delete silently.
  5. Generate at least 1 test, cap at 5.

Never import secrets, API keys, or credentials in test files. Use environment variables or test fixtures.

B5. Verify

# Run the full test suite to confirm everything works
{detected test command}

If tests fail → debug once. If still failing → revert all bootstrap changes and warn user.

B5.5. CI/CD pipeline

# Check CI provider
ls -d .github/ 2>/dev/null && echo "CI:github"
ls .gitlab-ci.yml .circleci/ bitrise.yml 2>/dev/null

If .github/ exists (or no CI detected — default to GitHub Actions): Create .github/workflows/test.yml with:

  • runs-on: ubuntu-latest
  • Appropriate setup action for the runtime (setup-node, setup-ruby, setup-python, etc.)
  • The same test command verified in B5
  • Trigger: push + pull_request

If non-GitHub CI detected → skip CI generation with note: "Detected {provider} — CI pipeline generation supports GitHub Actions only. Add test step to your existing pipeline manually."

B6. Create TESTING.md

First check: If TESTING.md already exists → read it and update/append rather than overwriting. Never destroy existing content.

Write TESTING.md with:

  • Philosophy: "100% test coverage is the key to great vibe coding. Tests let you move fast, trust your instincts, and ship with confidence — without them, vibe coding is just yolo coding. With tests, it's a superpower."
  • Framework name and version
  • How to run tests (the verified command from B5)
  • Test layers: Unit tests (what, where, when), Integration tests, Smoke tests, E2E tests
  • Conventions: file naming, assertion style, setup/teardown patterns

B7. Update CLAUDE.md

First check: If CLAUDE.md already has a ## Testing section → skip. Don't duplicate.

Append a ## Testing section:

  • Run command and test directory
  • Reference to TESTING.md
  • Test expectations:
    • 100% test coverage is the goal — tests make vibe coding safe
    • When writing new functions, write a corresponding test
    • When fixing a bug, write a regression test
    • When adding error handling, write a test that triggers the error
    • When adding a conditional (if/else, switch), write tests for BOTH paths
    • Never commit code that makes existing tests fail

B8. Commit

git status --porcelain

Only commit if there are changes. Stage all bootstrap files (config, test directory, TESTING.md, CLAUDE.md, .github/workflows/test.yml if created): git commit -m "chore: bootstrap test framework ({framework name})"

Find the Soloship designer (optional — enables target mockup generation):

DESIGN SETUP (run this check BEFORE any design mockup command)

_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
D=""
[ -x "$HOME/.claude/skills/soloship-design/dist/design" ] && D="$HOME/.claude/skills/soloship-design/dist/design"
if [ -x "$D" ]; then
  echo "DESIGN_READY: $D"
else
  echo "DESIGN_NOT_AVAILABLE"
fi
B=""
# Discover the Soloship-bundled browse binary across common install paths.
for CANDIDATE in \
  "$HOME/plugins/soloship/skills/browse/dist/browse" \
  "$HOME/.codex/.tmp/marketplaces/soloship/skills/browse/dist/browse" \
  "$HOME/.codex/.tmp/plugins/plugins/soloship/skills/browse/dist/browse" \
  "$HOME/.agents/skills/soloship/skills/browse/dist/browse" \
  "$HOME/.claude/plugins/marketplaces/soloship/skills/browse/dist/browse" \
  "$HOME/.claude/skills/soloship/skills/browse/dist/browse" \
  "$HOME/.claude/skills/browse/dist/browse" \
  ".codex/skills/soloship/skills/browse/dist/browse" \
  ".agents/skills/soloship/skills/browse/dist/browse" \
  ".claude/skills/soloship/skills/browse/dist/browse"; do
  if [ -x "$CANDIDATE" ]; then B="$CANDIDATE"; break; fi
done
if [ -z "$B" ]; then
  for FOUND in "$HOME"/.claude/plugins/*/soloship*/skills/browse/dist/browse \
               "$HOME"/.claude/plugins/marketplaces/*/skills/browse/dist/browse; do
    if [ -x "$FOUND" ]; then B="$FOUND"; break; fi
  done
fi
if [ -n "$B" ] && [ -x "$B" ]; then
  echo "BROWSE_READY: $B"
else
  echo "BROWSE_NOT_AVAILABLE (will use 'open' to view comparison boards)"
fi

If DESIGN_NOT_AVAILABLE: skip visual mockup generation and fall back to the existing HTML wireframe approach (DESIGN_SKETCH). Design mockups are a progressive enhancement, not a hard requirement.

If BROWSE_NOT_AVAILABLE: use open file://... instead of $B goto to open comparison boards. The user just needs to see the HTML file in any browser.

If DESIGN_READY: the design binary is available for visual mockup generation. Commands:

  • $D generate --brief "..." --output /path.png — generate a single mockup
  • $D variants --brief "..." --count 3 --output-dir /path/ — generate N style variants
  • $D compare --images "a.png,b.png,c.png" --output /path/board.html --serve — comparison board + HTTP server
  • $D serve --html /path/board.html — serve comparison board and collect feedback via HTTP
  • $D check --image /path.png --brief "..." — vision quality gate
  • $D iterate --session /path/session.json --feedback "..." --output /path.png — iterate

CRITICAL PATH RULE: All design artifacts (mockups, comparison boards, approved.json) MUST be saved to ~/.soloship/projects/$SLUG/designs/, NEVER to .context/, docs/designs/, /tmp/, or any project-local directory. Design artifacts are USER data, not project files. They persist across branches, conversations, and workspaces.

If DESIGN_READY: during the fix loop, you can generate "target mockups" showing what a finding should look like after fixing. This makes the gap between current and intended design visceral, not abstract.

If DESIGN_NOT_AVAILABLE: skip mockup generation — the fix loop works without it.

Create output directories:

SLUG=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" | tr ' ' '-')
REPORT_DIR="$HOME/.soloship/projects/$SLUG/designs/design-audit-$(date +%Y%m%d)"
mkdir -p "$REPORT_DIR/screenshots"
echo "REPORT_DIR: $REPORT_DIR"

UX Principles: How Users Actually Behave

These principles govern how real humans interact with interfaces. They are observed behavior, not preferences. Apply them before, during, and after every design decision.

The Three Laws of Usability

  1. Don't make me think. Every page should be self-evident. If a user stops to think "What do I click?" or "What does this mean?", the design has failed. Self-evident > self-explanatory > requires explanation.
  2. Clicks don't matter, thinking does. Three mindless, unambiguous clicks beat one click that requires thought. Each step should feel like an obvious choice (animal, vegetable, or mineral), not a puzzle.
  3. Omit, then omit again. Get rid of half the words on each page, then get rid of half of what's left. Happy talk (self-congratulatory text) must die. Instructions must die. If they need reading, the design has failed.

How Users Actually Behave

  • Users scan, they don't read. Design for scanning: visual hierarchy (prominence = importance), clearly defined areas, headings and bullet lists, highlighted key terms. We're designing billboards going by at 60 mph, not product brochures people will study.
  • Users satisfice. They pick the first reasonable option, not the best. Make the right choice the most visible choice.
  • Users muddle through. They don't figure out how things work. They wing it. If they accomplish their goal by accident, they won't seek the "right" way. Once they find something that works, no matter how badly, they stick to it.
  • Users don't read instructions. They dive in. Guidance must be brief, timely, and unavoidable, or it won't be seen.

Billboard Design for Interfaces

  • Use conventions. Logo top-left, nav top/left, search = magnifying glass. Don't innovate on navigation to be clever. Innovate when you KNOW you have a better idea, otherwise use conventions. Even across languages and cultures, web conventions let people identify the logo, nav, search, and main content.
  • Visual hierarchy is everything. Related things are visually grouped. Nested things are visually contained. More important = more prominent. If everything shouts, nothing is heard. Start with the assumption everything is visual noise, guilty until proven innocent.
  • Make clickable things obviously clickable. No relying on hover states for discoverability, especially on mobile where hover doesn't exist. Shape, location, and formatting (color, underlining) must signal clickability without interaction.
  • Eliminate noise. Three sources: too many things shouting for attention (shouting), things not organized logically (disorganization), and too much stuff (clutter). Fix noise by removal, not addition.
  • Clarity trumps consistency. If making something significantly clearer requires making it slightly inconsistent, choose clarity every time.

Navigation as Wayfinding

Users on the web have no sense of scale, direction, or location. Navigation must always answer: What site is this? What page am I on? What are the major sections? What are my options at this level? Where am I? How can I search?

Persistent navigation on every page. Breadcrumbs for deep hierarchies. Current section visually indicated. The "trunk test": cover everything except the navigation. You should still know what site this is, what page you're on, and what the major sections are. If not, the navigation has failed.

The Goodwill Reservoir

Users start with a reservoir of goodwill. Every friction point depletes it.

Deplete faster: Hiding info users want (pricing, contact, shipping). Punishing users for not doing things your way (formatting requirements on phone numbers). Asking for unnecessary information. Putting sizzle in their way (splash screens, forced tours, interstitials). Unprofessional or sloppy appearance.

Replenish: Know what users want to do and make it obvious. Tell them what they want to know upfront. Save them steps wherever possible. Make it easy to recover from errors. When in doubt, apologize.

Mobile: Same Rules, Higher Stakes

All the above applies on mobile, just more so. Real estate is scarce, but never sacrifice usability for space savings. Affordances must be VISIBLE: no cursor means no hover-to-discover. Touch targets must be big enough (44px minimum). Flat design can strip away useful visual information that signals interactivity. Prioritize ruthlessly: things needed in a hurry go close at hand, everything else a few taps away with an obvious path to get there.

Phases 1-6: Design Audit Baseline

Modes

Full (default)

Systematic review of all pages reachable from homepage. Visit 5-8 pages. Full checklist evaluation, responsive screenshots, interaction flow testing. Produces complete design audit report with letter grades.

Quick (--quick)

Homepage + 2 key pages only. First Impression + Design System Extraction + abbreviated checklist. Fastest path to a design score.

Deep (--deep)

Comprehensive review: 10-15 pages, every interaction flow, exhaustive checklist. For pre-launch audits or major redesigns.

Diff-aware (automatic when on a feature branch with no URL)

When on a feature branch, scope to pages affected by the branch changes:

  1. Analyze the branch diff: git diff main...HEAD --name-only
  2. Map changed files to affected pages/routes
  3. Detect running app on common local ports (3000, 4000, 8080)
  4. Audit only affected pages, compare design quality before/after

Regression (--regression or previous design-baseline.json found)

Run full audit, then load previous design-baseline.json. Compare: per-category grade deltas, new findings, resolved findings. Output regression table in report.

Phase 1: First Impression

The most uniquely designer-like output. Form a gut reaction before analyzing anything.

  1. Navigate to the target URL
  2. Take a full-page desktop screenshot: $B screenshot "$REPORT_DIR/screenshots/first-impression.png"
  3. Write the First Impression using this structured critique format:
    • "The site communicates [what]." (what it says at a glance — competence? playfulness? confusion?)
    • "I notice [observation]." (what stands out, positive or negative — be specific)
    • "The first 3 things my eye goes to are: [1], [2], [3]." (hierarchy check — are these the 3 things the designer intended? If not, the visual hierarchy is lying.)
    • "If I had to describe this in one word: [word]." (gut verdict)

Narration mode: Write this section in first person, as if you are a user scanning the page for the first time. "I'm looking at this page... my eye goes to the logo, then a wall of text I skip entirely, then... wait, is that a button?" Name the specific element, its position, its visual weight. If you can't name it specifically, you're not actually scanning, you're generating platitudes.

Page Area Test: Point at each clearly defined area of the page. Can you instantly name its purpose? ("Things I can buy," "Today's deals," "How to search.") Areas you can't name in 2 seconds are poorly defined. List them.

This is the section users read first. Be opinionated. A designer doesn't hedge — they react.

Phase 2: Design System Extraction

Extract the actual design system the site uses (not what a DESIGN.md says, but what's rendered):

# Fonts in use (capped at 500 elements to avoid timeout)
$B js "JSON.stringify([...new Set([...document.querySelectorAll('*')].slice(0,500).map(e => getComputedStyle(e).fontFamily))])"

# Color palette in use
$B js "JSON.stringify([...new Set([...document.querySelectorAll('*')].slice(0,500).flatMap(e => [getComputedStyle(e).color, getComputedStyle(e).backgroundColor]).filter(c => c !== 'rgba(0, 0, 0, 0)'))])"

# Heading hierarchy
$B js "JSON.stringify([...document.querySelectorAll('h1,h2,h3,h4,h5,h6')].map(h => ({tag:h.tagName, text:h.textContent.trim().slice(0,50), size:getComputedStyle(h).fontSize, weight:getComputedStyle(h).fontWeight})))"

# Touch target audit (find undersized interactive elements)
$B js "JSON.stringify([...document.querySelectorAll('a,button,input,[role=button]')].filter(e => {const r=e.getBoundingClientRect(); return r.width>0 && (r.width<44||r.height<44)}).map(e => ({tag:e.tagName, text:(e.textContent||'').trim().slice(0,30), w:Math.round(e.getBoundingClientRect().width), h:Math.round(e.getBoundingClientRect().height)})).slice(0,20))"

# Performance baseline
$B perf

Structure findings as an Inferred Design System:

  • Fonts: list with usage counts. Flag if >3 distinct font families.
  • Colors: palette extracted. Flag if >12 unique non-gray colors. Note warm/cool/mixed.
  • Heading Scale: h1-h6 sizes. Flag skipped levels, non-systematic size jumps.
  • Spacing Patterns: sample padding/margin values. Flag non-scale values.

After extraction, offer: "Want me to save this as your DESIGN.md? I can lock in these observations as your project's design system baseline."

Phase 3: Page-by-Page Visual Audit

For each page in scope:

$B goto <url>
$B snapshot -i -a -o "$REPORT_DIR/screenshots/{page}-annotated.png"
$B responsive "$REPORT_DIR/screenshots/{page}"
$B console --errors
$B perf

Auth Detection

After the first navigation, check if the URL changed to a login-like path:

$B url

If URL contains /login, /signin, /auth, or /sso: the site requires authentication. AskUserQuestion: "This site requires authentication. Want to import cookies from your browser? Run /setup-browser-cookies first if needed."

Trunk Test (run on every page)

Imagine being dropped on this page with no context. Can you immediately answer:

  1. What site is this? (Site ID visible and identifiable)
  2. What page am I on? (Page name prominent, matches what I clicked)
  3. What are the major sections? (Primary nav visible and clear)
  4. What are my options at this level? (Local nav or content choices obvious)
  5. Where am I in the scheme of things? ("You are here" indicator, breadcrumbs)
  6. How can I search? (Search box findable without hunting)

Score: PASS (all 6 clear) / PARTIAL (4-5 clear) / FAIL (3 or fewer clear). A FAIL on the trunk test is a HIGH-impact finding regardless of how polished the visual design is.

Design Audit Checklist (10 categories, ~80 items)

Apply these at each page. Each finding gets an impact rating (high/medium/polish) and category.

1. Visual Hierarchy & Composition (8 items)

  • Clear focal point? One primary CTA per view?
  • Eye flows naturally top-left to bottom-right?
  • Visual noise — competing elements fighting for attention?
  • Information density appropriate for content type?
  • Z-index clarity — nothing unexpectedly overlapping?
  • Above-the-fold content communicates purpose in 3 seconds?
  • Squint test: hierarchy still visible when blurred?
  • White space is intentional, not leftover?

2. Typography (15 items)

  • Font count <=3 (flag if more)
  • Scale follows ratio (1.25 major third or 1.333 perfect fourth)
  • Line-height: 1.5x body, 1.15-1.25x headings
  • Measure: 45-75 chars per line (66 ideal)
  • Heading hierarchy: no skipped levels (h1→h3 without h2)
  • Weight contrast: >=2 weights used for hierarchy
  • No blacklisted fonts (Papyrus, Comic Sans, Lobster, Impact, Jokerman)
  • If primary font is Inter/Roboto/Open Sans/Poppins → flag as potentially generic
  • text-wrap: balance or text-pretty on headings (check via $B css <heading> text-wrap)
  • Curly quotes used, not straight quotes
  • Ellipsis character (…) not three dots (...)
  • font-variant-numeric: tabular-nums on number columns
  • Body text >= 16px
  • Caption/label >= 12px
  • No letterspacing on lowercase text

3. Color & Contrast (10 items)

  • Palette coherent (<=12 unique non-gray colors)
  • WCAG AA: body text 4.5:1, large text (18px+) 3:1, UI components 3:1
  • Semantic colors consistent (success=green, error=red, warning=yellow/amber)
  • No color-only encoding (always add labels, icons, or patterns)
  • Dark mode: surfaces use elevation, not just lightness inversion
  • Dark mode: text off-white (~#E0E0E0), not pure white
  • Primary accent desaturated 10-20% in dark mode
  • color-scheme: dark on html element (if dark mode present)
  • No red/green only combinations (8% of men have red-green deficiency)
  • Neutral palette is warm or cool consistently — not mixed

4. Spacing & Layout (12 items)

  • Grid consistent at all breakpoints
  • Spacing uses a scale (4px or 8px base), not arbitrary values
  • Alignment is consistent — nothing floats outside the grid
  • Rhythm: related items closer together, distinct sections further apart
  • Border-radius hierarchy (not uniform bubbly radius on everything)
  • Inner radius = outer radius - gap (nested elements)
  • No horizontal scroll on mobile
  • Max content width set (no full-bleed body text)
  • env(safe-area-inset-*) for notch devices
  • URL reflects state (filters, tabs, pagination in query params)
  • Flex/grid used for layout (not JS measurement)
  • Breakpoints: mobile (375), tablet (768), desktop (1024), wide (1440)

5. Interaction States (10 items)

  • Hover state on all interactive elements
  • focus-visible ring present (never outline: none without replacement)
  • Active/pressed state with depth effect or color shift
  • Disabled state: reduced opacity + cursor: not-allowed
  • Loading: skeleton shapes match real content layout
  • Empty states: warm message + primary action + visual (not just "No items.")
  • Error messages: specific + include fix/next step
  • Success: confirmation animation or color, auto-dismiss
  • Touch targets >= 44px on all interactive elements
  • cursor: pointer on all clickable elements
  • Mindless choice audit: every decision point (button, link, dropdown, modal choice) is a mindless click (obvious what happens). If a click requires thought about whether it's the right choice, flag as HIGH.

6. Responsive Design (8 items)

  • Mobile layout makes design sense (not just stacked desktop columns)
  • Touch targets sufficient on mobile (>= 44px)
  • No horizontal scroll on any viewport
  • Images handle responsive (srcset, sizes, or CSS containment)
  • Text readable without zooming on mobile (>= 16px body)
  • Navigation collapses appropriately (hamburger, bottom nav, etc.)
  • Forms usable on mobile (correct input types, no autoFocus on mobile)
  • No user-scalable=no or maximum-scale=1 in viewport meta

7. Motion & Animation (6 items)

  • Easing: ease-out for entering, ease-in for exiting, ease-in-out for moving
  • Duration: 50-700ms range (nothing slower unless page transition)
  • Purpose: every animation communicates something (state change, attention, spatial relationship)
  • prefers-reduced-motion respected (check: $B js "matchMedia('(prefers-reduced-motion: reduce)').matches")
  • No transition: all — properties listed explicitly
  • Only transform and opacity animated (not layout properties like width, height, top, left)

8. Content & Microcopy (8 items)

  • Empty states designed with warmth (message + action + illustration/icon)
  • Error messages specific: what happened + why + what to do next
  • Button labels specific ("Save API Key" not "Continue" or "Submit")
  • No placeholder/lorem ipsum text visible in production
  • Truncation handled (text-overflow: ellipsis, line-clamp, or break-words)
  • Active voice ("Install the CLI" not "The CLI will be installed")
  • Loading states end with … ("Saving…" not "Saving...")
  • Destructive actions have confirmation modal or undo window
  • Happy talk detection: scan for introductory paragraphs that start with "Welcome to..." or tell users how great the site is. If you can hear "blah blah blah", it's happy talk. Flag for removal.
  • Instructions detection: any visible instructions longer than one sentence. If users need to read instructions, the design has failed. Flag the instructions AND the interaction they're compensating for.
  • Happy talk word count: count total visible words on the page. Classify each text block as "useful content" vs "happy talk" (welcome paragraphs, self-congratulatory text, instructions nobody reads). Report: "This page has X words. Y (Z%) are happy talk."

9. AI Slop Detection (10 anti-patterns — the blacklist)

The test: would a human designer at a respected studio ever ship this?

  • Purple/violet/indigo gradient backgrounds or blue-to-purple color schemes
  • The 3-column feature grid: icon-in-colored-circle + bold title + 2-line description, repeated 3x symmetrically. THE most recognizable AI layout.
  • Icons in colored circles as section decoration (SaaS starter template look)
  • Centered everything (text-align: center on all headings, descriptions, cards)
  • Uniform bubbly border-radius on every element (same large radius on everything)
  • Decorative blobs, floating circles, wavy SVG dividers (if a section feels empty, it needs better content, not decoration)
  • Emoji as design elements (rockets in headings, emoji as bullet points)
  • Colored left-border on cards (border-left: 3px solid <accent>)
  • Generic hero copy ("Welcome to [X]", "Unlock the power of...", "Your all-in-one solution for...")
  • Cookie-cutter section rhythm (hero → 3 features → testimonials → pricing → CTA, every section same height)
  • system-ui or -apple-system as the PRIMARY display/body font — the "I gave up on typography" signal. Pick a real typeface.

10. Performance as Design (6 items)

  • LCP < 2.0s (web apps), < 1.5s (informational sites)
  • CLS < 0.1 (no visible layout shifts during load)
  • Skeleton quality: shapes match real content layout, shimmer animation
  • Images: loading="lazy", width/height dimensions set, WebP/AVIF format
  • Fonts: font-display: swap, preconnect to CDN origins
  • No visible font swap flash (FOUT) — critical fonts preloaded

Phase 4: Interaction Flow Review

Walk 2-3 key user flows and evaluate the feel, not just the function:

$B snapshot -i
$B click @e3           # perform action
$B snapshot -D          # diff to see what changed

Evaluate:

  • Response feel: Does clicking feel responsive? Any delays or missing loading states?
  • Transition quality: Are transitions intentional or generic/absent?
  • Feedback clarity: Did the action clearly succeed or fail? Is the feedback immediate?
  • Form polish: Focus states visible? Validation timing correct? Errors near the source?

Narration mode: Narrate the flow in first person. "I click 'Sign Up'... spinner appears... 3 seconds pass... still spinning... I'm getting nervous. Finally the dashboard loads, but where am I? The nav doesn't highlight anything." Name the specific element, its position, its visual weight. If you can't name it specifically, you're not actually experiencing the flow, you're generating platitudes.

Goodwill Reservoir (track across the flow)

As you walk the user flow, maintain a mental goodwill meter (starts at 70/100). These scores are heuristic, not measured. The value is in identifying specific drains and fills, not in the final number.

Subtract points for:

  • Hidden information the user would want (pricing, contact, shipping): subtract 15
  • Format punishment (rejecting valid input like dashes in phone numbers): subtract 10
  • Unnecessary information requests: subtract 10
  • Interstitials, splash screens, forced tours blocking the task: subtract 15
  • Sloppy or unprofessional appearance: subtract 10
  • Ambiguous choices that require thinking: subtract 5 each

Add points for:

  • Top user tasks are obvious and prominent: add 10
  • Upfront about costs and limitations: add 5
  • Saves steps (direct links, smart defaults, autofill): add 5 each
  • Graceful error recovery with specific fix instructions: add 10
  • Apologizes when things go wrong: add 5

Report the final goodwill score with a visual dashboard:

Goodwill: 70 ████████████████████░░░░░░░░░░
  Step 1: Login page        70 → 75  (+5 obvious primary action)
  Step 2: Dashboard          75 → 60  (-15 interstitial tour popup)
  Step 3: Settings           60 → 50  (-10 format punishment on phone)
  Step 4: Billing            50 → 35  (-15 hidden pricing info)
  FINAL: 35/100 ⚠️ CRITICAL UX DEBT

Below 30 = critical UX debt. 30-60 = needs work. Above 60 = healthy. Include the biggest drains and fills as specific findings.

Phase 5: Cross-Page Consistency

Compare screenshots and observations across pages for:

  • Navigation bar consistent across all pages?
  • Footer consistent?
  • Component reuse vs one-off designs (same button styled differently on different pages?)
  • Tone consistency (one page playful while another is corporate?)
  • Spacing rhythm carries across pages?

Phase 6: Compile Report

Output Locations

Local: .soloship/design-reports/design-audit-{domain}-{YYYY-MM-DD}.md

Project-scoped:

SLUG=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" | tr ' ' '-')
mkdir -p "$HOME/.soloship/projects/$SLUG"

Write to: ~/.soloship/projects/{slug}/{user}-{branch}-design-audit-{datetime}.md

Baseline: Write design-baseline.json for regression mode:

{
  "date": "YYYY-MM-DD",
  "url": "<target>",
  "designScore": "B",
  "aiSlopScore": "C",
  "categoryGrades": { "hierarchy": "A", "typography": "B", ... },
  "findings": [{ "id": "FINDING-001", "title": "...", "impact": "high", "category": "typography" }]
}

Scoring System

Dual headline scores:

  • Design Score: {A-F} — weighted average of all 10 categories
  • AI Slop Score: {A-F} — standalone grade with pithy verdict

Per-category grades:

  • A: Intentional, polished, delightful. Shows design thinking.
  • B: Solid fundamentals, minor inconsistencies. Looks professional.
  • C: Functional but generic. No major problems, no design point of view.
  • D: Noticeable problems. Feels unfinished or careless.
  • F: Actively hurting user experience. Needs significant rework.

Grade computation: Each category starts at A. Each High-impact finding drops one letter grade. Each Medium-impact finding drops half a letter grade. Polish findings are noted but do not affect grade. Minimum is F.

Category weights for Design Score:

CategoryWeight
Visual Hierarchy15%
Typography15%
Spacing & Layout15%
Color & Contrast10%
Interaction States10%
Responsive10%
Content Quality10%
AI Slop5%
Motion5%
Performance Feel5%

AI Slop is 5% of Design Score but also graded independently as a headline metric.

Regression Output

When previous design-baseline.json exists or --regression flag is used:

  • Load baseline grades
  • Compare: per-category deltas, new findings, resolved findings
  • Append regression table to report

Design Critique Format

Use structured feedback, not opinions:

  • "I notice..." — observation (e.g., "I notice the primary CTA competes with the secondary action")
  • "I wonder..." — question (e.g., "I wonder if users will understand what 'Process' means here")
  • "What if..." — suggestion (e.g., "What if we moved search to a more prominent position?")
  • "I think... because..." — reasoned opinion (e.g., "I think the spacing between sections is too uniform because it doesn't create hierarchy")

Tie everything to user goals and product objectives. Always suggest specific improvements alongside problems.

Important Rules

  1. Think like a designer, not a QA engineer. You care whether things feel right, look intentional, and respect the user. You do NOT just care whether things "work."
  2. Screenshots are evidence. Every finding needs at least one screenshot. Use annotated screenshots (snapshot -a) to highlight elements.
  3. Be specific and actionable. "Change X to Y because Z" — not "the spacing feels off."
  4. Never read source code. Evaluate the rendered site, not the implementation. (Exception: offer to write DESIGN.md from extracted observations.)
  5. AI Slop detection is your superpower. Most developers can't evaluate whether their site looks AI-generated. You can. Be direct about it.
  6. Quick wins matter. Always include a "Quick Wins" section — the 3-5 highest-impact fixes that take <30 minutes each.
  7. Use snapshot -C for tricky UIs. Finds clickable divs that the accessibility tree misses.
  8. Responsive is design, not just "not broken." A stacked desktop layout on mobile is not responsive design — it's lazy. Evaluate whether the mobile layout makes design sense.
  9. Document incrementally. Write each finding to the report as you find it. Don't batch.
  10. Depth over breadth. 5-10 well-documented findings with screenshots and specific suggestions > 20 vague observations.
  11. Show screenshots to the user. After every $B screenshot, $B snapshot -a -o, or $B responsive command, use the Read tool on the output file(s) so the user can see them inline. For responsive (3 files), Read all three. This is critical — without it, screenshots are invisible to the user.

Design Hard Rules

Classifier — determine rule set before evaluating:

  • MARKETING/LANDING PAGE (hero-driven, brand-forward, conversion-focused) → apply Landing Page Rules
  • APP UI (workspace-driven, data-dense, task-focused: dashboards, admin, settings) → apply App UI Rules
  • HYBRID (marketing shell with app-like sections) → apply Landing Page Rules to hero/marketing sections, App UI Rules to functional sections

Hard rejection criteria (instant-fail patterns — flag if ANY apply):

  1. Generic SaaS card grid as first impression
  2. Beautiful image with weak brand
  3. Strong headline with no clear action
  4. Busy imagery behind text
  5. Sections repeating same mood statement
  6. Carousel with no narrative purpose
  7. App UI made of stacked cards instead of layout

Litmus checks (answer YES/NO for each — used for cross-model consensus scoring):

  1. Brand/product unmistakable in first screen?
  2. One strong visual anchor present?
  3. Page understandable by scanning headlines only?
  4. Each section has one job?
  5. Are cards actually necessary?
  6. Does motion improve hierarchy or atmosphere?
  7. Would design feel premium with all decorative shadows removed?

Landing page rules (apply when classifier = MARKETING/LANDING):

  • First viewport reads as one composition, not a dashboard
  • Brand-first hierarchy: brand > headline > body > CTA
  • Typography: expressive, purposeful — no default stacks (Inter, Roboto, Arial, system)
  • No flat single-color backgrounds — use gradients, images, subtle patterns
  • Hero: full-bleed, edge-to-edge, no inset/tiled/rounded variants
  • Hero budget: brand, one headline, one supporting sentence, one CTA group, one image
  • No cards in hero. Cards only when card IS the interaction
  • One job per section: one purpose, one headline, one short supporting sentence
  • Motion: 2-3 intentional motions minimum (entrance, scroll-linked, hover/reveal)
  • Color: define CSS variables, avoid purple-on-white defaults, one accent color default
  • Copy: product language not design commentary. "If deleting 30% improves it, keep deleting"
  • Beautiful defaults: composition-first, brand as loudest text, two typefaces max, cardless by default, first viewport as poster not document

App UI rules (apply when classifier = APP UI):

  • Calm surface hierarchy, strong typography, few colors
  • Dense but readable, minimal chrome
  • Organize: primary workspace, navigation, secondary context, one accent
  • Avoid: dashboard-card mosaics, thick borders, decorative gradients, ornamental icons
  • Copy: utility language — orientation, status, action. Not mood/brand/aspiration
  • Cards only when card IS the interaction
  • Section headings state what area is or what user can do ("Selected KPIs", "Plan status")

Universal rules (apply to ALL types):

  • Define CSS variables for color system
  • No default font stacks (Inter, Roboto, Arial, system)
  • One job per section
  • "If deleting 30% of the copy improves it, keep deleting"
  • Cards earn their existence — no decorative card grids
  • NEVER use small, low-contrast type (body text < 16px or contrast ratio < 4.5:1 on body text)
  • NEVER put labels inside form fields as the only label (placeholder-as-label pattern — labels must be visible when the field has content)
  • ALWAYS preserve visited vs unvisited link distinction (visited links must have a different color)
  • NEVER float headings between paragraphs (heading must be visually closer to the section it introduces than to the preceding section)

AI Slop blacklist (the 10 patterns that scream "AI-generated"):

  1. Purple/violet/indigo gradient backgrounds or blue-to-purple color schemes
  2. The 3-column feature grid: icon-in-colored-circle + bold title + 2-line description, repeated 3x symmetrically. THE most recognizable AI layout.
  3. Icons in colored circles as section decoration (SaaS starter template look)
  4. Centered everything (text-align: center on all headings, descriptions, cards)
  5. Uniform bubbly border-radius on every element (same large radius on everything)
  6. Decorative blobs, floating circles, wavy SVG dividers (if a section feels empty, it needs better content, not decoration)
  7. Emoji as design elements (rockets in headings, emoji as bullet points)
  8. Colored left-border on cards (border-left: 3px solid <accent>)
  9. Generic hero copy ("Welcome to [X]", "Unlock the power of...", "Your all-in-one solution for...")
  10. Cookie-cutter section rhythm (hero → 3 features → testimonials → pricing → CTA, every section same height)
  11. system-ui or -apple-system as the PRIMARY display/body font — the "I gave up on typography" signal. Pick a real typeface.

Source: OpenAI "Designing Delightful Frontends with GPT-5.4" (Mar 2026) + Soloship design methodology.

Record baseline design score and AI slop score at end of Phase 6.

Output Structure

~/.soloship/projects/$SLUG/designs/design-audit-{YYYYMMDD}/
├── design-audit-{domain}.md                  # Structured report
├── screenshots/
│   ├── first-impression.png                  # Phase 1
│   ├── {page}-annotated.png                  # Per-page annotated
│   ├── {page}-mobile.png                     # Responsive
│   ├── {page}-tablet.png
│   ├── {page}-desktop.png
│   ├── finding-001-before.png                # Before fix
│   ├── finding-001-target.png                # Target mockup (if generated)
│   ├── finding-001-after.png                 # After fix
│   └── ...
└── design-baseline.json                      # For regression mode

Design Outside Voices (parallel)

Automatic: Outside voices run automatically when Codex is available. No opt-in needed.

<!-- concern:delegation-discipline -->

This skill's mandated dispatches are the ceiling, not the floor — run the dispatches it names, and do not add discretionary subagents on top (no extra verification or review dispatches, no splitting one modest task across parallel workers); see references/delegation-discipline.md.

Check Codex availability:

which codex 2>/dev/null && echo "CODEX_AVAILABLE" || echo "CODEX_NOT_AVAILABLE"

If Codex is available, launch both voices simultaneously:

  1. Codex design voice (via Bash):
TMPERR_DESIGN=$(mktemp /tmp/codex-design-XXXXXXXX)
_REPO_ROOT=$(git rev-parse --show-toplevel) || { echo "ERROR: not in a git repo" >&2; exit 1; }
codex exec "Review the frontend source code in this repo. Evaluate against these design hard rules:
- Spacing: systematic (design tokens / CSS variables) or magic numbers?
- Typography: expressive purposeful fonts or default stacks?
- Color: CSS variables with defined system, or hardcoded hex scattered?
- Responsive: breakpoints defined? calc(100svh - header) for heroes? Mobile tested?
- A11y: ARIA landmarks, alt text, contrast ratios, 44px touch targets?
- Motion: 2-3 intentional animations, or zero / ornamental only?
- Cards: used only when card IS the interaction? No decorative card grids?

First classify as MARKETING/LANDING PAGE vs APP UI vs HYBRID, then apply matching rules.

LITMUS CHECKS — answer YES/NO:
1. Brand/product unmistakable in first screen?
2. One strong visual anchor present?
3. Page understandable by scanning headlines only?
4. Each section has one job?
5. Are cards actually necessary?
6. Does motion improve hierarchy or atmosphere?
7. Would design feel premium with all decorative shadows removed?

HARD REJECTION — flag if ANY apply:
1. Generic SaaS card grid as first impression
2. Beautiful image with weak brand
3. Strong headline with no clear action
4. Busy imagery behind text
5. Sections repeating same mood statement
6. Carousel with no narrative purpose
7. App UI made of stacked cards instead of layout

Be specific. Reference file:line for every finding." -C "$_REPO_ROOT" -s read-only -c 'model_reasoning_effort="high"' --enable web_search_cached < /dev/null 2>"$TMPERR_DESIGN"

Use a 5-minute timeout (timeout: 300000). After the command completes, read stderr:

cat "$TMPERR_DESIGN" && rm -f "$TMPERR_DESIGN"
  1. Claude design subagent (via Agent tool): Dispatch a subagent with this prompt: "Review the frontend source code in this repo. You are an independent senior product designer doing a source-code design audit. Focus on CONSISTENCY PATTERNS across files rather than individual violations:
  • Are spacing values systematic across the codebase?
  • Is there ONE color system or scattered approaches?
  • Do responsive breakpoints follow a consistent set?
  • Is the accessibility approach consistent or spotty?

For each finding: what's wrong, severity (critical/high/medium), and the file:line."

Error handling (all non-blocking):

  • Auth failure: If stderr contains "auth", "login", "unauthorized", or "API key": "Codex authentication failed. Run codex login to authenticate."
  • Timeout: "Codex timed out after 5 minutes."
  • Empty response: "Codex returned no response."
  • On any Codex error: proceed with Claude subagent output only, tagged [single-model].
  • If Claude subagent also fails: "Outside voices unavailable — continuing with primary review."

Present Codex output under a CODEX SAYS (design source audit): header. Present subagent output under a CLAUDE SUBAGENT (design consistency): header.

Synthesis — Litmus scorecard:

Use the same scorecard format as /plan-design-review (shown above). Fill in from both outputs. Merge findings into the triage with [codex] / [subagent] / [cross-model] tags.

Log the result: Replace STATUS with "clean" or "issues_found", SOURCE with "codex+subagent", "codex-only", "subagent-only", or "unavailable".

Phase 7: Triage

Sort all discovered findings by impact, then decide which to fix:

  • High Impact: Fix first. These affect the first impression and hurt user trust.
  • Medium Impact: Fix next. These reduce polish and are felt subconsciously.
  • Polish: Fix if time allows. These separate good from great.

Mark findings that cannot be fixed from source code (e.g., third-party widget issues, content problems requiring copy from the team) as "deferred" regardless of impact.

Phase 8: Fix Loop

For each fixable finding, in impact order:

8a. Locate source

# Search for CSS classes, component names, style files
# Glob for file patterns matching the affected page
  • Find the source file(s) responsible for the design issue
  • ONLY modify files directly related to the finding
  • Prefer CSS/styling changes over structural component changes

8a.5. Target Mockup (if DESIGN_READY)

If the Soloship designer is available and the finding involves visual layout, hierarchy, or spacing (not just a CSS value fix like wrong color or font-size), generate a target mockup showing what the corrected version should look like:

$D generate --brief "<description of the page/component with the finding fixed, referencing DESIGN.md constraints>" --output "$REPORT_DIR/screenshots/finding-NNN-target.png"

Show the user: "Here's the current state (screenshot) and here's what it should look like (mockup). Now I'll fix the source to match."

This step is optional — skip for trivial CSS fixes (wrong hex color, missing padding value). Use it for findings where the intended design isn't obvious from the description alone.

8b. Fix

  • Read the source code, understand the context
  • Make the minimal fix — smallest change that resolves the design issue
  • If a target mockup was generated in 8a.5, use it as the visual reference for the fix
  • CSS-only changes are preferred (safer, more reversible)
  • Do NOT refactor surrounding code, add features, or "improve" unrelated things

8c. Commit

git add <only-changed-files>
git commit -m "style(design): FINDING-NNN — short description"
  • One commit per fix. Never bundle multiple fixes.
  • Message format: style(design): FINDING-NNN — short description

8d. Re-test

Navigate back to the affected page and verify the fix:

$B goto <affected-url>
$B screenshot "$REPORT_DIR/screenshots/finding-NNN-after.png"
$B console --errors
$B snapshot -D

Take before/after screenshot pair for every fix.

8e. Classify

  • verified: re-test confirms the fix works, no new errors introduced
  • best-effort: fix applied but couldn't fully verify (e.g., needs specific browser state)
  • reverted: regression detected → git revert HEAD → mark finding as "deferred"

8e.5. Regression Test (design-review variant)

Design fixes are typically CSS-only. Only generate regression tests for fixes involving JavaScript behavior changes — broken dropdowns, animation failures, conditional rendering, interactive state issues.

For CSS-only fixes: skip entirely. CSS regressions are caught by re-running /design-review.

If the fix involved JS behavior: follow the same procedure as /qa Phase 8e.5 (study existing test patterns, write a regression test encoding the exact bug condition, run it, commit if passes or defer if fails). Commit format: test(design): regression test for FINDING-NNN.

8f. Self-Regulation (stop and evaluate)

Every 5 fixes (or after any revert), compute the design-fix risk level:

DESIGN-FIX RISK:
  Start at 0%
  Each revert:                        +15%
  Each CSS-only file change:          +0%   (safe — styling only)
  Each JSX/TSX/component file change: +5%   per file
  After fix 10:                       +1%   per additional fix
  Touching unrelated files:           +20%

If risk > 20%: stop immediately. Show the user what you've done so far. Ask whether to continue.

Hard cap: 30 fixes. After 30 fixes, stop regardless of remaining findings.

Phase 9: Final Design Audit

After all fixes are applied:

  1. Re-run the design audit on all affected pages
  2. If target mockups were generated during the fix loop AND DESIGN_READY: run $D verify --mockup "$REPORT_DIR/screenshots/finding-NNN-target.png" --screenshot "$REPORT_DIR/screenshots/finding-NNN-after.png" to compare the fix result against the target. Include pass/fail in the report.
  3. Compute final design score and AI slop score
  4. If final scores are WORSE than baseline: WARN prominently — something regressed

Phase 10: Report

Write the report to $REPORT_DIR (already set up in the setup phase):

Primary: $REPORT_DIR/design-audit-{domain}.md

Also write a summary to the project index:

SLUG=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" | tr ' ' '-')
mkdir -p "$HOME/.soloship/projects/$SLUG"

Write a one-line summary to ~/.soloship/projects/{slug}/{user}-{branch}-design-audit-{datetime}.md with a pointer to the full report in $REPORT_DIR.

Per-finding additions (beyond standard design audit report):

  • Fix Status: verified / best-effort / reverted / deferred
  • Commit SHA (if fixed)
  • Files Changed (if fixed)
  • Before/After screenshots (if fixed)

Summary section:

  • Total findings
  • Fixes applied (verified: X, best-effort: Y, reverted: Z)
  • Deferred findings
  • Design score delta: baseline → final
  • AI slop score delta: baseline → final

PR Summary: Include a one-line summary suitable for PR descriptions:

"Design review found N issues, fixed M. Design score X → Y, AI slop score X → Y."

Phase 11: TODOS.md Update

If the repo has a TODOS.md:

  1. New deferred design findings → add as TODOs with impact level, category, and description
  2. Fixed findings that were in TODOS.md → annotate with "Fixed by /design-review on {branch}, {date}"

Additional Rules (design-review specific)

  1. Clean working tree required. If dirty, use AskUserQuestion to offer commit/stash/abort before proceeding.
  2. One commit per fix. Never bundle multiple design fixes into one commit.
  3. Only modify tests when generating regression tests in Phase 8e.5. Never modify CI configuration. Never modify existing tests — only create new test files.
  4. Revert on regression. If a fix makes things worse, git revert HEAD immediately.
  5. Self-regulate. Follow the design-fix risk heuristic. When in doubt, stop and ask.
  6. CSS-first. Prefer CSS/styling changes over structural component changes. CSS-only changes are safer and more reversible.
  7. DESIGN.md export. You MAY write a DESIGN.md file if the user accepts the offer from Phase 2.

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.