skills/product/ux-review/SKILL.md
Use when evaluating UX quality — user flows, information architecture, user research synthesis, personas, and usability assessment. Also covers generative UX flow design from requirements. NOT for visual design consistency (use visual-review) or accessibility code audits (use product/accessibility).
npx skillsauth add mikeparcewski/wicked-garden wicked-garden-product-ux-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.
UX and design quality thinking embedded throughout delivery.
Tier-3 knowledge module behind the
ux-reviewaction of thewicked-garden-productdomain skill (skills/product/SKILL.md). Canonical invocation:/wicked-garden-product ux-review [args]or plain natural language — the examples below use that form.
Good UX is how we build trust. Don't wait for polish phase—design with users in mind from the start.
| Area | Expert | Focus | |------|--------|-------| | User Flows | UX Designer | Experience design, interactions, IA | | Visual Design | UI Reviewer | Consistency, components, design system | | Accessibility | A11y Expert | WCAG, keyboard, screen readers | | User Research | User Researcher | Needs, personas, journeys |
| Command | Purpose |
|---------|---------|
| /wicked-garden-product ux-review | Run UX review (auto-detect focus) |
| /wicked-garden-product ux-review --focus flows | User flow analysis |
| /wicked-garden-product ux-review --focus ui | Visual design review |
| /wicked-garden-product ux-review --focus a11y | Accessibility audit |
| /wicked-garden-product ux-review --focus research | User research |
| /wicked-garden-product ux-review --focus all | Comprehensive review |
# Auto-detect what to review
/wicked-garden-product ux-review src/components/Dashboard
# Focus on accessibility
/wicked-garden-product ux-review src/components/Form --focus a11y
# User research on requirements
/wicked-garden-product ux-review outcome.md --focus research
# Comprehensive review
/wicked-garden-product ux-review src/app --focus all
# Quick triage
/wicked-garden-product ux-review src/components --quick
Review produces:
Works with:
metadata.event_type="task"| Phase | Suggested Review | Expert | |-------|------------------|--------| | Clarify | User research | User Researcher | | Design | User flows + IA | UX Designer | | Build | A11y + UI consistency | A11y Expert + UI Reviewer | | Review | Comprehensive review | All experts |
For fast feedback:
# Quick a11y scan
/wicked-garden-product ux-review {file} --focus a11y --quick
# Quick UI consistency
/wicked-garden-product ux-review {file} --focus ui --quick
# Quick flow check
/wicked-garden-product ux-review {file} --focus flows --quick
UX: Unclear flows, missing error states, confusing navigation UI: Color/typography/spacing inconsistencies, missing states A11y: Missing alt text, poor contrast, no keyboard access Research: Assumed needs, missing personas, unmapped journeys
ux-review.md - Findings and recommendationspersonas/, journeys/ - Research artifactsa11y-report.md - Accessibility resultsmetadata.event_type="task")# Comprehensive quick review
/wicked-garden-product ux-review src/ --focus all --quick
# Accessibility deep dive
/wicked-garden-product ux-review src/components --focus a11y
# User research
/wicked-garden-product ux-review outcome.md --focus research
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).