What problem does it solve? Visual style decisions in a project often live scattered across code, config files, and people's heads, so interfaces get built inconsistently. This Skill produces a single authoritative art bible document whose every value is either extracted from the codebase or confirmed by the user — never invented. ## Core Features & Use Cases - Repository mining: Extracts existing color tokens, fonts, components, styling ADRs, and asset conventions from the project before asking any questions. - Guided interview with approval gate: Asks only about what the repo cannot answer (intent, mood, references, repeated failures), then requires an approved outline before writing anything. - Computed contrast ratios: Calculates WCAG contrast ratios via an awk script instead of estimating them, and records unverifiable values as open questions with owners. - Use Case: A team complains that every generated screen looks different and gray. Run this Skill to mine the Tailwind config and component library, interview the design owner, and produce a versioned art bible with hard rules, token mappings, and accessibility thresholds. ## Quick Start Ask the agent to write an art bible for this project based on the existing design tokens and components.
