You are unifying a component that grew by additive layers rather than coherent design. Target component: $ARGUMENTS

This skill inherits the large-feature workflow by composition. As your FIRST action, invoke the Skill tool with skill: large-feature and args:

Unify the component $ARGUMENTS: refactor it from accreted layers into one coherent design.

The injected large-feature workflow (review cycle, design workflow, implementation workflow) governs the dev loop. The sections below specialize its phases for layered-code refactoring; where they conflict, the rules here win.

Hard default — behavior preservation. /unify must not change externally observable behavior: API responses, CLI output, persisted formats, error messages callers rely on. This holds through every phase. Any intended behavior change requires explicit user approval before it is implemented.

Specialization of design exploration: archaeology survey

Replace the large-feature design step "explore the relevant parts of the codebase first" with a survey of the component. Run Explore subagents in parallel — one per angle, launched in a single message: each angle gets an independent context, so coverage is diverse and the raw file dumps stay out of the main context; only the synthesized reports come back. The angles: