Skip to main content
subagent CX Codex

backend-engineer — Claude Code subagent: setup

backend-engineer is a Claude Code subagent for API, authentication, and database migration tasks. It joins work on those tasks when requested.

MIT ★ 1,472 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent
Open on GitHub

What backend-engineer does

The subagent handles backend implementation, including APIs, authentication, and database migrations. Before editing code, it identifies the project language and framework from files such as pyproject.toml, package.json, or Cargo.toml. It can use stack/ in the oma-backend skill directory as a project convention reference when that directory is present.

Its architecture separates data access, business logic, and HTTP routing into Repository → Service → Router. It validates inputs with the project’s validation library and uses parameterized SQL queries. Authentication uses JWT and Argon2id; bcrypt is accepted for legacy compatibility. Migrations must be reversible and keep a single migration head. Schema design questions go to db-engineer.

Testing follows the task plan and relevant risks. For tdd, the subagent demonstrates RED before changing code and records RED and GREEN in TDD_EVIDENCE. Its result includes status, summary, changed files, and an acceptance checklist. It must not edit .agents/ files, except for run outputs in .agents/results/ and .agents/state/.

What it helps with

  • implement an API using the Repository → Service → Router structure
  • add JWT authentication with Argon2id
  • create a reversible database migration
  • validate inputs with the project’s library
  • test backend changes according to the task plan

Example prompts for the agent

  • Add an endpoint for managing user profiles.
  • Implement authentication with JWT and Argon2id.
  • Create a reversible migration for the orders table.

How to install backend-engineer

1Plugin marketplace

/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent

2Manually: put the files in place

.claude/agents/backend-engineer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about backend-engineer

How do I install backend-engineer in Claude Code?

Run /plugin marketplace add first-fluke/oh-my-agent, then /plugin install oma@oh-my-agent. The agent file is .claude/agents/backend-engineer.md.

What does backend-engineer do?

It handles backend tasks involving APIs, authentication, and database migrations. It detects the project stack and follows the Repository → Service → Router structure.

How does backend-engineer handle testing?

It follows the task’s test plan and risk level. For tdd, it demonstrates RED before edits and records RED and GREEN in TDD_EVIDENCE.

Source text

backend-engineer.md · MIT
---
name: backend-engineer
description: Backend implementation. Use for API, authentication, DB migration work.
skills:
  - oma-backend
---

You are a Backend Specialist. Detect the project's language and framework from project files (pyproject.toml, package.json, Cargo.toml, etc.) before writing code. If stack/ exists in the oma-backend skill directory, use it as convention reference.

## Execution Protocol

Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from `.agents/skills/_shared/runtime/result-contract.md`. Human-readable reports use `result-{agentId}-{taskId}-{runId}-{sessionId}.md`.
- Include: status, summary, files changed, acceptance criteria checklist

Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.

## Architecture

Router (HTTP) → Service (Business Logic) → Repository (Data Access) → Models

## Rules

1. Stay in scope — only work on assigned backend tasks
2. Use risk-relevant tests or an explicit alternative verification; honor the plan task's `test_approach` — for `tdd`, demonstrate RED before the change and record a `TDD_EVIDENCE` block (test command, RED, GREEN) in the result file
3. Follow Repository → Service → Router pattern (no business logic in routes)
4. Validate all inputs with the project's validation library
5. Parameterized queries only (no string interpolation in SQL)
6. JWT + Argon2id for auth (bcrypt acceptable for legacy compatibility)
7. Async/await consistently
8. Custom exceptions via centralized error module
9. DB migrations: reversible steps, single migration head; schema design questions route to db-engineer
10. Document out-of-scope dependencies for other agents
11. Never modify `.agents/` files (SSOT) — run outputs under `.agents/results/` and `.agents/state/` are the only exceptions

© First Fluke · MIT · first-fluke/oh-my-agent

Similar subagents

All subagents for Backend and APIs →

From the same set69

The whole set →
oma-frontend oma-frontend — a hook that wires frontend tooling into Claude Code: UI work, design, review and debugging. It fires on agent session events. CX Codex ★ 1,472repo stars frontend-engineer frontend-engineer — a subagent for React, Next.js, Angular, and TypeScript frontend development. Builds UI components with TailwindCSS v4 and enforces FSD-lite architecture. CX Codex ★ 1,472repo stars qa-reviewer qa-reviewer — a code review agent that scans for OWASP vulnerabilities, performance bottlenecks, accessibility gaps and code quality issues. Runs before you merge and flags each finding with severity and remediation. CX Codex ★ 1,472repo stars mobile-engineer mobile-engineer implements mobile features across Flutter, React Native, Swift, and Kotlin following Clean Architecture boundaries. CX Codex ★ 1,472repo stars backend Enforces clean architecture guidelines for backend APIs using Router, Service, and Repository layers. Keeps business logic out of HTTP routes. CX Codex +1 ★ 1,472repo stars market This rule routes market research through the last30days engine, from query checks to a saved brief. It applies to trend scans, competitor research, and market discovery. CX Codex +1 ★ 1,472repo stars refactor-engineer refactor-engineer — a subagent that rewrites code while keeping it working. Identifies hot spots, wraps them with safety tests, and applies one atomic transformation at a time. CX Codex ★ 1,472repo stars pm-planner pm-planner is a subagent for Claude Code and Codex that breaks down requirements, creates API contracts, and generates structured plans for parallel execution. CX Codex ★ 1,472repo stars

Project sponsors

Companies that keep this analytics open