proflead/codex-skills-library - Page 2

zero-downtime-migration

Plan a zero-downtime migration for data or infrastructure. Use when a senior developer needs a safe migration strategy.

cost-optimization-review

Review system costs and propose reductions. Use when a senior developer needs cost-saving recommendations.

performance-budgeting

Define performance budgets and guardrails. Use when a senior developer needs performance targets and enforcement.

performance-trace-guide

Guide collection and analysis of performance traces. Use when a mid-level developer needs to diagnose slowness.

scalability-assessment

Assess a system for growth bottlenecks. Use when a senior developer needs to evaluate scaling limits.

dependency-upgrade-plan

Plan safe dependency upgrades with risk notes. Use when a mid-level developer is tasked with upgrading libraries.

org-standardization

Define engineering standards across teams. Use when a senior developer needs to align practices.

pr-reviewer

Review a pull request for correctness, regressions, and missing tests. Use when a mid-level developer needs structured review guidance.

refactor-roadmap

Create a staged refactor plan for a module. Use when a mid-level developer needs a safe refactor path.

roadmap-prioritization

Prioritize roadmap initiatives with tradeoffs. Use when a senior developer needs help ranking projects.

simple-refactor

Suggest small refactors that improve readability without changing behavior. Use when a junior developer asks to clean up code.

tech-debt-portfolio

Assess and prioritize tech debt items. Use when a senior developer needs an investment plan for debt reduction.

vendor-evaluation

Evaluate third-party vendors for engineering fit. Use when a senior developer needs a structured vendor assessment.

incident-postmortem

Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.

reliability-slo-sla

Define or review SLOs and SLAs for a service. Use when a senior developer needs reliability targets.

compliance-readiness

Assess readiness for compliance audits. Use when a senior developer needs a gap analysis for standards.

config-hardening

Harden configuration and defaults for safer deployment. Use when a mid-level developer needs to reduce misconfig risks.

dependency-risk-audit

Audit dependencies for licensing, security, and maintenance risk. Use when a senior developer needs risk assessment.

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.

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.

integration-test-planner

Plan integration tests across modules or services. Use when a mid-level developer needs to verify system interactions.

unit-test-starter

Generate starter unit tests for a small function or module. Use when a junior developer needs test scaffolding and edge cases.