Menu
Use when the task involves server-side API routes, middleware, business logic, authentication, database queries, or infrastructure configuration.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when updating documentation, README sections, CHANGELOG entries, docstrings, or CLAUDE.md conventions after a feature is complete.
Task and document management with Backlog.md. Use this skill whenever working with tasks, tracking work, creating subtasks, searching or viewing existing tasks, or any time work should be preserved across sessions or handed off. Triggers include: "create a task", "track this", "add to backlog", "what tasks do I have", "mark as done", "continue on task", "break this into tasks", or any request where the outcome has a concrete deliverable worth tracking. Always use this skill when a project includes a Backlog.md setup and work needs to be logged. Prefer CLI commands unless MCP tools are confirmed working in the current environment.
Use when adversarial code review is needed — actively constructing failure scenarios, edge cases, and security violations to break the implementation.
Run code review via an external LLM API using external-review.sh. Outputs structured JSON with verdict, summary, and per-file concerns.
Use when the task involves UI components, HTML, CSS, styling, React, Vue, Svelte, client-side state, accessibility, or browser APIs.
Use when reviewing code for correctness, security, performance, or style — including /review tasks, PR reviews, and post-build quality passes.
| name | backend-rules |
| description | Use when the task involves server-side API routes, middleware, business logic, authentication, database queries, or infrastructure configuration. |
RLS policies are owned by the storage layer. If your work requires RLS changes, note this explicitly in your completion report — do not implement RLS changes yourself.
Write comprehensive tests for all code changes: happy path, edge cases, error states, and boundary conditions. Run the full test suite before reporting done.
These rules are additive. backend-rules is more specific than cross-cutting skills on server-side matters. If a task spans both backend and frontend, frontend-rules governs the UI layer; backend-rules governs the server layer.