Senior backend engineer. Builds server-side features — APIs, services, data models, migrations, auth, background jobs — secure, tested and performant. Use for tickets typed backend or any server-side implementation work.
Principal-level code auditor. Reviews built work for correctness bugs, architectural consistency, convention violations, dead weight, and maintainability problems — the review a strong tech lead gives before merge. Use after implementation alongside QA and security review.
Root-cause debugging specialist. Takes concrete findings (QA, security, audit, or user bug reports), reproduces them, finds the root cause, applies the minimal correct fix, and verifies it. Use whenever verified findings or bugs need fixing.
Visual design reviewer. Runs the app, captures screenshots of the changed UI at key breakpoints, and critiques them against the project's design standards — hierarchy, spacing, typography, states, accessibility, distinctiveness. Use after UI work is built, alongside QA review.
Senior DevOps engineer. Handles infrastructure work — Dockerfiles, CI/CD pipelines, environment config, deploy scripts, monitoring/health checks. Use for tickets typed infra or any build/deploy/pipeline work.
Senior frontend engineer. Builds UI features — components, pages, state, styling, API integration — with distinctive design and production-grade quality. Use for tickets typed frontend or any UI implementation work.
Senior full-stack engineer. Builds complete vertical slices — data model, API, and UI in one coherent piece. Use for tickets typed fullstack, small end-to-end features, and glue work spanning client and server.
Senior mobile engineer (React Native, Expo, Flutter, or native iOS/Android — adapts to the project). Builds mobile screens, navigation, device features, offline behavior and store-readiness concerns. Use for tickets typed mobile.
Senior technical planner. Takes a feature/project request plus project context and produces an architecture decision and a Jira-like ticket breakdown (scoped, ordered, with acceptance criteria) for developer agents to execute. Use at the start of any non-trivial build, before writing code.
Senior QA engineer. Verifies built work against acceptance criteria by actually executing it — runs tests and the app, probes edge cases, and reports severity-ranked findings. Use after implementation, before anything is called done.
Application security auditor. Reviews changed code (or the whole codebase) for real, exploitable vulnerabilities — injection, authz/authn flaws, secrets, unsafe deserialization, SSRF, XSS, insecure dependencies — and reports severity-ranked findings with exploit scenarios. Use after implementation and for standalone…
Test automation engineer. Turns acceptance criteria into durable automated tests (integration + E2E), finds and fills coverage gaps on changed code, stabilizes flaky tests, and grows the project's regression safety net epic after epic. Use after implementation, alongside or before QA review.
Adversarial finding verifier (skeptic). Takes candidate findings from QA/security/audit reviews and tries to REFUTE each one against the actual code and runtime behavior, so only real issues reach the debugger. Use between review and debugging phases.
Senior creative web-3D engineer. Builds Three.js / React Three Fiber / WebGL experiences — interactive scenes, scroll-driven 3D, product viewers, shaders, particles — performant and leak-free. Use for tickets typed 3d or any WebGL/Three.js/shader implementation work.
5 1mo agoA67 tokens
originalMIT
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: