claude-superpowers

Execute a structured code review protocol that inspects code quality against the full rule set. Use when auditing code written by yourself or another agent, during code audit workflows, or when the user asks for a code review. Produces a findings document with severity tags.

Structured research protocol for investigating technologies, patterns, and APIs before implementation. Use when exploring unfamiliar technologies, evaluating library options, or documenting technical findings. Covers multi-tool search strategy, research log conventions, and training data fallback honesty protocol.

Apply WCAG accessibility standards when building UI components, forms, interactive elements, or any user-facing interface. Covers semantic HTML, ARIA attributes, keyboard navigation, color contrast, and screen reader support.

Document significant architectural decisions using the ADR (Architecture Decision Record) format. Use during research phases when choosing between approaches, when introducing new dependencies or patterns, or when the user asks to document a technical decision.

Apply REST/HTTP API design conventions when implementing endpoints, handlers, middleware, request validation, or response formatting. Covers resource naming, status codes, error formats, versioning, and pagination.

Apply Kubernetes deployment and GitOps patterns when configuring container orchestration, deployment strategies (rolling, blue-green, canary), ArgoCD/Flux manifests, or Kubernetes secrets management. Supplement to ci-cd-principles.

Apply CI/CD pipeline design patterns when configuring build pipelines, deployment processes, release strategies, Dockerfiles, or GitHub Actions workflows. Covers pipeline stages, artifact management, environment promotion, and rollback strategies.

Apply safe command execution patterns when spawning external processes, shell commands, or system calls from application code. Covers input sanitization, timeout handling, output capture, and error propagation.

Apply concurrency and parallelism patterns when implementing goroutines, async/await, threads, channels, mutexes, worker pools, or any concurrent data access. Covers race condition prevention, deadlock avoidance, and message passing.

Apply configuration management patterns when working with environment variables, config files, settings structs, secrets injection, or feature toggles. Covers validation, layering, fail-fast on missing config, and twelve-factor app principles.

Apply data serialization best practices when encoding, decoding, or validating structured data formats (JSON, YAML, XML, Protocol Buffers, MessagePack). Covers schema validation, versioning, backward compatibility, and safe deserialization.

Apply database design patterns when creating schemas, writing migrations, designing queries, managing indexes, or working with transaction boundaries. Covers normalization, query optimization, connection pooling, and migration safety.

Execute a structured debugging protocol to systematically identify root causes of software issues. Use when diagnosing complex bugs, flaky tests, intermittent failures, or unknown system behavior by forming hypotheses and validating them through specific, reproducible tasks.

Apply dependency management best practices when adding, updating, or auditing project dependencies in go.mod, package.json, Cargo.toml, pubspec.yaml, or requirements.txt. Covers version pinning, vulnerability scanning, and dependency hygiene.

Apply feature flag patterns ONLY when explicitly required by the PRD or technical architecture document. Covers flag evaluation rules, lifecycle management, testing strategies, and infrastructure requirements. Do NOT load speculatively.

Apply git workflow conventions when creating branches, writing commit messages, managing pull requests, or resolving merge conflicts. Covers conventional commits, branch naming, PR hygiene, and release tagging.

Run pre-flight checklists before writing code and post-implementation self-review after writing code. Use at the start of implementation to verify readiness, and after writing code but before verification to catch architectural violations, missing observability, and security oversights early.

Apply structured logging and observability implementation patterns when adding log statements, configuring loggers, implementing correlation IDs, or setting up telemetry. Covers log levels, structured fields, context propagation, and language-specific logger setup.

Generate distinctive, production-grade mobile interfaces for Flutter and React Native with platform-native patterns, adaptive layouts, and fluid motion. Use when building mobile app screens, widgets, or when the user requests visually striking mobile UI with proper iOS/Android conventions.

Apply health check and metrics patterns when implementing readiness/liveness probes, instrumenting RED/USE metrics, integrating error tracking, or adding production observability code. Covers Prometheus metrics, health endpoints, and alert threshold design.

Execute profile-driven performance optimization using a structured methodology. Use when profiling data (CPU, heap, trace, flamegraph) is available, when the user requests performance analysis, or when a benchmark regression is detected. Covers prioritization, pattern catalog, safety invariants, and when-to-stop heuristics. Language-specific tooling in languages/*.md.

Apply performance optimization principles when profiling, benchmarking, or optimizing hot paths. Covers the measure-first methodology, identifying bottlenecks, caching strategies, and when to stop optimizing. For hands-on profiling workflows, use the perf-optimization skill instead.

Apply resource lifecycle management patterns when working with files, database connections, network sockets, locks, or any resource requiring explicit cleanup. Covers RAII, defer/finally, connection pooling, graceful shutdown, and leak prevention.

Perform dynamic, reflective problem-solving through iterative thought chains with built-in revision and branching. Use for complex planning, multi-step analysis, hypothesis verification, or any problem where the full scope isn't initially clear and thinking may need course correction.