code-review
25Cursor rule
Code review guidelines — scoring criteria, review structure, focus areas, and output format. Applied when reviewing code or PRs.
Cursor rule
Code review guidelines — scoring criteria, review structure, focus areas, and output format. Applied when reviewing code or PRs.
Cursor rule
Database design guidelines — relational normalisation, indexing, constraints, NoSQL patterns, query optimisation, migrations, security, and backup strategies. Applied when working with database schemas and queries.
Cursor rule
DevOps practices — CI/CD pipeline design, Docker containerisation, Kubernetes orchestration, Infrastructure as Code, monitoring, logging, and security. Applied when working with deployment and infrastructure files.
Cursor rule
Universal architecture and design principles — stack-agnostic. Applied when making structural decisions, reviewing design proposals, choosing patterns, or reasoning about system boundaries and evolution.
Cursor rule
Universal software engineering principles — stack-agnostic. Clean code, SOLID, clean architecture, error handling, testability, naming, and design quality. Applied whenever writing, reviewing, or reasoning about any code.
Cursor rule
Universal security principles — stack-agnostic. Applied when writing any code that handles input, authentication, authorisation, secrets, or sensitive data. Aligned with OWASP Top 10.
Cursor rule
OWASP AI Security & Privacy Guide – PR rules emphasizing data protection, governance, and safety.
Cursor rule
OWASP Top 10 for LLM Applications – actionable PR rules for AI features and agent tools.
Cursor rule
Performance optimisation guidelines — bundle optimisation, memory management, rendering, network, Electron-specific, and monitoring strategies. Applied when working on performance-sensitive code.
Cursor rule
Pull request templates, commit conventions, code review standards, and quality gates. Applied when creating PRs, writing commits, or reviewing code.
Cursor rule
Security guidelines — OWASP Top 10 mitigations, authentication, authorisation, encryption, input validation, and secure coding practices. Applied when writing or reviewing code that handles input, identity, secrets, or sensitive data.
Cursor rule
Testing strategies and quality assurance — testing pyramid, unit/integration/E2E testing, TDD/BDD, test automation, and quality metrics. Applied when writing or reviewing tests.
Skill Claude CodeCodex
Senior software architect and principal engineer reasoning — stack-agnostic. Evaluates design proposals, trade-offs, boundaries, complexity, and system evolution. Use when the user says "/architect", "design this", "evaluate this approach", "is this too complex", "architecture review", "trade-off analysis", "should I…
Skill Claude CodeCodex
Autonomous implementation workflow for low-supervision execution with mandatory decision logging. Executes end-to-end without interactive approval gates, but persists auditable run logs and architecture decisions in project artifacts. Use when the developer asks for autonomous mode, low supervision, or unattended…
Skill Claude CodeCodex
Capture the current work state so a developer, another agent, or a future session can resume without losing context. Use when the developer says "checkpoint", "save state", "checkpoint this", "handoff", "pause here", or "resume later".
Skill Claude CodeCodex
Systematic, evidence-based code review — runs mandatory searches before any manual analysis, then produces a structured report with severity-classified findings. Stack-agnostic core with stack-specific searches and commands injected at install time. Use when the user says "/review", "code review", "review this", "PR…
Skill Claude CodeCodex
Adversarial reviewer for high-impact decisions. Challenges the chosen approach from a clean, skeptical perspective — counter-argument, viable alternative, failure signals, and a Go/Go with conditions/Stop verdict.
Skill Claude CodeCodex
Preview skill for council review of an idea, hypothesis, or implementation direction from multiple perspectives before turning it into a spec, ticket, ADR, or code change. Use when the developer says "council", "idea review", "validate this idea", "review this hypothesis", "should we build this", "implementation…
Skill Claude CodeCodex
Minimal-friction implementation path for well-scoped tasks. Assumes the developer has full context, knows the codebase, and does not need planning ceremony. Use when the developer says "/express", wants to move fast on a well-understood single-layer change, or explicitly opts out of the full workflow.
Skill Claude CodeCodex
Infrastructure as Code for .NET on Azure - defines, reviews, and troubleshoots Bicep and Terraform for .NET applications. Use when the user says "/iac", "infrastructure", "Bicep", "Terraform", "ARM template", "provision resources", "Azure resources", "deploy infra", "cloud setup", "new environment", or wants to…
Skill Claude CodeCodex
Senior implementation lead — orchestrates the full feature lifecycle from problem exploration to commit. Enforces gated approval before writing code, incremental quality checks during implementation, and handoff to code-review for final validation. Stack-agnostic by default; loads stack-specific references when a…
Skill Claude CodeCodex
Capture a durable project lesson in Agent Runway memory. Use when the developer says "learning", "remember this", "save this lesson", "add to memory", or when a completed task reveals a recurring decision, failure, convention, or guardrail that should influence future work.
Skill Claude CodeCodex
Evaluates product quality of specs and tickets before implementation. Focuses on business value, clarity, scope, success metrics, risks, dependencies, and readiness from a Product Owner perspective. Use when the user says "/po-eval", "evaluate this spec", "evaluate this ticket from PO view", or "is this product-ready".
Skill Claude CodeCodex
Guides structured refactoring to improve readability, maintainability, and SOLID/Clean Architecture alignment — without changing observable behaviour. Deepest examples are in .NET/C#, but the workflow applies to any stack. Use when the user says "/refactor", "clean up", "improve this", "simplify", "restructure"…