design

Generate or extract a markdown design manifest from Tailwind config, CSS, and components.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mferris77/SpringBoard --skill design-mferris77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/mferris77/SpringBoard/tree/main/vscode-citadel-harness/skills/design
Command: npx skills add https://github.com/mferris77/SpringBoard --skill design-mferris77

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract a design system from an existing Tailwind project?

To extract a design system from Tailwind, this tool scans your tailwind.config, global CSS, and component files to infer palettes, type scales, spacing, and radii. It generates a structured markdown manifest citing source files to document your current visual language.

How do I stop hardcoded CSS values from causing visual drift in my codebase?

To stop hardcoded CSS values from causing visual drift, this tool writes anti-pattern rules used by a post-edit hook. The hook warns developers during edits when it detects hardcoded colors, mismatched spacing, and out-of-scale font sizes.

Can I generate a starter style guide for a new project without existing CSS?

You can generate a starter style guide for new projects by answering up to four targeted questions about feel, color mode, brand colors, and layout density. The tool produces a sensible starter manifest with color, typography, spacing, and shape scales.

What is the best way to maintain visual consistency across an existing codebase?

The best way to maintain visual consistency is creating a single source of truth for your design language. This tool produces a structured markdown manifest documenting color, typography, spacing, shape scales, and anti-pattern rules to identify deviations before they accumulate.

Does this design manifest tool work with plain CSS or only Tailwind configurations?

This design manifest tool works with both Tailwind configurations and plain global CSS. It scans tailwind.config and component files alongside global styles to extract palettes, type scales, spacing, radii, and shadows into a unified style guide.

What limitations should I expect when extracting a design manifest from component files?

When extracting a design manifest from component files, the tool infers common patterns and cites source files but relies on existing code structure. Complex or highly dynamic styling may require manual review to ensure the generated manifest accurately captures all visual scales.