Skill / Control UI registry

Skin completeness

Treat a skin as a complete source recipe, not a partial class override layer.

Goal

Make every skin a complete visual layer for the public Control UI component set.

Registry-first guidance for installable Control UI components, skins, hooks, and blocks.

Checks

1Each skin implements the same documented component files.

2Each skin's theme.css explicitly resolves the complete token contract in light and dark without inheriting Refined or core values.

3Skins can replace UI dependencies when the visual behavior needs more than classes.

4Adapters never import skin internals.

1Partial skins that only work on one block.

2Variant matrices for theme-level differences.