keystone-ui
Official@keystone-ui
Offers specialized architectural governance and component engineering standards for React-based design systems using Tailwind CSS v4.
Agent Skills by keystone-ui
Showing 10 vetted skills indexed across 1 GitHub repositories.
keystone-uicodebase-auditor
Audit Keystone UI component source and story files for convention violations.
keystone-uidocs-writer
Inspect React component source and Storybook stories to write concise technical documentation.
keystone-uivercel-react-best-practices
Optimize React and Next.js code for performance best practices.
keystone-uidocs-curator
Review Keystone UI Storybook stories against component source and exports.
keystone-uiweb-animation-design
Select natural motion timing, easing, and transform behavior for UI animations.
keystone-uicontributing
Synchronize Keystone UI component changes with Storybook, Fumadocs, MDX, and registry files.
keystone-uicomponent-architecture
Define structural conventions for Keystone UI component files.
keystone-uidesign-tokens
Standardize UI design token usage and component styling for Keystone UI React components.
keystone-uipopup-patterns
Standardize popup component styling and behavior across dropdown menus, selects, comboboxes, and popovers.
keystone-uikeystoneui-react
Build and fix Keystone UI React components using subpath imports and Tailwind CSS v4 tokens.
Frequently Asked Questions About keystone-ui
FAQPage SchemaWhat specific tasks does Keystone-UI enable for frontend developers?▼
Keystone-UI enables the systematic auditing of component source files, generation of technical documentation from Storybook stories, and enforcement of design token consistency. It facilitates the synchronization of component changes across MDX files, registry configurations, and UI styling layers to ensure architectural integrity.
Which technical personas benefit most from these component standards?▼
Frontend engineers, design system maintainers, and UI architects benefit from these standards. The registry is specifically designed for teams managing complex React component libraries who require strict adherence to Tailwind CSS v4 tokens and consistent structural conventions across large-scale interface projects.
What are the primary dependencies for implementing Keystone-UI standards?▼
Implementation requires a React-based environment utilizing Storybook for component isolation and Fumadocs for MDX-based documentation. Projects must be configured to support subpath imports and Tailwind CSS v4 token structures to ensure full compatibility with the provided component architecture and styling conventions.