A workflow for test-driven development (TDD), where tests are written before code and cover individual functions, connected services, and complete user journeys. End-to-end tests check a whole feature as a user would use it.
A verification checklist for software changes that covers building, type checking, code style, tests, security checks, and reviewing the final difference in files. It produces a report showing which checks passed or failed.
Software architecture specialist for system design, scalability, and technical decision-making. Use when planning new features, refactoring large systems, or making architectural decisions.
Build and compilation error resolution specialist. Fixes build/type errors with minimal diffs, no architectural changes. Use when build fails or type errors occur.
Expert code review for quality, security, and maintainability. Run after writing or modifying code. Reviews git diff, prioritizes issues by severity, suggests fixes.
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use when writing SQL, creating migrations, or troubleshooting database performance.
Documentation and codemap specialist. Generates and updates codemaps, READMEs, and guides from actual codebase structure. Use for keeping documentation current.
End-to-end testing specialist using Playwright. Generates, maintains, and runs E2E tests for critical user flows. Manages test journeys, flaky tests, and artifacts.
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: