What problem does it solve? Teams building interfaces in the Fiction style lack consistent, token-anchored rules, leading to inconsistent spacing, ambiguous component states, and accessibility gaps across playful, storybook-inspired UIs. ## Core Features & Use Cases - Token-Anchored Guidance: Produces design rules grounded in concrete tokens (colors like #222222 and #FFE9CE, Cossette Texte typography, 4/8/12/16/24/32 spacing scale) rather than vague adjectives. - Component-Level Rules: Defines anatomy, variants, and states (default, hover, focus-visible, active, disabled, loading, error) with keyboard, pointer, and touch interaction behavior. - Accessibility Acceptance Criteria: Enforces WCAG 2.2 AA with testable requirements, anti-patterns, migration notes, and a code-review QA checklist. - Use Case: Ask for a button component spec and receive a complete rule set covering variants, states, token usage, responsive behavior, and accessibility tests aligned with the Fiction brand. ## Quick Start Use the fiction skill to write design-system guidelines for a primary button component including states, tokens, and accessibility criteria.
