hub:backend-specialist
APIs, services, business logic. Equally fluent in Node.js (Express, Fastify, Next API routes), Python (FastAPI, Flask), and edge runtimes.
What it's good at
- REST / GraphQL / tRPC endpoint design — with validation at the boundary.
- Business logic organised into services, not fat controllers.
- Auth flows, rate limiting, idempotency, webhooks.
- Integrations — Stripe, Resend, Twilio, S3 — with the right error model.
What it won't do
- Design the schema.
hub:database-architecthandles that first. - Build UI. frontend-specialist.
- Deploy.
hub:devops-engineer.
Skills it loads
api-patterns, clean-code, nodejs-best-practices, python-patterns, fastapi-expert, sqlalchemy-expert, mcp-builder, database-design, lint-and-validate(13 total — the agent picks what's relevant).
When Claude auto-dispatches it
Triggers: API, endpoint, route, service, webhook, REST, GraphQL, tRPC, FastAPI, backend, server, auth, database integration.
Example session
Add a Stripe webhook
user
add a /api/webhooks/stripe route that validates the signature and updates the subscription state
hub:backend-specialist
Shape: POST, raw body, stripe-signature header verify via Stripe SDK, idempotent upsert against subscriptions table.
Wrote:
app/api/webhooks/stripe/route.ts— usesconfig.api.bodyParser = false-style raw read in App Router.lib/stripe/webhook.ts— handlers per event type, each pure and unit-testable.lib/stripe/verify.ts— signature + timestamp-skew check.
Tests:
- Replay attack rejected (stale timestamp).
- Unknown event type returns 200 but no-ops.
- Duplicate event id — idempotent, no double-update.
Left a STRIPE_WEBHOOK_SECRET entry in .env.example.
Direct call
/hub:agent-backend-specialist add webhook for Stripe subscriptions with signature verify@hub agent-backend-specialist add webhook for Stripe subscriptions with signature verifyPro tips
- Say the validation library. “Zod”, “Pydantic”, “joi” — it'll match your project's style.
- Ask for tests explicitly for webhooks and auth flows. The agent will write happy-path only otherwise.
- Pair it with security-auditor for anything touching auth, billing, or PII.
Next steps
- Security auditor — review what backend-specialist wrote.
- Clean code — the floor for every diff.
- All agents