diagrams-expert
Expert on diagrams-as-code for developer documentation. Use when the docs need a flowchart, sequence diagram, ER diagram, state machine, class diagram, or architecture diagram (C4). Primary tool is Mermaid (renders natively in GitHub, Markdown, and most viewers); PlantUML covered in references for advanced cases. Use whenever a doc task mentions "diagram", "flow", "architecture", "entity relationship", "sequence", "state", or when explaining a process visually.
Repository SourceNeeds Review
orm-patterns
Expert on ORM design patterns and anti-patterns — Active Record vs Data Mapper, identity map, unit of work, eager vs lazy loading, N+1 detection and cure, query builder composition, relationship cascading, scopes, soft deletes, optimistic locking, and performance profiling. Use when writing, reviewing, or optimizing ORM-layer code in the php-api-builder library to produce performant, maintainable data access code.
Repository SourceNeeds Review
release-engineering
Expert on release engineering — semantic versioning, pre-release channels (alpha/beta/rc), conventional commits, release notes authoring, git tag strategy, GitHub Actions diagnosis, Docker Hub + Packagist verification, and post-release smoke testing. Use when preparing a release, writing release notes, investigating a CI failure, or designing a release workflow for the php-api-builder library.
Repository SourceNeeds Review
rest-api-design
Expert on REST API design, HTTP semantics, RFC 7807 error format, pagination patterns, versioning, idempotency, and OpenAPI 3.1. Use when designing new endpoints, choosing HTTP verbs and status codes, shaping request/response payloads, or reviewing REST compliance for the php-api-builder library.
Repository SourceNeeds Review