What problem does it solve? This Skill documents how to move a component's five implementation paths (declaration, block, label, generation, execution) out of shared source files into its own capsule folder under src/components/<scope>/<name>/, without breaking baselines, guardrails, or toolbox ordering. Note: this Skill is retired (superseded by component-generate) because all 177 components have already been encapsulated; it is preserved as a historical record. ## Core Features & Use Cases - Shape classification before migrating: Categorizes components into five shapes (dispatch-table row, router entry, full pattern object, dedicated module folder, function-like dispatcher) to estimate migration cost and choose the right mechanism (registration call vs glob direct-read). - Six-condition movability check: Verifies single-output, single-reference, block/label existence, non-aliased implementations, and trait-based consumer dispatch before cutting code. - Baseline and self-proof testing discipline: Requires recording five-path baselines, verifying baseline files actually contain content, and anchoring every negative assertion with a positive one. - Use Case: When refactoring a codebase so each component owns its logic, use this record to understand how 177 components were migrated in 17 batches, why transition tables must be deleted when empty, and how to avoid assembly-point regressions. ## Quick Start Ask the AI to read this Skill's record and explain how a component was cut from shared files into its capsule, or use component-generate for creating new components.
