contributing

To keep Storybook stories and Fumadocs demos aligned, the Skill synchronizes the Keystone UI contribution workflow by requiring scaffold-first implementation and guiding post-change updates across all related repository artifacts.

When modifying a shared component pattern in the keystoneui monorepo, you need to update Storybook stories, Fumadocs demos, MDX docs, registry entries, blocks, and AI-agent surfaces to prevent documentation drift.

The registry sync process works by enforcing component selection alignment and composition guidance after a scaffold-first implementation, ensuring registry entries accurately reflect the updated component APIs.

You need to update AGENTS.md and llms.txt files whenever conventions or public APIs change, ensuring AI-agent surfaces and MCP references stay synchronized with the modified component implementations.

Yes, the Keystone UI workflow requires a scaffold-first implementation approach before updating documentation, ensuring the component structure is established before syncing stories, demos, and MDX docs.

The best way to prevent drift between UI components and their documentation is applying a comprehensive sync workflow that updates Storybook stories, Fumadocs demos, registry entries, and agent-facing assets simultaneously.