Bang-isme

Use for project memory, decisions, handoffs, genome, knowledge index, changelog, and patterns that must persist across sessions.

Use for frontend, backend, mobile, debugging, security, or specialized engineering work that needs focused domain references and strict boundaries.

Use for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits.

Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.

Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.

Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.

Use at the start of a Codex task to inspect repo readiness, project profile, monorepo shape, role docs, spec status, knowledge index, and recommend the next workflow.

Use when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.

Use for UI, frontend, styling, landing page, or component creation; injects palettes, typography, layouts, motion, and anti-generic design rules.

Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.

Use for frontend, backend, mobile, debugging, security, or specialized engineering work that needs focused domain references and strict boundaries.

Use when an approved plan has independent tasks ready for delegated execution with fresh subagents and two-stage review.

Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.

Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.

Use when committing or pushing completed work; automates gate-aware conventional commits with optional signing and CI/CD checks.

Use for project memory, decisions, handoffs, genome, knowledge index, changelog, and patterns that must persist across sessions.