A practical walkthrough of setting up Claude Code agent teams with clear roles, task ownership, communication rules, review steps, and lightweight output contracts.
A hands-on case study of using Codex subagents to coordinate data collection, preparation, and Slidev report generation in parallel.
I wanted Python repository health checks without flooding the main Codex thread with raw `uv`, `ruff`, `pytest`, and `ty` output. So I built a subagent-backed skill that inspects the repo, runs the usual commands, and returns a compact report with clear pass, warn, and fail signals.
A practical guide to what the planner actually sees, why context is more than the prompt, and why better context selection matters more than simply adding more tokens.
I already had reusable `uv`-first instructions for Claude Code and Codex. I have now added the Cursor path too: generate a rule from the same source guidance so Cursor stays on the same Python workflow.