fe-ui-element-components

To create reusable UI components, you codify design-system patterns by establishing shared primitives, semantic tokens, and theming contracts. This reduces redundancy and ensures consistency by enforcing API contracts and classification across multiple projects.

Data-state and data-slot conventions are structural contracts used to manage component variations and internal element styling without relying on heavy CSS. They establish predictable data attributes to support scalable UI systems and maintainable theming across different codebases.

Polymorphic APIs allow a component to render as different underlying elements or primitives while maintaining strict type safety. They enforce API contracts through prop patterns like `as` or `asChild` to ensure flexible yet predictable component composition.

Yes, this design-system skill provides explicit guidance for distribution and documentation to accelerate cross-project collaboration. It helps teams deploy shared UI primitives, export prop types, and standardize adoption strategies across multiple codebases.

You need to classify design artifacts like primitives, components, blocks, and templates to manage scope and API expectations effectively. This classification guides the establishment of token contracts and polymorphic API rules for scalable UI systems.

The best way to enforce API contracts for shared UI components is to codify design-system patterns that mandate prop type exports and polymorphic conventions. This ensures predictable component composition and standardizes documentation across teams.