What problem does it solve? Component documentation in Storybook often drifts out of sync with actual stories, duplicates code snippets, or ignores the design system's structure. This Skill enforces a consistent two-tab MDX documentation format so docs stay accurate and maintainable. ## Core Features & Use Cases - Two-Tab Structure Enforcement: Ensures every component doc uses Overview (anatomy, properties, accessibility) and Implementation (setup, code examples) tabs. - Story-Backed Code Examples: Requires <Source of={ComponentStories.StoryName} /> instead of hand-written fenced code blocks, keeping snippets in sync with Storybook. - Design-System Table Markup: Provides a copy-paste table template in references/tables.md using design tokens like body-2, text-accent, and border-muted. - Use Case: When documenting a new Button component, generate an MDX file with the required tab structure, link each code example to its story, and format any tables with the correct design-system tokens. ## Quick Start Write the Storybook MDX documentation for my component following the two-tab Overview and Implementation structure with story-backed Source examples.