| name | design-systems-slds-apply |
| description | Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include "build a modal", "create a form", "data table", "SLDS styling", "style with hooks", "add an icon". |
| metadata | {"version":"1.0"} |
Applying SLDS
The Salesforce Lightning Design System (SLDS) is a CSS framework with thousands of artifacts. This skill teaches agents how to find and correctly use them.
Version: This skill targets SLDS v2. Legacy --lwc-* tokens and slds-*--modifier syntax are deprecated.
Audit scope: The companion design-systems-slds-validate skill analyzer only scans .css, .html, and .js files. Use it directly for LWC and similar HTML/CSS/JS components; treat it as a partial signal for JSX/TSX or other framework-specific template formats and supplement with manual review.
What is SLDS?
| Artifact | Count | Description |
|---|
| Lightning Base Components | ~70 | Pre-built LWC components (LWC only) |
| SLDS Blueprints | 85 | CSS/HTML patterns for any framework |
| Styling Hooks | 523 | CSS custom properties (--slds-g-*) for theming |
| Utility Classes | 1,147 | Rapid styling classes for spacing, layout, visibility |
| Icons | 1,732 | SVG icons across 5 categories |
Scope
This skill covers:
- Which blueprint to use for a given UI pattern
- How to style with hooks (color, spacing, typography, shadows, borders)
- Which utility classes to use for layout, spacing, visibility
- Which icon to use and from which category
- SLDS naming conventions, class structure, hook syntax
This skill includes basic accessibility reminders (icon alt text, focus outlines, color-not-sole-indicator) in the validation checklists. Full WCAG compliance requires a dedicated accessibility review.
This skill does NOT cover (use companion skills):
- Design decisions -- visual hierarchy, composition, interaction patterns
- LWC mechanics -- component structure, @wire, @api, lifecycle, events (not yet available)
- Full accessibility -- WCAG conformance, ARIA patterns, keyboard navigation, focus management, contrast ratios (not yet available)
Component Selection Hierarchy
Always follow this order:
1. Lightning Base Components (LWC only) ← Check first
2. SLDS Blueprints (any framework) ← Use exact SLDS classes
3. Custom with Styling Hooks ← Use var(--slds-g-*)
4. Custom CSS (last resort) ← Still use hooks for values
If building in LWC, check for an LBC first: Lightning Component Library
If no LBC exists (or not using LWC), select an SLDS Blueprint. See references/component-selection.md.
Core Rules
Do
- Follow the selection hierarchy: LBC > Blueprint > Hooks > Custom CSS
- Use
var(--slds-g-*, fallback) for all themeable values
- Create custom classes (
my-*, c-*) instead of overriding .slds-*
- Verify every hook, class, and utility exists before using it — run the search scripts; never assume an artifact exists based on naming patterns (see Verify Before You Use)
- Pair surface colors with on-surface colors for text
- Provide
alternative-text on every <lightning-icon>
Don't
- Hard-code colors, spacing, or typography values
- Override
.slds-* classes directly
- Use deprecated
--lwc-* tokens as primary values
- Use
--slds-s-* (shared) hooks -- they are private/internal
- Reassign hook values -- only reference them with
var()
- Use color alone to convey meaning
- Invent hook names by interpolating patterns from other families (see Naming Traps below)
Hook Naming Traps
SLDS hook families do NOT all follow the same naming pattern. Agents frequently invent hooks that don't exist by assuming {prefix}-{number} works universally. Always verify a hook exists via the bundled search-hooks.cjs script or metadata/hooks-index.json before using it.
Trap 1: Font size hooks are NOT numbered
| Wrong (does not exist) | Correct | Notes |
|---|
--slds-g-font-size-3 | --slds-g-font-scale-1 | Font sizes use font-scale-*, not font-size-* |
--slds-g-font-size-4 | --slds-g-font-scale-2 | Only --slds-g-font-size-base exists (base size) |
--slds-g-font-size-8 | --slds-g-font-scale-6 | Scale goes: neg-4 through 10 |
Rule: For font sizes, use --slds-g-font-size-base (the one base size) or --slds-g-font-scale-* (the numbered scale). Never --slds-g-font-size-N.
Trap 2: Color hooks always require a number
| Wrong (does not exist) | Correct | Notes |
|---|
--slds-g-color-on-surface | --slds-g-color-on-surface-2 | All color hooks need a number |
--slds-g-color-on-accent | --slds-g-color-on-accent-1 | Pick 1/2/3 by emphasis level |
--slds-g-color-surface | --slds-g-color-surface-1 | No unnumbered base form |
Rule: Every --slds-g-color-* hook ends in a number. Pick by emphasis: -1 (low), -2 (medium), -3 (high).
Trap 3: Not all values have hook equivalents
Some CSS values (e.g., min-width: 7rem for label alignment) have no SLDS hook. This is acceptable:
.c-field-label {
min-width: 7rem;
}
Rule: When no hook exists, use the value directly with a comment explaining it's intentional. Prefer SLDS grid utilities (slds-size_*) as alternatives to hardcoded widths where possible.
Verify Before You Use
Rule: Never include an SLDS hook, utility class, blueprint class, or icon in generated code without first confirming it exists in the metadata. Guessing based on naming patterns is the primary source of invented artifacts.
Run the appropriate search command before emitting any SLDS artifact:
| Artifact | Verification command | Source of truth |
|---|
Styling hook (--slds-g-*) | node scripts/search-hooks.cjs --prefix "<hook-name>" | metadata/hooks-index.json |
Utility class (slds-*) | node scripts/search-utilities.cjs --search "<class-name>" | metadata/utilities-index.json |
| Blueprint / CSS class | node scripts/search-blueprints.cjs --search "<pattern>" then read the YAML | metadata/blueprints/components/*.yaml |
| Icon | node scripts/search-icons.cjs --query "<description>" | metadata/icon-metadata.json |
If the search returns no match: do not use the artifact. Find an alternative from the search results or build custom with verified hooks.
Naming Conventions
Use a consistent prefix for custom classes to avoid collision with SLDS:
| Pattern | Use Case | Example |
|---|
my-* | General custom styling | my-card-header |
c-* | LWC component-specific | c-accountList-row |
[namespace]-* | Package/app namespace | acme-dashboard-widget |
Avoid: generic names (container, wrapper), SLDS-like names (custom-slds-button), BEM on SLDS classes (slds-card__custom-header).
Custom hook namespacing:
:root {
--my-app-primary: var(--slds-g-color-accent-1);
--my-app-card-padding: var(--slds-g-spacing-4);
}
Knowledge Map
This skill bundles comprehensive SLDS knowledge. Read files as needed -- don't read everything upfront.
Decision Guides (start here for each task)
Search Scripts (find specific artifacts)
| Script | What it searches | Example |
|---|
scripts/search-blueprints.cjs | 85 blueprint YAMLs | --search "dialog" |
scripts/search-hooks.cjs | 523 styling hooks | --prefix "--slds-g-color-accent-" |
scripts/search-icons.cjs | 1,732 icons with synonyms | --query "save button" |
scripts/search-utilities.cjs | 1,147 utility classes | --category "grid" |
Deep-Dive Guidance (read for detailed rules)
| Folder | Content | Index |
|---|
guidance/overviews/ | Foundational concepts (color, spacing, typography, etc.) | guidance/README.md |
guidance/styling-hooks/ | Hook categories with detailed usage | guidance/README.md |
guidance/utilities/ | 27 utility class categories | guidance/README.md |
guidance/slds-development-guide.md | Full SLDS development guide | -- |
Raw Metadata (structured data for lookup)
Do not read metadata JSON files directly — they are too large for agent context (hooks-index.json is 6,000+ lines; icon-metadata.json is 38,000+ lines). Use the search scripts above to query them.
| File | Content | Lines |
|---|
metadata/blueprints/components/*.yaml | 85 blueprint specs (classes, variants, a11y, HTML) | ~50-200 each |
metadata/hooks-index.json | 523 hooks with values and CSS properties | ~6,300 |
metadata/icon-metadata.json | 1,732 icons with synonyms for search | ~38,500 |
metadata/utilities-index.json | 1,147 utility classes with CSS rules | ~6,900 |
Authoring Workflow
Phase 1: Understand the Need
Identify:
- What UI pattern is needed? (form, table, modal, card, etc.)
- What framework? (LWC, React, Vue, Angular, vanilla)
- What data will it display?
- What states does it need? (loading, empty, error, success)
Phase 2: Select the Artifact
- If LWC: Check the Lightning Component Library for an LBC
- Search blueprints:
node scripts/search-blueprints.cjs --search "<pattern>"
- Read the blueprint YAML:
metadata/blueprints/components/<name>.yaml for exact classes, modifiers, states, and accessibility requirements
- No match? Build custom with hooks (see Phase 3)
Details: references/component-selection.md
Phase 3: Apply Styling
- Read: references/styling-decision-guide.md
- Colors: Classify role (surface, accent, feedback, border) then pick hook
- Spacing: Use utility classes (
slds-p-*, slds-m-*) or hooks (--slds-g-spacing-*)
- Layout: Use grid utilities (
slds-grid, slds-col, slds-size_*)
- Custom CSS: Use
var(--slds-g-*, fallback), custom class prefixes only
Phase 4: Add Icons
- Read: references/icons-decision-guide.md
- Search:
node scripts/search-icons.cjs --query "<description>"
- In LWC: Use
<lightning-icon> with alternative-text
- In non-LWC: Use SVG with
slds-icon classes and slds-assistive-text
Phase 5: Validate (Mandatory — Do Not Skip)
Step 1: Run the SLDS linter. This is required. Zero violations is the target.
npx @salesforce-ux/slds-linter@latest lint <component-path>
The linter catches hardcoded values, class overrides, and deprecated tokens. Fix all violations before proceeding. Do not rationalize violations as acceptable.
Step 2: Verify no invented hooks. Confirm every --slds-g-* hook in the output exists in metadata/hooks-index.json. Cross-reference against the T051 check in checklists.md.
Step 3: Run through checklists.md for the checks the linter cannot automate:
- All
var(--slds-g-*) have fallback values (T002)
- Surface/accent/feedback color hooks are properly paired (T010–T013)
- Spacing uses hooks or utility classes — no magic
px values (T020–T021)
- Font sizes use
--slds-g-font-scale-*, not --slds-g-font-size-N (T031)
- All icons have accessibility text (A004)
- Custom classes use
my-* or c-* prefix (Q010)
Step 4 (optional): Run the full quality audit using the design-systems-slds-validate skill for a scored report before code review or deployment. Use it directly for LWC / HTML-CSS-JS components; for JSX/TSX outputs, treat the result as partial coverage only. Target a B grade (≥80) or higher before marking work complete.
Quick Reference
Common Hook Patterns
background: var(--slds-g-color-surface-1, #ffffff);
color: var(--slds-g-color-on-surface-2, #181818);
padding: var(--slds-g-spacing-4, 1rem);
border-radius: var(--slds-g-radius-border-2, 0.25rem);
box-shadow: var(--slds-g-shadow-1, 0 2px 4px rgba(0,0,0,0.1));
background: var(--slds-g-color-accent-1, #0176d3);
color: var(--slds-g-color-on-accent-1, #ffffff);
font-size: var(--slds-g-font-scale-2, 0.875rem);
Common Utility Patterns
<div class="slds-grid slds-wrap slds-gutters">
<div class="slds-col slds-size_1-of-1 slds-medium-size_1-of-2">...</div>
</div>
<div class="slds-p-around_medium slds-m-bottom_small">...</div>
<p class="slds-truncate" title="Full text here">Full text here</p>
Examples
See examples.md for worked examples demonstrating the full workflow from intent to SLDS artifact selection.
Validation
See checklists.md for validation checklists aligned with the design-systems-slds-validate skill.
Resources
