gsp-design-system

To audit a design system, run the command at your project root to scan the workspace. It identifies tech stack, components, tokens, and conventions, then generates comprehensive markdown documentation reports.

Extract design tokens by scanning your codebase for Tailwind extensions, CSS variables, and theme files. The scan gathers these configurations to produce a comprehensive inventory of your theming setup.

Yes, you can generate a component inventory for a large project. The scan lists up to 30 components, capturing their names, file paths, and usage patterns to keep your system maintainable.

Yes, the design system audit detects frameworks and styling approaches. It identifies package managers, framework configurations, and styling methods used in your workspace automatically.

Identify design debt and accessibility gaps by generating a design concerns report. The scan highlights token coverage issues, accessibility gaps, and other debt within your components.

Yes, you need read access to project files to document design conventions. The audit utilizes Bash, Glob, and Grep to scan your workspace and capture naming, export, and file-organization patterns.