phinx-skills

Senior-level backend API engineering covering REST design, authentication, authorization, database access patterns, error handling, logging, and service architecture. Use this skill whenever building, reviewing, or debugging API endpoints, middleware, services, repositories, database queries, auth flows, or any server-side code. Also trigger for discussions about API design, microservices vs monolith, request validation, rate limiting, caching strategy, or when the user mentions Go, Django, FastAPI, Express, Fiber, GORM, SQLAlchemy, Prisma, or any backend framework.

Foundational software engineering principles covering SOLID, design patterns, clean code, clean architecture, and refactoring. Use this skill whenever writing new code, refactoring existing code, designing classes or modules, making structural decisions, or discussing code organization. Also trigger when the user mentions SOLID, DRY, KISS, YAGNI, design patterns, Factory, Strategy, Observer, Builder, Adapter, clean code, clean architecture, hexagonal architecture, coupling, cohesion, dependency injection, abstraction, polymorphism, inheritance vs composition, Law of Demeter, separation of concerns, or any foundational software design topic. This is the most fundamental skill — it underpins all other engineering skills.

Senior-level code review standards and PR quality assessment. Use this skill whenever reviewing pull requests, providing code feedback, evaluating code quality, refactoring, or discussing code review practices. Also trigger when the user says 'review this', 'check my code', 'is this good?', 'improve this', asks about clean code principles, SOLID, DRY, code smells, refactoring, or naming conventions.

Senior-level database design, schema modeling, query optimization, and migration strategy. Use this skill whenever designing database schemas, writing migrations, optimizing queries, choosing indexes, or making decisions about database technology. Also trigger when the user discusses PostgreSQL, MySQL, MongoDB, Redis, data modeling, normalization, denormalization, N+1 queries, query plans, partitioning, replication, or any database-related topic.

Senior-level DevOps and infrastructure engineering covering Docker, CI/CD, cloud platforms, monitoring, alerting, and deployment strategies. Use this skill whenever building Dockerfiles, docker-compose configs, CI/CD pipelines, Terraform/IaC, Kubernetes manifests, Nginx configs, deployment scripts, monitoring setup, or any infrastructure code. Also trigger when discussing deployment strategies, scaling, observability, secrets management, SSL/TLS, load balancing, or when the user mentions Docker, K8s, AWS, GCP, GitHub Actions, GitLab CI, Terraform, Ansible, Prometheus, Grafana, or any DevOps tool.

Senior-level technical documentation covering API docs, ADRs, runbooks, READMEs, and system documentation. Use this skill whenever writing or reviewing technical documentation, README files, API documentation, architecture decision records, runbooks, onboarding guides, or inline code documentation. Also trigger when the user mentions docs, documentation, README, ADR, runbook, OpenAPI, Swagger, or asks 'how should I document this'.

Senior-level React, Next.js, and TypeScript frontend engineering. Use this skill whenever building, reviewing, or debugging React components, pages, hooks, state management, data fetching, forms, or any frontend UI code. Also trigger when discussing frontend architecture, component APIs, accessibility, performance optimization, SSR/SSG, or when the user mentions React, Next.js, TypeScript, Tailwind, Zustand, TanStack Query, or any frontend library.

Senior-level Git workflow, branching strategy, commit conventions, and release management. Use this skill whenever creating branches, writing commits, managing PRs, resolving merge conflicts, setting up Git hooks, tagging releases, or discussing Git workflow. Also trigger when the user mentions Git, branching strategy, trunk-based development, GitFlow, conventional commits, rebasing, cherry-picking, release management, or changelogs.

Senior-level performance optimization covering profiling, caching, database tuning, frontend performance, and scalability. Use this skill whenever optimizing slow code, profiling performance bottlenecks, implementing caching, tuning database queries, optimizing bundle size, improving page load times, or discussing performance benchmarks. Also trigger when the user mentions slow API, high latency, memory leak, CPU usage, load testing, benchmarking, Core Web Vitals, or any performance concern.

Senior-level product thinking for engineers covering requirements analysis, user stories, PRDs, feature scoping, and prioritization. Use this skill whenever writing product requirements, user stories, acceptance criteria, feature specifications, or when making product decisions as an engineer. Also trigger when the user discusses MVP scope, feature prioritization, user experience, stakeholder communication, technical trade-offs with product impact, or asks 'what should we build' or 'how should we scope this'.

Senior-level security engineering and code review for vulnerabilities. Use this skill whenever reviewing code for security issues, implementing authentication/authorization, handling user input, managing secrets, configuring CORS, setting up SSL/TLS, or discussing OWASP vulnerabilities. Also trigger when the user mentions security audit, penetration testing, threat modeling, XSS, CSRF, SQL injection, IDOR, rate limiting, encryption, or any security concern.

Senior-level system design and software architecture. Use this skill whenever designing a new system, discussing architecture trade-offs, evaluating scalability, planning microservices boundaries, designing data flow, or making build-vs-buy decisions. Also trigger when the user asks about distributed systems, event-driven architecture, CQRS, message queues, load balancing, caching layers, service mesh, API gateways, or any architectural decision that spans multiple components.

Senior-level testing philosophy, patterns, and strategy. Use this skill whenever writing tests, designing test architecture, discussing test coverage, debugging flaky tests, setting up testing infrastructure, or choosing testing tools. Also trigger when the user mentions unit tests, integration tests, E2E tests, TDD, mocking, fixtures, test coverage, Pytest, Jest, Vitest, Playwright, Cypress, React Testing Library, or any testing framework or pattern.