What problem does it solve? Components in @dextinity/admin that hardcode markup and styling silently break all three MUI customization paths (per-instance sx/className, theme styleOverrides, and theme defaultProps), and the gap is only discovered later when a consumer tries to customize them. This Skill ensures every component is built with the slot and theme machinery from the start. ## Core Features & Use Cases - Slot-based component construction: Guides building each visual slot with createComponentSlot and typing props via ThemedComponentBaseProps so consumers get slotProps and root sx/className. - Theme integration verification: Ensures props flow through useThemeProps and the component is registered in MUI's theme types (ComponentsPropsList, ComponentNameToClassKey, Components) for typed styleOverrides and defaultProps. - Ten-point review checklist: Catches the most common review findings, including prop spread ordering, ownerState usage, classesResolver modifier classes, overridable iconMapping, and consistent DextinityAdmin<Name> naming. - Use Case: When adding a new component to @dextinity/admin, admin-color-picker, admin-date-time, or admin-rte, follow the checklist to guarantee consumers can restyle every instance through the theme and override individual instances. ## Quick Start Use this skill to author a new customizable component in @dextinity/admin and verify it against the ten-point checklist before submitting for review.
