Step-by-step workflow for deploying this project. USE FOR: creating a new release; drafting release notes; classifying semver (patch, minor, major); publishing a version tag or GitHub Release; understanding the CI → CD → staging → production pipeline; knowing what triggers Docker image builds; checking deployment status. DO NOT USE FOR: general coding; writing tests; local development setup.
Guidance on using the project Makefile as the primary development interface. USE FOR: running tests, linting, formatting, security scans, or Docker commands; understanding which make target to use for a task; replacing raw commands with their make equivalents. DO NOT USE FOR: understanding the deployment pipeline; adding dependencies; writing documentation.
Write descriptive conventional commit messages that explain intent. USE FOR: committing changes; reviewing staged diffs; drafting commit messages; when the user asks to commit. DO NOT USE FOR: general coding; writing tests; deployment.
Repo cleanup workflow for dead code removal, stale comment cleanup, naming consistency, redundant code reduction, and safe maintainability improvements. USE FOR: requests like "clean up", maintenance passes, removing unused imports or variables, pruning TODOs, and replacing inappropriate production print statements. DO NOT USE FOR: speculative rewrites, major architecture changes, or broad dependency upgrades.
Behavior-preserving refactor workflow for simplifying logic, extracting smaller functions, consolidating duplication, and improving naming and structure. USE FOR: requests like "refactor", "simplify this module", or "break this function down". DO NOT USE FOR: feature work, speculative rewrites, or dependency-management tasks.
Rules and workflow for writing and editing project documentation. USE FOR: creating or updating Markdown files in docs/; checking documentation style; understanding line-length limits; writing headings, code blocks, or links correctly; running markdownlint. DO NOT USE FOR: writing code comments or docstrings; general coding tasks.
How to add Python or Node.js dependencies to this project. USE FOR: adding a new package; understanding where dependencies are declared; knowing what to run after adding a dependency; understanding how security scanning covers new dependencies. DO NOT USE FOR: general coding; writing tests; deployment.
How to use the project Python virtual environment when running Python commands directly. USE FOR: running a Python script or command that has no make target; activating the venv manually; understanding which Python binary to use; troubleshooting "module not found" errors when running python directly. DO NOT USE FOR: tasks that already have a make target (use the use-makefile skill instead).