engineering-skills

Use when the user wants to free disk space, investigate disk usage, clean caches, remove unused artifacts, or when disk capacity is high. Also use when asked to "clean up", "free space", "disk full", or "what's using disk space". Always uses AskUserQuestion for every deletion decision.

Use at the start of every conversation and for every user message — orchestrates the full engineering skills suite by understanding intent, clarifying requirements interactively, and invoking the right skills

Use when refactoring Go code, cleaning up legacy codebases, optimizing performance, or enforcing clean architecture boundaries in a Go/Fiber backend

Use when refactoring Python code, cleaning up legacy codebases, optimizing performance, enforcing type safety, or improving clean architecture in a FastAPI backend

Use when refactoring React components, cleaning up legacy frontends, optimizing performance, improving component architecture, or reducing bundle size

Use when reviewing changed code before committing or after completing a feature — checks performance, architecture, type safety, and code quality against project standards

Use after any skill completes work that changes project structure, conventions, commands, environment variables, dependencies, or architecture — proactively updates CLAUDE.md so future sessions inherit current project state

Use when debugging any issue in Go, Python, or React applications — provides hands-on investigation tools including Docker inspection, API probing, log analysis, database queries, and browser debugging

Use when onboarding to a codebase, inheriting legacy code, after pulling changes, or for periodic health assessment — detects code quality debt, missing tests, architecture violations, and dead code in Go, Python, or React projects

Use when creating or updating Docker configurations, Dockerfiles, or docker-compose setups for Go, Python, or React projects

Use when making significant technical decisions that should be documented — framework choices, architecture patterns, trade-offs, and migration decisions

Use when designing API contracts between frontend and backend, implementing contract testing, or managing API versioning and breaking changes

Use when designing new API endpoints, reviewing API consistency, or establishing REST conventions for Go/Fiber or Python/FastAPI backends

Use when creating or updating CI/CD pipelines with GitHub Actions or GitLab CI for Go, Python, or React projects

Use when writing any production code in Go, Python, or React — enforces performance-first patterns, prevents N+1 queries, demands algorithmic efficiency, and ensures security safety at every layer

Use when creating or modifying database schema in Go projects using golang-migrate with PostgreSQL

Use when updating dependencies, running security audits, or managing tech debt in Go, Python, or React projects

Use when setting up deployment pipelines, Kubernetes manifests, environment promotion, or production infrastructure for Go, Python, or React applications

Use when implementing async processing, background jobs, webhooks, real-time events, or message queues in Go or Python applications

Use when implementing a new feature, endpoint, or use case in a Go/Fiber backend with clean architecture and PostgreSQL

Use when starting a new Go backend, API, or microservice with Fiber, PostgreSQL, and clean architecture

Use when adding logging, metrics, tracing, or error tracking to Go, Python, or React applications — structured observability from day one

Use when onboarding to a new codebase, setting up a new engineer, or generating project documentation like ARCHITECTURE.md, CONTRIBUTING.md, or CODEOWNERS

Use when implementing a new feature, endpoint, or use case in a Python/FastAPI backend with clean architecture, SQLAlchemy, and PostgreSQL

Use when creating or modifying database schema in Python projects using Alembic with SQLAlchemy 2.0 and PostgreSQL

Use when starting a new Python/FastAPI backend, API, or microservice with SQLAlchemy, Alembic, and clean architecture

Use when implementing a new React feature, page, component, or hook in a Vite/Bun frontend with testing-library

Use when starting a new React/Vite/Bun frontend with testing-library, feature-based structure, and typed API client

Use when implementing authentication, authorization, input validation, or security hardening in Go, Python, or React applications

Use for every interaction where clarification is needed — enforces AskUserQuestion tool over plaintext questions for all requirement gathering and decision making

Use when implementing product analytics, event tracking, user metrics, funnels, or A/B testing in Go, Python, or React applications

Use when designing database schema, entity relationships, or index strategy before writing migrations — for PostgreSQL with Go or Python

Use when production is broken, a service is down, or a critical bug is affecting users — structured incident management and postmortem

Use when starting a new feature, product, or project — before any architecture or code, to define what to build and why

Use when designing system architecture for a new project or major feature — service boundaries, data flow, API contracts, and technical trade-offs

Use when writing integration tests for Go services that need real PostgreSQL, Redis, or other external dependencies via testcontainers

Use when writing integration tests for Python/FastAPI services that need real PostgreSQL, Redis, or other external dependencies via testcontainers