config-hardening
Harden configuration and defaults for safer deployment. Use when a mid-level developer needs to reduce misconfig risks.
api-contract-checker
Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.
css-layout-helper
Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.
db-migration-reviewer
Review database migrations for safety and rollback. Use when a mid-level developer needs validation of schema changes.
linter-fix-guide
Explain lint errors and propose fixes. Use when a junior developer needs help resolving common lint or format warnings.
unit-test-starter
Generate starter unit tests for a small function or module. Use when a junior developer needs test scaffolding and edge cases.
graphql-query-optimizer
Optimize GraphQL queries and resolvers for performance. Use when a mid-level developer needs to reduce N+1 or payload size.
feature-flag-playbook
Plan feature flag rollout and cleanup. Use when a mid-level developer needs controlled release guidance.
incident-postmortem
Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.
readme-polish
Improve a README for clarity and completeness. Use when a junior developer needs guidance on documenting setup and usage.
integration-test-planner
Plan integration tests across modules or services. Use when a mid-level developer needs to verify system interactions.
debugging-checklist
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured, step-by-step approach.
org-standardization
Define engineering standards across teams. Use when a senior developer needs to align practices.
writing-assistant
Edits, rewrites, or improves text for clarity, tone, grammar, or style.
vendor-evaluation
Evaluate third-party vendors for engineering fit. Use when a senior developer needs a structured vendor assessment.
function-docstrings
Write concise docstrings for functions. Use when a junior developer needs help describing inputs, outputs, and errors.
security-quick-scan
Scan code or configuration for common security issues. Use when a mid-level developer needs a quick security pass.
threat-modeling
Perform threat modeling for a system or feature. Use when a senior developer needs security risk assessment.
log-summarizer
Summarize noisy logs into likely causes and next steps. Use when a junior developer needs help interpreting logs.
cross-service-debugger
Coordinate debugging across multiple services. Use when a senior developer needs to trace a distributed issue.
zero-downtime-migration
Plan a zero-downtime migration for data or infrastructure. Use when a senior developer needs a safe migration strategy.
observability-setup
Set up metrics, logs, and traces for a service. Use when a mid-level developer needs basic observability coverage.
dependency-upgrade-plan
Plan safe dependency upgrades with risk notes. Use when a mid-level developer is tasked with upgrading libraries.
refactor-roadmap
Create a staged refactor plan for a module. Use when a mid-level developer needs a safe refactor path.
prompt-optimization
Improve and rewrite user prompts to reduce ambiguity and improve LLM output quality. Use when a user asks to optimize, refine, clarify, or rewrite a prompt for better results, or when the request is about prompt optimization or prompt rewriting.
config-file-explainer
Explain a configuration file and its key options. Use when a junior developer is confused by a config file.
system-design-draft
Draft a practical system design for a feature. Use when a mid-level developer needs a starting architecture.
data-governance-check
Review data handling for privacy and retention. Use when a senior developer needs governance validation.
accessibility-basic-check
Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.
reliability-slo-sla
Define or review SLOs and SLAs for a service. Use when a senior developer needs reliability targets.
ticket-breakdown
Break a task or ticket into small steps. Use when a junior developer needs guidance on how to start.
caching-strategy-helper
Recommend caching strategies and invalidation patterns. Use when a mid-level developer needs performance guidance.
performance-trace-guide
Guide collection and analysis of performance traces. Use when a mid-level developer needs to diagnose slowness.
bug-repro-plan
Create a minimal, repeatable reproduction plan for a bug. Use when a junior developer needs clear steps to reproduce and capture evidence.
sql-query-starter
Draft a basic SQL query from a simple requirement. Use when a junior developer needs help forming SELECT statements.
queue-processing-patterns
Design safe queue consumers and retries. Use when a mid-level developer needs reliable background processing.
codebase-orientation
Guide quick orientation of an unfamiliar codebase with module mapping, entry points, and local run steps. Use when a junior developer needs to get situated fast.
architecture-review
Review a system architecture for scalability, reliability, and maintainability. Use when a senior developer needs to critique a design.
api-request-builder
Build a basic HTTP request (curl or fetch) for an API. Use when a junior developer needs a quick request example.
dependency-risk-audit
Audit dependencies for licensing, security, and maintenance risk. Use when a senior developer needs risk assessment.
multi-region-strategy
Design a multi-region architecture strategy. Use when a senior developer needs geo-redundant planning.
dependency-install-helper
Guide installation of project dependencies and toolchains. Use when a junior developer is stuck setting up the environment.
git-basic-helper
Provide safe git commands for common tasks. Use when a junior developer needs help with branching, commits, or resolving simple conflicts.
cost-optimization-review
Review system costs and propose reductions. Use when a senior developer needs cost-saving recommendations.
error-message-explainer
Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.
iac-reviewer
Review infrastructure-as-code changes for safety and correctness. Use when a mid-level developer needs a second look on IaC.
release-notes-drafter
Draft release notes from changes and PRs. Use when a mid-level developer needs a structured changelog.
ci-failure-triage
Diagnose CI failures and stabilize pipelines. Use when a mid-level developer needs to resolve flaky or failing builds.