skills

Guides you through learning programming and software engineering topics using a Socratic ladder. Never gives the exact answer or a matching example. Activates on explicit requests like "help me learn X", "explain Y", "I'm trying to understand Z". Gives links to online sources.

Distills the current session into a structured specification document (SPEC.md). Captures design decisions, canonical terms, edge cases, known weak points, open questions, and ADRs. Activate with "spec this", "create spec", "write the spec", "turn this into a spec", "specify this", or after a design-interview or premortem-this session concludes.

Runs a structured, relentless design interview to reach a shared understanding of a plan, feature, or system. Walks the design tree branch by branch, resolving decision dependencies one at a time. Activate when the user says "interview me", "let's design", "walk me through", "review my plan", or shares a spec/plan and asks for feedback.

Stress-tests any plan, project, or decision by imagining it has already failed and working backward to discover why. Surfaces hidden assumptions, weak decisions, and missing risks before resources are committed. Activate when the user says "premortem this", "stress test this plan", "what could go wrong", "poke holes in this", "what am I missing", or after a design-interview session to stress-test a clarified plan.

Governs how the agent writes files. Enforces chunked, sequential writes to prevent silent truncation from buffer/context limits.

Governs the agent's internal reasoning process and communication style. Enforces hypothesis-driven, test-first, iterate-fast problem solving. Eliminates silent internal loops, premature abstraction, and invisible approach changes.

Proactively guides and enforces code quality practices: eliminating magic numbers and strings, constructor-based dependency injection, and thorough documentation. Flags violations as they are noticed, plans safe incremental refactors, and integrates with tdd-workflow, ddd, long-term-memory, and pair-mode when active.

Guides Domain-Driven Design architecture across four layers (domain, application, infrastructure, presentation) organized by bounded context. Enforces dependency rules, tactical patterns, ubiquitous language, and aggregate rules. Supports greenfield and incremental legacy migration. Integrates with tdd-workflow, long-term-memory, and pair-mode.

Maintains a persistent project journal in MEMORY.md across sessions. Records state, architectural decisions, discoveries, task history, and open questions; reconciles with the project's planning documents; archives old entries automatically. Invoke at session start and after every completed task. Toggle with "memory on" / "memory off". Compatible with pair-mode.

Pair programming navigator mode. Toggles a state where the agent scaffolds structure and writes failing tests, but refuses to implement business logic — the user writes it. Activates when the user types "pair on", "pair mode on", "/pair on", or "let's pair". Deactivates only on "pair off", "pair mode off", "/pair off", or "stop pairing". Use this skill whenever any of these triggers appear, and keep the mode active across turns until explicitly disabled.

Enforces strict Test-Driven Development (Red-Green-Refactor) workflow for any language or framework. Use this skill whenever implementing new features, fixing bugs, or modifying behavior in code. Activates on requests like "implement", "add feature", "fix bug", "create function", or any code change that affects behavior.