CV-generate

Use for general product implementation work that is not primarily backend architecture, pure integration wiring, or screenshot-driven design-to-code.

Use when backend work requires contract-first thinking, schema changes, permission checks, side-effect analysis, or test planning.

Use immediately after codebase discovery to classify task scale and determine which workflow steps are required vs. optional.

Use when the user provides screenshots, mockups, or design assets and wants implementation that stays visually close to the source.

Use when the main deliverable is maintainable documentation such as repository rules, onboarding guides, runbooks, ADRs, or architecture notes.

Use when encountering compile errors, test failures, runtime exceptions, or unexpected behavior during implementation.

Use when a request needs system-level planning before implementation, especially for cross-module, high-risk, or ambiguous work.

Use to maintain persistent context across agent sessions — decision logs, architecture memory, and constraint tracking.

Use on first entry to a new repository to run environment scanning and ask targeted boundary questions before implementation.

Use to maximize prompt cache hit rates across LLM providers by enforcing a stable instruction loading order and file size discipline.

Use before any implementation to understand the codebase structure, existing patterns, dependency graph, and project conventions.

Use after writing or modifying code to enforce the mandatory write → test → fix → repeat validation cycle.