Skill / Refined UI registry
Compound components DX
Expose named anatomy parts when users need to customize layout or actions.
Goal
Prefer anatomy-based compound components over large prop bags for customizable Refined UI surfaces.
Registry-first guidance for installable Refined UI components, skins, hooks, and blocks.
Checks
1Expose meaningful parts such as Root, Header, Content, Actions, Media, Title, and Submit when users may customize layout.
2Keep data or state props only where they drive behavior, such as from, state, value, onSubmit, or code.
3Type each part with ComponentProps<> for its rendered element or base UI component.
4Forward remaining native props with ...props and let users customize each part with className.
Avoid
1Adding new visual props when a child component slot would be clearer.
2Centralized classNames slot objects for components that can expose real parts.
3Data arrays for actions or toolbar items when users should compose children directly.