What problem does it solve?
Many projects lack a single source of truth for visual language, which leads to inconsistent colors, typography, spacing, and component shapes; this Skill extracts or generates a design manifest and helps teams identify deviations before they accumulate.
Core Features & Use Cases
- Extract Mode: Scans tailwind.config, global CSS, and component files to infer palettes, type scales, spacing, radii, shadows, and common component patterns and cites source files.
- Generate Mode: Asks up to four targeted questions about feel, color mode, brand colors, and layout density to produce a sensible starter manifest for new projects.
- Enforcement Hook: Writes .planning/springboard-design-guide.md and supplies anti-pattern rules used by the post-edit hook to warn on hardcoded colors, mismatched spacing, and out-of-scale font sizes.
- Use Case: Run on an existing repo to create a documented style guide that flags hardcoded hex values during edits and reduces visual drift across a codebase.
Quick Start
Run the design skill by saying /design extract the design system to scan the repository and produce .planning/springboard-design-guide.md for review.