The skills

Thirty-eight skills install with the full profile (the starter profile ships the pipeline spine plus the working-law owners). You rarely name them — describe what you want and the agent routes; the full invocation rubric ships in your repo at .claude/skills/project-router/ROUTING.md (same under .agents/). When routing is ever unclear, the agent names its pick and asks.

Six always-loaded working laws hold in every session: work isn't done until interrogated (the done gate); ambiguity is grilled, never guessed through; structure is drawn, not narrated; no secret crosses the line; durable prose is written like a person; and a preference about how the agent works meets the discipline that owns that ground before it's persisted.

By neighborhood#

Route and personas — project-router resolves where the project stands; planner owns intent (proposed → planned); builder owns execution (executing → verifying); workspace-setup configures a repo once.

Shape the intent — grilling (the interview), grill-with-docs (the interview that records rulings), domain-modeling (pin the words), wayfinder (chart weeks of fog as a decision map).

Gather evidence — research (primary sources, cited), prototype (throwaway spikes), verify-this (baseline/treatment proof), control-cli / control-ui (drive a CLI or UI under test).

Compile and build — to-spec, to-tickets, implement, tdd.

Review — delivery-review (standards + spec fidelity), ponytail-review (over-engineering), sweep-tests (is the suite honest?), diagnosing-bugs (reproduction-first debugging).

Code guidelines — ponytail, codebase-design, model-the-domain, type-system-discipline, boundary-discipline.

Honesty and safety — fail-loud, airgap-secrets (paste a key near the agent and watch it refuse, revoke-first), answer-plainly, record-architecture-decisions.

Prose and chat — unslop, technical-writing, show-me.

Visual and docs — diagram-design (branded durable diagrams), architecture-map (the versioned isometric repo map), product-description (outside-in behavior docs).

Cadence and maintenance — progress-check (speaking unasked during long work, evidence moments only), improve-codebase-architecture (where is the design shallow?).

Provenance#

Every vendored skill is preserved byte-identically from its pinned upstream and carries its authors' voice; Green Line adds only bookends around the method, never edits inside it. The full provenance ships in your repo's installed files and in the package's notices.