forcedotcom/sf-skills / skills/design-systems-slds-apply
design-systems-slds-apply
UnverifiedApply 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".
assets/blueprints/components/summary-detail.yaml
View on GitHubname: Summary Detail
description: A layout pattern that displays a condensed summary view with an expandable detail section, allowing users to
quickly scan information and dive deeper when needed.
category: Layout
slds_classes:
root: slds-summary-detail
elements:
- class: slds-summary-detail__content
description: Container for the summary content
purpose: Holds the condensed summary information
modifiers: []
states:
- class: slds-is-open
description: Open detail state
trigger: Applied when detail section is expanded
- class: slds-is-closed
description: Closed detail state
trigger: Applied when detail section is collapsed
variants:
- name: Base
description: Standard summary detail with expandable content
classes:
- slds-summary-detail
usage_context: Default implementation for summary/detail patterns
differences: Collapsible detail section with summary always visible
lightning_component:
name: No direct component
url: https://developer.salesforce.com/docs/component-library/overview/components
mapping_notes: No direct Lightning Base Component equivalent - can be implemented using lightning-accordion or custom components
accessibility:
keyboard_support:
- Tab to focus expand/collapse button
- Enter/Space to toggle detail visibility
- Tab navigation through detail content when expanded
screen_reader:
- Summary content always announced
- Expand/collapse state clearly communicated
- Detail content announced when expanded
aria_attributes:
- aria-expanded on toggle button
- aria-controls linking button to detail content
- aria-labelledby for detail section
- role='button' for interactive elements
usage_guidelines:
when_to_use:
- For progressive disclosure of information
- When space is limited but detail is important
- To reduce cognitive load with scannable summaries
- For optional detailed information
when_not_to_use:
- When all information is equally important
- For critical information that shouldn't be hidden
- In contexts where expansion isn't expected
best_practices:
- Make summaries meaningful and self-contained
- Provide clear expand/collapse indicators
- Ensure smooth transitions between states
- Keep summary content concise but informative
- Use consistent expand/collapse patterns
common_mistakes:
- Making summaries too vague or incomplete
- Hiding critical information in details
- Poor visual indicators for expand/collapse state
- Inconsistent interaction patterns
code_examples:
- title: Basic Summary Detail
description: Summary detail in collapsed state
code: "<div class=\"slds-summary-detail slds-is-closed\">\n <div class=\"\">\n <h3>Contact Information</h3>\n\
\ </div>\n <div class=\"slds-summary-detail__content\">\n <p>John Smith - Primary Contact</p>\n \
\ <button class=\"slds-button slds-button_neutral\" aria-expanded=\"false\" aria-controls=\"summary-detail-02\">\n \
\ <svg class=\"slds-button__icon slds-button__icon_left\" aria-hidden=\"true\">\n <use xlink:href=\"\
/assets/icons/utility-sprite/svg/symbols.svg#chevronright\"></use>\n </svg>\n Show Details\n \
\ </button>\n </div>\n <div id=\"summary-detail-02\" class=\"slds-hide\">\n <p>Detailed contact information\
\ would appear here when expanded.</p>\n </div>\n </div>\n"
dependencies:
css_files:
- summary-detail.css
- grid.css
- button.css
javascript:
- summary-detail.js
icons:
- utility-sprite.svg
other_components:
- button
- grid
related_components:
- name: Accordion
relationship: similar
description: Similar expandable content pattern
- name: Expandable Section
relationship: similar
description: Similar progressive disclosure concept
- name: Cards
relationship: container
description: Often used within card containers
references:
official_docs: https://v1.lightningdesignsystem.com/components/summary-detail/
metadata:
version: 1.0.0
last_updated: '2025-11-12'
review_status: complete
notes: ' Cleaned invalid classes and CSS variables on 2025-11-12 using slds-plus.css as source of truth.'
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |