ss-bs-discovering-design

Generate, import, or audit a repository's DESIGN.md from scanned token sources.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-bs-discovering-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-bs-discovering-design
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/project-bootstrap/ss-bs-discovering-design
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-bs-discovering-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you produce (or correctly extend and audit) a DESIGN.md that captures your project’s visual design system—tokens, component rules, and the project-specific philosophy—without forcing you to invent everything from scratch.

Core Features & Use Cases

  • Import an existing design: Copy a user-provided DESIGN.md into the configured location atomically when you already have a ready file from tools or hand-authored work.
  • Build design collaboratively from code: Scan the repository for tokens, theme signals, and component vocabulary, then ask targeted questions for what the code cannot tell you, producing or updating DESIGN.md accordingly.
  • Extend or audit an existing design: Extend merges content without overwriting, while audit performs drift checks and prompts you to resolve token/component/variant drift before writing the updated document.

Quick Start

Use the ss-bs-discovering-design skill to either import an existing DESIGN.md file or build one from your codebase by choosing the import or build option when prompted, then confirming the output path to write docs/DESIGN.md.

Frequently Asked Questions about ss-bs-discovering-design

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

FAQPage Schema
How do I generate a DESIGN.md for an existing repository?

To generate a DESIGN.md, the Skill scans your repository for design tokens and component vocabulary, asks targeted questions for missing design intent, and atomically writes the output to your configured file path.

Can I import an existing design system file without overwriting my current tokens?

Yes, you can import an existing design system file atomically, or use extend mode to merge new content into your DESIGN.md without overwriting your current tokens and component rules.

What is a design system drift audit and when do I need one?

A design system drift audit checks your DESIGN.md against current code to identify token, component, and variant drift, prompting you to resolve discrepancies before writing the updated document.

How do I bootstrap design documentation from code without starting from scratch?

You can bootstrap design documentation by scanning the repository for theme signals and component vocabulary, then answering targeted questions to capture project-specific design philosophy without inventing everything from scratch.

Does this design documentation tool work without external dependencies?

Yes, this design documentation tool works standalone without external dependencies, requiring only your repository root path, desired mode, and configured file path to coordinate the generation or audit process.

What's the best way to manage component variants and design tokens in a project?

The best way to manage component variants and design tokens is to document them in a DESIGN.md file, using audit mode to periodically drift-check the documented tokens against your current codebase.