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.
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.
I kept noticing coding agents drifting into `pip install`, raw `python`, and hand-edited dependency files in Python projects. So I built a small repo with reusable `CLAUDE.md` and `AGENTS.md` guidelines that push both Claude and Codex toward a consistent `uv` workflow.
The show must go on in the AI era. The responsibility - and the opportunity - for experienced software engineers to help grow the next generation is still here. Sharing knowledge and supporting early-career talent is something AI did not and could not change.
Listening to Boris Cherny talk about “coding being largely solved” felt familiar — it describes a shift many of us are already living, even if we don’t always name it.