Write git commits in Nic Cope's style. Use when creating commits, staging changes for commit, or when the user asks to commit. Includes Signed-off-by requirements and problem-first messaging.
Write and edit documents in Nic Cope's voice and style. Use when drafting designs, one-pagers, PRDs, proposals, explorations, blog posts, or any prose document. Also use when tightening, de-slopping, or copy editing prose, whether yours, Nic's, or someone…
Create GitHub issues in Nic Cope's style. Use when opening, creating, or filing issues, bug reports, feature requests, or proposals. Uses gh CLI and respects issue templates.
Create and manage GitHub pull requests in Nic Cope's style. Use when creating, opening, or drafting PRs, or updating PR descriptions. Uses gh CLI.
Review non-trivial code changes in a fresh context before committing. Use before committing new features, non-trivial bug fixes, refactors, or any change where correctness matters. Also use when the user asks for a review or sanity check. Do not use for typo…
Core engineering principles to apply before beginning implementation in any language. Read at the start of a coding session, before writing the first new code, refactor, or change to existing code. Establishes how to approach a codebase, design for change,…
Review code and docs the way negz reviews them - naming, Go idiom, Kubernetes API conventions, simplicity (YAGNI), consistency with existing patterns, testing style, comments, and compatibility. Use when reviewing a PR or diff, when asked for a review or…
Factor and structure Go code for clarity, testability, and composability. Use when writing new Go code, refactoring existing code, reviewing code structure, adding interfaces, decomposing large functions or structs, or when the user mentions factoring,…