skills/product/design-review/SKILL.md
Visual design and UI consistency review — design system adherence, spacing tokens, typography, color usage, component patterns, and responsive polish. Use when: "design critique", "polish the UI", "design system adherence", "responsive design", "visual polish", "review the design", "UI inconsistency"
npx skillsauth add mikeparcewski/wicked-garden design-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Deep visual design and UI implementation review.
Visual Consistency:
Component Patterns:
Responsive Design:
Visual Polish:
Full review criteria: See Visual Consistency, Components & Responsive, and Accessibility & Scoring
# Scan for components
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/product/component-inventory.py" src/
# Find patterns
wicked-garden:search "className=" --type jsx
wicked-garden:search "styled\." --type ts
# Find hardcoded colors (violations)
wicked-garden:search "#[0-9a-fA-F]{3,6}" --type css
# Find magic number spacing
wicked-garden:search "[0-9]+px" --type css
| Category | Score | Notes | |----------|-------|-------| | Colors | {✓⚠✗} | {brief note} | | Typography | {✓⚠✗} | {brief note} | | Spacing | {✓⚠✗} | {brief note} | | Components | {✓⚠✗} | {brief note} | | Responsive | {✓⚠✗} | {brief note} |
Scoring guide: See refs/scoring-guide-methodology.md and refs/scoring-guide-examples.md
❌ Hardcoded colors: `color: #3b82f6` vs `color: var(--primary)`
❌ Magic numbers: `margin: 17px` vs `margin: var(--space-4)`
❌ Missing states: No `:hover` or `:focus` styles
❌ Non-responsive: Fixed widths without media queries
❌ Component duplication: Multiple similar button implementations
❌ Inaccessible contrast: Light gray on white
Fix examples: See Color Issues, Component Issues, Animation Issues
## Design Review
**Consistency**: {✓ Ship it | ⚠ Minor issues | ✗ Needs work}
### Component Inventory
- Buttons: {count}
- Inputs: {count}
- Cards: {count}
### Issues
#### Critical
- {Issue breaking design}
- Location: {file:line}
- Fix: {code change}
#### Major
- {Inconsistency}
- Location: {file:line}
- Recommendation: {improvement}
### Recommendations
1. {High-priority fix}
2. {Design system improvement}
Full report template: See refs/report-template-findings.md and refs/report-template-actions.md
If project has a design system:
If no design system:
Design system guide: See Tokens & Foundations, Components, Governance
Fast improvements with high impact:
Implementation guide: See Quick Wins 1-5, Quick Wins 6-10, and Workflow & Planning
Tools:
# Screenshots: Use the Read tool on a screenshot file, or capture via browser automation if available.
# Color contrast
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/product/contrast-check.py" "#666" "#fff"
# Track design debt via native TaskCreate
# TaskCreate(
# subject="UI: {issue}",
# metadata={
# "event_type": "task",
# "chain_id": "design-review.root",
# "source_agent": "design-review",
# "priority": "P2"
# }
# )
Collaboration:
Detailed guides in refs/:
development
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
tools
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
development
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
tools
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).