skills/architect/SKILL.md
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for architect this, design this, or non-trivial work where jumping to code would lock in the wrong shape.
npx skillsauth add shipshitdev/library architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design before implementing. Sketch types, function signatures, class
shapes, and module boundaries with not implemented bodies. Synthesize
across parallel candidates, then fill in code against the chosen sketch.
Companion to codebase-design, which owns deep-module vocabulary. This
skill owns the pre-implementation sketch loop.
Inputs:
Outputs:
Creates/Modifies:
External Side Effects:
Confirmation Required:
Delegates To:
how for grounding, why when ownership or layering is the
constraint, arena for candidate sketches, interrogate when the
design is contestedOpen a todo list with one entry per phase: Ground, Sketch, Agree, Implement, Scrap.
Run how over every system the new code touches. If the design
redefines ownership or layering, also run why on the existing shape.
Skip only when the work is genuinely greenfield.
Run arena with the design-sketch task. Each candidate produces a
package shaped per
references/rationale-template.md
using references/runner-prompt.md.
Require at least two structurally distinct candidates. Screen every candidate against references/design-red-flags.md. Prefer the design that hides more complexity behind a smaller public surface.
Default: proceed to implementation. Opt in to a checkpoint when the invoker asks to see the sketch first. Human pushback is Phase A evidence. Re-ground and re-run Phase B.
Replace not implemented bodies. Deviations from the sketch are
signal. Surface them. Do not bolt them on silently.
If implementation keeps producing the same shape of friction, throw the
sketch out. Re-run how over what was built. Redesign as if the new
constraints were day-one assumptions. Subtract before adding. Return to
Phase B.
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.