Sandgrouse/adobe-express-dev-skill / skills/adobe-express-spectrum-ui-ux
adobe-express-spectrum-ui-ux
VerifiedBuild or review Adobe Express add-on panel UI with Spectrum patterns, stack selection guidance (raw SWC, swc-react, React Spectrum), Express theme setup, state and navigation design, and actionable UX quality checks. Use when implementing or auditing panel layouts, interaction states, multi-screen flows, and accessibility.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.0 KB |
| references/sample-walkthroughs.md | markdown | 2.4 KB |
| references/state-and-navigation-patterns.md | markdown | 2.5 KB |
| references/ui-stack-guide.md | markdown | 1.7 KB |
references/ui-stack-guide.md
View on GitHub# UI Stack Guide
Choose one Spectrum strategy per panel and keep it consistent.
## Preferred Order
1. Spectrum Web Components (raw)
2. swc-react for React repos
3. React Spectrum only when already established in the repo
## Stack Selection Rules
- Use raw SWC for small or framework-light panels.
- Use swc-react when React state management is already in place.
- Keep React Spectrum only when migration cost outweighs benefit.
- Avoid blending SWC and React Spectrum in one feature unless explicitly migrating.
## Theme Essentials
Apply Express theme before UI tuning:
- Import typography and Express theme modules.
- Wrap panel content in an Express theme container.
- Keep `scale` and `color` consistent unless accessibility requirements demand change.
Example patterns:
```html
<sp-theme system="express" color="light" scale="medium">
<!-- panel content -->
</sp-theme>
```
```tsx
<Theme theme="express" color="light" scale="medium">
{/* panel content */}
</Theme>
```
## Component Selection Baseline
- Actions: buttons/action buttons
- Inputs: textfield/textarea/checkbox/switch/radio
- Selection lists: menu/dropdown/action-menu
- Status: progress-circle, inline error text, toast for global feedback
- Layout: clear sections with headings/dividers instead of dense control clusters
## Accessibility Guardrails
- Ensure primary actions are keyboard reachable.
- Keep focus order consistent when screens change.
- Show error text near invalid inputs.
- Avoid color-only status signals.
## Read These Sources
- https://developer.adobe.com/express/add-ons/docs/guides/build/design/implementation-guide/
- https://developer.adobe.com/express/add-ons/docs/guides/build/design/ux_guidelines/
- https://opensource.adobe.com/spectrum-web-components/
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 |