architect

Use a design-first workflow that sketches types, function signatures, and module boundaries with placeholder bodies before implementation. This Skill grounds the problem in the existing system, generates multiple candidate designs in parallel, and synthesizes the strongest one into a rationale document.

Generate at least two structurally distinct candidate designs, then screen each against red flags like shallow modules, information leakage, and pass-through methods. Compare survivors on interface depth, preferring the design that hides more complexity behind a smaller public surface.

Redesign when you see a repeated pattern of friction, not isolated hard cases: recurring workarounds of the same shape, types needing escape hatches like casts or any, or callers forced to know internal rules. Single edge cases do not condemn a design.

A shallow module exposes a large interface while hiding little complexity. Signs include callers coordinating several methods for one operation, public options exposing internal stages, and an interface that does not save callers from learning the implementation.

No, human checkpoints are opt-in. By default the workflow proceeds directly from the synthesized design to implementation; a checkpoint pause only happens when the invoker explicitly asks to review the design first.