What problem does it solve? Code changes in a React/TypeScript frontend often ship without corresponding documentation updates, leaving READMEs, module docs, Storybook stories, and contributor guides stale and misleading. This Skill treats documentation as part of the definition of done, ensuring every code change lands with synchronized docs in the same branch and PR. ## Core Features & Use Cases - Documentation impact mapping: Maps each change type (components, hooks, GraphQL operations, state stores, configuration, security, testing, performance, accessibility) to the specific docs that must be updated. - Scenario-based update patterns: Provides concrete documentation patterns per scenario, including Storybook rebuilds, GraphQL mock fixture notes, DI wiring records, and Lighthouse budget references. - Quality gates and checklist: Enforces consistency, completeness, link validity, tested examples, and a pre-commit checklist integrated with Markdown lint and CI checks. - Use Case: After adding a new UI component with props and variants, use this Skill to update the module README, add a Storybook story, rebuild Storybook, and verify all examples and links before opening the PR. ## Quick Start Ask the assistant to update all affected documentation for the component and hook changes in the current branch before committing.
