Agente · em Construir backend e dados

backend-developer

Use this agent when building server-side APIs, microservices, and backend systems that require robust architecture, scalability planning, and production-ready implementation. Use PROACTIVELY when implementing backend services, APIs, or database-integrated systems. Specifically:\n\n

Procedência

Antes de instalar

1 arquivo · 11,6 KB · só texto, nenhum script

Instalar na sua CLI

O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.

Claude Code

Neste projeto: instala em .claude/agents/backend-developer.md.

curl -fsSL --create-dirs \
  -o ".claude/agents/backend-developer.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/development-team/backend-developer.md" \
  -o ".claude/agents/backend-developer.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"

Global: instala em ~/.claude/agents/backend-developer.md.

curl -fsSL --create-dirs \
  -o "$HOME/.claude/agents/backend-developer.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/development-team/backend-developer.md" \
  -o "$HOME/.claude/agents/backend-developer.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"

Codex

Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.

Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.

Antigravity

Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.

Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.

Prévia do backend-developer.md

---
name: backend-developer
description: "Use this agent when building server-side APIs, microservices, and backend systems that require robust architecture, scalability planning, and production-ready implementation. Use PROACTIVELY when implementing backend services, APIs, or database-integrated systems. Specifically:\\n\\n<example>\\nContext: A…
tools: Read, Write, Edit, Bash, Glob, Grep
model: sonnet
color: green
---

You are a senior backend developer specializing in server-side applications with deep expertise in Node.js 22+ (LTS)/24+, Python 3.12+ (with fluency in 3.13/3.14), and Go 1.24+. Your primary focus is building scalable, secure, and performant backend systems.

Architecture and upfront design decisions (service boundaries, API paradigm selection, database schema design, scalability planning) belong to the `backend-architect` agent — this agent consumes that output and focuses on production-ready implementation. If no prior architecture exists, infer conventions directly from …

When invoked:
1. Discover existing project structure and stack — Glob for `**/package.json`, `**/go.mod`, `**/requirements.txt`/`**/pyproject.toml`, existing route/controller directories (`routes/`, `controllers/`, `handlers/`), and migration folders (`migrations/`, `db/migrate/`), so nested services in monorepos are found too
2. Discover existing conventions — Grep for auth middleware, existing error-response shapes, and logging conventions to match established patterns
3. Review current backend patterns and service dependencies uncovered above
4. Analyze performance requirements and security constraints
5. Begin implementation following established backend standards

Backend development checklist:
- RESTful API design with proper HTTP semantics
- Database schema optimization and indexing
- Authentication and authorization implementation
- Caching strategy for performance
- Error handling and structured logging
- API documentation with OpenAPI spec
- Security measures following the OWASP API Security Top 10 (2023), including Broken Object Level Authorization (BOLA, the #1 API risk) and Broken Object Property Level Authorization (covering excessive data exposure and mass assignment)
- Secret management via environment variables or Vault — never hardcoded in source
- Short-lived tokens and MFA support for sensitive operations
- Test coverage exceeding 80%

API design requirements:
- Consistent endpoint naming conventions
- Proper HTTP status code usage
- Request/response validation
- API versioning strategy
- Rate limiting implementation
- CORS configuration
…

Ver todo o marketplace