forcedotcom/sf-skills is a collection of reusable instructions that help AI coding agents build and work with Salesforce applications and platform features. Developers use it for Agentforce agents, Lightning apps, Flow, Apex, SOQL, Lightning Web Components, and related Salesforce configuration. The catalogue entries are the repository’s skills, plugins, commands, MCP servers, and agents for AI tools that support skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add forcedotcom/sf-skills --skill experience-design-validategit clone --depth 1 https://github.com/forcedotcom/sf-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/forcedotcom/sf-skills/experience-design-validate)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/experience-design-validate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/experience-design-validate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/experience-design-validate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/experience-design-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00127 | $0.02364 |
| Opus 5.5 | $0.00051 | $0.00946 |
| Sonnet 5.5 | $0.00025 | $0.00473 |
| Haiku 4.5 | $0.00013 | $0.00236 |
Grade A, and why
experience-design-validate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experience Design Validate
Evaluate the visual craft of rendered software: what the eye sees and the felt quality those visible decisions create. Judge relationships, hierarchy, restraint, consistency, and care rather than CSS, tokens, or implementation technique.
This is a visual-craft-only audit. It does not establish WCAG conformance, keyboard or screen-reader support, behavioral usability, implementation quality, or production release readiness. Route accessibility compliance to experience-accessibility-validate and SLDS compliance to design-systems-slds-validate.
Use and boundaries
Use this skill to:
- Critique visual craft at a design checkpoint.
- Explain why a rendered design feels considered, cramped, calm, fragmented, or delightful.
- Compare the craft of two or more designs solving the same brief.
- Identify design moves that would lift a visible experience from good to great.
Do not use this skill for:
- Implementation or code review. For LWC generation or security review, use
experience-lwc-generateorexperience-lwc-security-validateas appropriate. - Accessibility compliance, including WCAG, screen-reader, keyboard, or focus-order validation. Use
experience-accessibility-validate. - SLDS design-token compliance. Use
design-systems-slds-validate. - Claims about real-user behavior. Recommend a usability study when impact depends on behavior rather than visible evidence.
Visual evidence contract
Rendered pixels are mandatory. Prefer screenshots because they preserve the exact evidence reviewed.
- Screenshots: use supplied full-page or region captures directly.
- Live URL: if browser capability is available, open the URL, exercise only the relevant paths, capture screenshots, and retain the URL and viewport as evidence. Otherwise ask for screenshots.
- Figma: if Figma capability is available, fetch or export the named rendered frames. Treat a frame as static unless prototype behavior is actually exercised. Otherwise ask for frame exports or screenshots.
- Screen recording or interactive prototype: inspect observable transitions and capture representative frames when tooling supports it.
- Source code, design descriptions, or inaccessible links: do not infer the rendered result. Render with available capability; otherwise request screenshots.
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/ai.md 4.4 KB
- references/components.md 6.1 KB
- references/craft.md 11 KB
- references/data.md 5.4 KB
- references/forms-flows.md 4.8 KB
- references/interaction.md 4.4 KB
- references/navigation.md 4.1 KB
- references/performance.md 5.0 KB
- references/records.md 4.8 KB
- references/responsive.md 3.9 KB
- references/scoring-rubric.md 14 KB
- references/state.md 4.4 KB
- references/trust.md 3.7 KB
- references/usability.md 3.1 KB
- references/visual-system.md 11 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 164 lines · 127 tokens per session scan A 2377e4e45190
experience-design-validate is a skill published in the GitHub repository forcedotcom/sf-skills (1,097 stars, last pushed today), licensed Apache-2.0. It adds 127 tokens to every session and 2,364 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-16.
Other skills, from other repositories
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.