.dotfiles

Step-by-step teaching mode for implementation guidance. Use when the user asks Codex to teach them how to implement a change themselves, says "use instruct", "teach me step by step", "walk me through implementing", "show me incrementally", or otherwise wants guidance-first coding help instead of Codex directly editing files.

Guidance for designing, writing, reviewing, or refactoring tests in this project. Use when adding tests for features or bugs, deciding unit vs integration boundaries, choosing what to mock, improving test structure, or reducing brittle/slow/flaky tests.

Turn a rough idea into a reviewed design spec before any implementation.

Debug issues using a structured, evidence-first process.

Execute a written implementation plan in this session with checkpoints.

Execute a written implementation plan task-by-task using pi subagents with review gates.

Verify tests, present merge options, and clean up a finished branch.

Process review feedback with technical rigor before changes.

Create an isolated worktree with safety checks and a clean baseline.

Create a detailed implementation plan from an approved spec.

Create or edit an agent skill using a test-driven documentation process.

Python language conventions, patterns, and tooling. This skill should be used when working with Python source files (.py), pyproject.toml, or writing Python scripts.

Go language conventions, patterns, and tooling. This skill should be used when working with Go source files (.go), go.mod, or building Go CLI programs.