One-click install
npx skills add https://github.com/Dragoon0x/dragoon-skills --skill scan-dragoon0x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan
Source: https://github.com/Dragoon0x/dragoon-skills/tree/main/skills/scan
Command: npx skills add https://github.com/Dragoon0x/dragoon-skills --skill scan-dragoon0x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually documenting a codebase's design system (tech stack, color palettes, spacing grids, type scales, accessibility metrics) to use dragoon's design intelligence tools is tedious, error-prone, and creates friction when onboarding new projects or updating design systems.

Core Features & Use Cases

  • Automated Codebase Scanning: Uses regex-based scanning (no AST parsers or network calls) to detect your project's tech stack, design tokens, and accessibility metrics, automatically skipping irrelevant directories like node_modules and .git.
  • Canonical Manifest Generation: Creates the dragoon.json file that serves as the single source of truth for all other dragoon skills, ensuring generated code, critiques, and design checks match your project's existing style.
  • Use Case: Run this Skill first when setting up dragoon in a new project, or after major design system changes, to ensure subsequent commands like /critique, /slop, and /component produce accurate, on-brand outputs.

Quick Start

Use the scan skill to fingerprint your project's codebase and generate the required dragoon.json manifest for all dragoon design workflows.

Frequently Asked Questions about scan

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

FAQPage Schema
How do I extract design tokens and color palettes from my codebase?

To extract design tokens from a codebase, you can use regex-based scanning to detect tech stack, color palettes, spacing grids, type scales, and accessibility metrics. This automated codebase scanning eliminates tedious manual design system documentation by generating a standardized manifest file.

What is a design DNA manifest and why do I need it?

A design DNA manifest is a standardized JSON file that captures your project's tech stack, design tokens, and accessibility metrics. It acts as the single source of truth for design intelligence tools, ensuring generated code and critiques match your project's existing style.

Does codebase scanning require AST parsers or external network calls?

Codebase scanning does not require AST parsers or external network calls. It uses regex-based scanning to detect design tokens and automatically skips irrelevant directories like node_modules and .git, operating entirely without external dependencies.

When do I need to scan my codebase for design system changes?

You need to scan your codebase when setting up design intelligence tools in a new project, or immediately after major design system changes. This ensures subsequent commands like critique, slop, component, and ship produce accurate, on-brand outputs matching existing patterns.

Can I use design intelligence commands without generating a manifest first?

Generating a manifest is a required first step before running design intelligence commands like critique, slop, component, or ship. Without this standardized design DNA file, the tools cannot ensure outputs match your project's existing design patterns.