design-system-guardian

Validate UI component usage against a design system manifest.

7|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/kaelig/react-craft --skill design-system-guardian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-guardian
Source: https://github.com/kaelig/react-craft/tree/main/react-craft/skills/design-system-guardian
Command: npx skills add https://github.com/kaelig/react-craft --skill design-system-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that UI development adheres to the established design system, preventing inconsistencies and promoting efficient component reuse.

Core Features & Use Cases

  • Component Validation: Checks if custom components are used where design system equivalents exist.
  • Prop Enforcement: Verifies correct usage of props for design system components.
  • Composition Suggestions: Identifies opportunities to replace multiple elements with single design system components.
  • Use Case: A developer is building a new feature and uses a custom button component. The Design System Guardian flags this, suggesting the use of the official AcmeButton and ensuring it has the necessary onClick prop.

Quick Start

Analyze the current project's UI code against the design system manifest.

Frequently Asked Questions about design-system-guardian

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

FAQPage Schema
How do I validate React UI components against a design system?

You can validate React UI components by analyzing your code against a design system manifest. This process detects custom components where design system equivalents exist, checks incorrect prop usage, and identifies composition opportunities.

How do I check for incorrect prop usage in Storybook UI components?

Checking for incorrect prop usage involves comparing your target files against a manifest loaded from Storybook MCP or a cache. The analysis verifies correct usage of props for design system components and outputs structured findings with suggestions.

Can I use this design system validation without any external dependencies?

Yes, you can use this design system validation without external dependencies. It operates independently to analyze your target files and compare your code against a cached manifest or Storybook MCP to enforce UI consistency.

What is the best way to enforce UI component consistency in frontend code?

The best way to enforce UI component consistency is to validate component usage against a design system manifest. This detects custom components where official equivalents exist and outputs structured findings with severity, description, and suggestions.

How do I identify composition opportunities for design system components?

Identifying composition opportunities involves analyzing target files to find multiple elements that can be replaced with single design system components. The validator outputs structured findings highlighting these replacement suggestions.