my-claude-codex

Use when a Go task needs guidance on error ownership, logging, stdlib-vs-custom helper choices, version-specific APIs, concurrency, testing, package/interface design, performance, gRPC/protobuf, database/sql, Ent, or tooling decisions.

Use when writing or reviewing MySQL 8.0 or Aurora MySQL 3 SQL, indexes, UUID storage, cursor pagination, EXPLAIN, HLL, deadlocks, MDL, gh-ost, pt-osc, RDS Proxy, JDBC Wrapper, slow query logs, schema migrations, connection pools, or Aurora failover.

Use before crossing a decision boundary: a direction choice (multiple valid implementations), a contract commitment (public API, database schema, proto/GraphQL field, migration, auth/tenant boundary, event format), a costly-to-reverse action (delete data, force push, deploy to shared env), after a discovery that invalidates the plan, or after completing an independently reviewable slice. Not for routine work inside the agreed slice — never pre-emptively, never based on size.

Use when the user asks to create, update, synchronize, merge, close, reopen, mark draft, or mark ready a pull request, or when PR title, body, branch, label, merge, or publish authorization conventions matter. Caruso/JasperLabs scoped. Not for PR review comments; use resolve-pr-comments.

Use when the user asks to "plan a project", "break down this project", "create an engineering plan", or "plan the work for [project name]". Also use when reviewing or refining an existing engineering plan.