What problem does it solve? When a UI kit component or base class does not cover a case, developers often write clones next to the ready-made code, which diverge from the original and create undeclared duplication. This Skill enforces a reuse-first workflow: verify the capability is truly missing, extend the kit instead of cloning, and formally declare any approved deviation. ## Core Features & Use Cases - Missing-capability verification: Grep-based checks across the kit exports and neighboring domains before writing anything new. - Extend-don't-clone guidance: New variants are added to the kit or base class so all screens benefit, instead of forking a local copy. - Deviation declaration: One-off departures are marked with a native-ok comment explaining what the kit lacks, and custom ready-mades are registered as sign entries with scope, cancel, and instead fields. - Use Case: A developer needs a phone-input field the kit lacks. After confirming it is missing and getting owner approval, they add a native-ok marker citing the gap and task key, and remove it once the kit ships the component. ## Quick Start Ask the assistant to check whether the UI kit already covers the component you are about to write and, if not, how to extend it or declare a native-ok deviation.
