All skills
design-system-rules
FoundationJIT onlyanalysis-agent/task-agent: use when tokens, components, responsive behavior, accessibility, or variants need consistency rules; skip when UI system rules are unaffected.
- Group
- Experience design
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- apply design tokens component conventions spacing typography and interaction rules
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local design system rules decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- design-system decision with semantic intent, token and component mapping, variant and state contract, responsive and accessibility behavior, bounded exceptions, validation evidence, and residual owners
Escalation signals
When this skill must hand the decision back
- Design drift increases inconsistency maintenance cost and user confusion
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Shared component, variant, token, or interaction choices compete. | A feature-local layout does not alter shared semantics. | AnalysisTask |
| checklist.mddecision-checklist | System changes accessibility, responsiveness, variants, or API compatibility. | No shared component or token contract changes. | AnalysisTask |
| evidence-patterns.mdevidence-pattern | Design-system claims require current stories, screenshots, or accessibility reports. | No reuse, responsive, or accessibility claim awaits proof. | AnalysisTask |