system-auditor

To audit a design system package for npm publish readiness, verify token architecture, folder structure, and package.json exports to ensure consumer distributability. This process checks peerDependencies, build output formats, and theme.css compliance to produce a final PASS verdict.

Semantic token layering in a design system architecture separates primitive design values from semantic naming conventions within theme.css. Auditing this layering ensures Tailwind v4 @theme compliance and verifies that tokens are structured correctly for reliable consumer theming.

Validating peerDependencies in an npm design system package requires inspecting package.json exports to ensure correct dependency declarations for consumers. A system-level audit verifies these peerDependencies alongside build output formats to confirm distributable standards are met.

A design system folder structure benefits from atoms, molecules, and organisms organization to maintain a clear public API. Auditing this structure verifies the re-export strategy and style distribution expectations, ensuring consumers can correctly import components.

A design system compliance matrix is a structured report detailing token architecture, folder structure, and npm distributable standards verification. You need one during release readiness checks to identify issues and receive concrete before and after improvement proposals.

A design system theme audit fails Tailwind v4 @theme compliance when semantic naming, token completeness, and primitive versus semantic layering do not align with expected standards. Inspecting theme.css tokens identifies these architecture gaps and generates remediation proposals.