What problem does it solve? Teams building bold, high-contrast interfaces often lack consistent, implementation-ready design-system documentation, leading to inconsistent spacing, ambiguous component states, and accessibility gaps. ## Core Features & Use Cases - Token-Driven Foundations: Defines color tokens (primary #BBF351, secondary #00BCFF), typography scales (14/16/18/24/32/40), and spacing scales (4/8/12/16/24/32) for the Neon style. - Structured Guideline Authoring: Produces component-level rules covering anatomy, variants, states (hover, focus-visible, disabled, loading, error), and responsive behavior. - Accessibility Acceptance Criteria: Enforces WCAG 2.2 AA compliance with testable requirements, anti-patterns, and a QA checklist for code review. - Use Case: A designer-engineer pair needs to document a new button component for a neon-styled product; the Skill outputs token-anchored rules, interaction states, and accessibility criteria ready for implementation. ## Quick Start Use the neon skill to write design-system guidelines for a primary button component including states, tokens, and accessibility criteria.