What documentation layers does this skill support?

It currently supports the SEED Design System architecture, specifically validating Design Guidelines, Rootage Component Specs, and React Implementation Docs.

How does it verify component properties?

The skill parses Rootage YAML definitions and extracts variants, sizes, and states, then compares them against the Props tables found in your Design Guidelines MDX files.

Does it automatically update my documentation files?

No, it generates a detailed report highlighting inconsistencies and missing elements, providing the exact file paths and recommendations so you can review and apply the fixes safely.

Can it identify missing documentation?

Yes, it builds a component inventory from your technical specs and flags any component missing its corresponding design or React documentation files.

Design System Docs Consistency Checker

Name: Design System Docs Consistency Checker
Author: Activer007

byActiver007

Content Management

Validates synchronization and accuracy across design guidelines, technical specifications, and implementation documentation within the SEED Design System.

About

The Documentation Consistency Checker is a specialized auditing tool designed to maintain high standards in the SEED Design System. It cross-references three critical documentation layers—Design Guidelines (MDX), Rootage Component Specs (YAML), and React Implementation Docs (MDX)—to ensure component names, descriptions, and props are perfectly aligned. By identifying orphaned files, missing property definitions, and naming discrepancies, this skill helps teams maintain a reliable source of truth and ensures documentation stays in sync with technical implementation.

Key Features

Comprehensive consistency reporting with actionable fix recommendations
Deep props and variants verification against Rootage technical specs
Automated cross-layer validation between MDX and YAML files
0 GitHub stars
Identification of orphaned files and missing documentation layers
Component ID and naming convention enforcement

Use Cases

Standardizing descriptions and properties across design and implementation docs
Validation of new component documentation before publishing
Pre-release audits to ensure documentation completeness for all components

About

Key Features

Comprehensive consistency reporting with actionable fix recommendations
Deep props and variants verification against Rootage technical specs
Automated cross-layer validation between MDX and YAML files
0 GitHub stars
Identification of orphaned files and missing documentation layers
Component ID and naming convention enforcement

Use Cases

Standardizing descriptions and properties across design and implementation docs
Validation of new component documentation before publishing
Pre-release audits to ensure documentation completeness for all components