Activation Contract

Use this standalone skill for frontend design-system decisions when an agent must choose, review, or document production-ready technical direction.

Designing or reviewing UI systems, component anatomy, tokens, layout, or visual interaction.
Choosing CSS architecture, responsive behavior, accessibility constraints, or motion rules.
Converting repository visual direction into implementation-ready frontend guidance.

Do not use it for generic explanation, copy editing, or one-off code changes that do not affect architecture or reusable implementation patterns.

Non-Negotiable Runtime Rules

Preserve repository token and component-state contracts; do not hardcode isolated visual decisions.
Use semantic HTML and native controls before ARIA substitutes. Define native keyboard behavior, visible focus, measurable contrast, touch/pointer criteria, and reduced-motion behavior for every interactive UI.
Keep components reusable and responsive; reserve media and font geometry and do not accept performance regressions without compatible evidence.
Keep the answer decision-first. Do not add version, browser, API, accessibility-law, security, adoption, or legal-applicability claims without current authoritative verification.
Treat security requirements as conditional product and repository inputs; do not infer controls, policy, telemetry, or external-tool permission when evidence is absent.