Loading...
Loading...
Found 15 Skills
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
Designs, deepens, and hardens TypeScript codebase architecture in three modes: folder structures, module contracts, and middleware pipelines for a new app; domain-informed deepening of existing code; and the guardrail tooling, CI gates, and wayfinding that stop a structure decaying. Use when setting up project structure, organizing a monorepo, designing backend modules, writing an architecture brief, recovering domain terminology, recording an architecture decision, or asking "how should I structure this app", "find architecture improvements", "this module is a mess", "make this codebase agent-friendly", "set up guardrails for coding agents", "add a dead-code check", or "my agent can't find anything in this repo". For scaffolding a new repo use scaffold-nextjs or scaffold-cli, for multi-tenant isolation use multi-tenant-architecture, for the AGENTS.md file's own content use agents-md, and for review of a local diff use pr-reviewer.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Find high-value ways to deepen a codebase's modules, present them visually, and explore the chosen change.
Use this skill when > Identify architectural friction and propose deepening opportunities — refactors that turn shallow modules into deep ones for better testability and AI-navigability. Use when improving architecture, finding refactoring opportunities, consolidating tightly-coupled modules, or making a codebase more testable.
Analyze a GitHub codebase to create comprehensive architecture documentation including ASCII diagrams, component relationships, data flow, hosting infrastructure, and file structure assessment.
Helps an agent inspect a repository and produce C4 architecture documentation. Use this when reverse engineering a codebase, documenting system context, containers, components, or clarifying architecture from code and infrastructure.
Identify codebase deepening opportunities based on the domain language in CONTEXT.md and decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's backlog backend (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the backlog, triage labels, or domain docs.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
Builds and stress-tests implementation plans in two modes. Create mode scans code and docs, asks one question at a time with a recommended answer, runs a blindspot pass when the user is new to the area, then writes a plan file. Review mode scores completeness, feasibility, scope, testability, risk, and assumptions, verifies checkable claims, and writes resolutions back until every dimension reaches 5/5. Use when asked to "create a plan", "plan this feature", "I want to build X", "grill me", "think this through", "blindspot pass", "unknown unknowns", "this is new to me", "review my plan", "rubber duck this", "stress test this plan", "is this plan ready", "get this plan to 5/5", "what am I missing", "verify this claim", "prove this plan", "fact-check this plan", "split this into tickets", "break this down into slices", "this is too big for one plan", or when the user explicitly wants a plan artifact before implementation. For code review use pr-reviewer; for architecture briefs use codebase-architecture.