forcedotcom/sf-skills / skills/experience-design-validate
experience-design-validate
VerifiedUse this skill to run a visual-craft audit of a rendered UI and produce an evidence-grounded Craft Report across Useful, Usable, Reliable, Coherent, and Well-Crafted. Invoke it for craft audits, visual critiques, design comparisons, felt-quality reviews, or visual-craft readiness checks on screenshots (.png, .jpg, .jpeg, .webp, .gif), Figma frames, rendered prototypes, and live URLs. Do not use it for source-code review, SLDS compliance (use design-systems-slds-validate), or accessibility compliance (use experience-accessibility-validate).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.2 KB |
| references/ai.md | markdown | 4.4 KB |
| references/components.md | markdown | 6.1 KB |
| references/craft.md | markdown | 10.9 KB |
| references/data.md | markdown | 5.4 KB |
| references/forms-flows.md | markdown | 4.8 KB |
| references/interaction.md | markdown | 4.4 KB |
| references/navigation.md | markdown | 4.1 KB |
| references/performance.md | markdown | 5.0 KB |
| references/records.md | markdown | 4.8 KB |
| references/responsive.md | markdown | 3.9 KB |
| references/scoring-rubric.md | markdown | 14.1 KB |
| references/state.md | markdown | 4.4 KB |
| references/trust.md | markdown | 3.7 KB |
| references/usability.md | markdown | 3.1 KB |
| references/visual-system.md | markdown | 11.0 KB |
references/usability.md
View on GitHub# Usability
> **Skip this reference if the design has no decisions to make, no actions to take, and no flow to navigate — i.e. nothing for craft to make smoother.**
Usability craft is the difference between a product that you operate and one that operates with you. It's the visible system status that tells you the save went through, the predictable interaction that lets you trust your muscle memory, the consistent pattern that makes the second use easier than the first. Good usability craft is invisible when it works — you just feel competent. Poor usability craft makes you feel stupid for not knowing where the controls are.
## Why this matters
Designs win or lose on the small moments of feedback and predictability. When a click produces an immediate visible response, when a state change is announced through motion or color, when consistent patterns mean the user never has to relearn — the product feels responsive and trustworthy. When those moments are missing, every interaction carries doubt: did it work, am I in the right place, is this the same control I used yesterday. Craft here is about respect — respecting the user's time, attention, and prior learning by making the system answer back when spoken to.
---
## Feedback and Predictability
- **The system answers back when spoken to.** Every action produces a visible response — a state change, a confirmation, a transition — within the moment of the click. Silence reads as broken.
- **Patterns repeat.** The same kind of action looks and behaves the same across the product. When a "save" feels different on two screens, the user has to relearn instead of trust their muscle memory.
- **The user's place in the system is always visible.** Where they are, what's selected, what they just did. A page that wipes context after every interaction asks the user to rebuild it constantly.
- **Edges are designed.** Empty states, errors, loading, and success all feel like part of the same product — not afterthoughts grafted onto the happy path.
- **Hierarchy matches priority.** What's important looks important. When secondary actions outweigh primary ones visually, the user has to fight the design to do the right thing.
- **Interactive elements look interactive.** A button that looks like a label, a link that looks like static text, a card that hides a click target — each forces the user to discover by trial.
- **Simpler is preferred when both work.** Two controls where one would do, three options where two cover the cases — the extras add cognitive load without adding capability.
---
## Scoring Guide
**Contributes to dimensions: Usable, Useful, Well-Crafted**
| Score | Criteria |
|-------|----------|
| 9-10 | Edges are designed. Interactive elements look interactive. Hierarchy matches priority. The product responds to every input with visible craft. |
| 7-8 | Most flows feel responsive and predictable. Minor gaps in edge-state polish. |
| 5-6 | Happy path is fine; edges feel unfinished. Some controls don't feel interactive. |
| 3-4 | Inconsistent feedback. Edge states neglected. Hierarchy fights the user. |
| 1-2 | No visible system response. Interactions feel unanswered. |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |