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/trust.md
View on GitHub# Trust & Safety
> **Skip this reference if the design shows no auth surfaces, no privacy controls, no permission UI, no destructive settings, and no risk-bearing actions.**
Craft in trust surfaces is the visual proof that a product takes consequences seriously. It shows up in the placement of a verification icon, the elevation of a danger zone, the restraint of a sensitive-data mask, the calibrated visual weight of a warning versus a critical confirmation. This reference judges the visual treatment of trust signals, the staging of authentication, and the progressive elevation of risk surfaces.
## Why this matters
Trust is a felt quality, not a feature — and craft is what makes a user feel safe before they read any copy. When craft is high, sensitive moments feel deliberate: the lock icon sits where the eye expects it, the danger zone is visually quarantined from the rest of the settings, warnings escalate in visual weight as stakes increase, and confirmations carry the right amount of friction without theatrics. When craft is low, trust surfaces feel either gaudy (every action a red banner) or careless (a destructive button styled like a save button). The visual register of risk is something users absorb subconsciously — a misstep here is the difference between confidence and unease.
---
## Trust Signals
- **Visual polish is itself a trust signal.** Misaligned elements, mismatched typography, and broken layouts read as carelessness with everything else — including the user's data.
- **Verification indicators sit where the eye expects them.** A single recognizable icon, placed consistently across the product, with a quiet explanation on hover.
- **Sensitive data is masked by default.** A visibility toggle returns it on demand. Showing a credit card number or a phone number unprompted reads as careless.
## Authentication
- **Login is staged, not stuffed.** Identity first, credential second. A single mega-form for everything reads as bureaucratic.
- **Password fields are forgiving.** A show/hide toggle and live validation reduce the anxiety of typing into a black box.
## Consent
- **Cookie banners don't trap the user.** Dismissing without accepting is as easy as accepting. "Essential only" carries the same visual weight as "Accept all." A banner that blocks content until the user accepts reads as coercive.
## Risk Communication
- **Severity escalates with consequence.** Informational notes, cautionary highlights, warnings that pause the user, and critical confirmations that demand typing — each carries a distinct visual weight. When everything is the same shade of red, nothing reads as urgent.
- **Warnings appear before the point of no return.** Not after, not during — before. A warning that arrives after the action committed is theater.
- **The same severity treatment is never used for unequal risks.** When archiving and deleting wear the same warning, the user stops trusting the warnings.
- **Destructive settings are visually quarantined.** A "danger zone" set apart from ordinary settings — not interleaved with everyday toggles where a misclick is one row away.
---
## Scoring Guide
**Contributes to dimensions: Reliable, Coherent, Well-Crafted**
| Score | Criteria |
|-------|----------|
| 9-10 | Trust is earned through every interaction. Sensitive moments feel deliberate. Risk is calibrated. The danger zone is unmistakable. |
| 7-8 | Trust patterns are mostly consistent with minor gaps in disclosure or symmetry. |
| 5-6 | Bundled consent. Inconsistent warning severity. A few dark patterns. |
| 3-4 | Dark patterns. Invasive defaults. The product feels indifferent to consequence. |
| 1-2 | Trust is actively broken. Hidden data collection. Misleading consent. |
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 |