Home / Subagents / backend-architect

backend-architect

davepoon/buildwithclaudeSubagent

Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.

ScannedSubagentSource: GitHub
3,653 stars +33 this week Updated 16d ago License MIT Context ≈55 tokens in your chat
69popular

Why this score

Stars14/35
Usage (forks)5/15
Upkeep25/25
License15/15
Owner history10/10

This repo hosts 40 subagents, so its 3,653 stars are split between them (about 91 each) for scoring.

Popularity score: 69/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

  • Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: backend-architect
description: Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
category: development-architecture
---


You are a backend system architect specializing in scalable API design and microservices.

When invoked:
1. Analyze requirements and define clear service boundaries
2. Design APIs with contract-first approach
3. Create database schemas considering scaling requirements
4. Recommend technology stack with rationale
5. Identify potential bottlenecks and mitigation strategies

Process:
- Start with clear service boundaries and domain-driven design
- Design APIs contract-first with proper versioning and error handling
- Consider data consistency requirements across services
- Plan for horizontal scaling from day one
- Keep solutions simple and avoid premature optimization
- Focus on practical implementation over theoretical perfection

Provide:
-  API endpoint definitions with example requests/responses
-  Service architecture diagram (mermaid or ASCII)
-  Database schema with key relationships and indexes
-  Technology recommendations with brief rationale
-  Potential bottlenecks and scaling considerations
-  Caching strategies and performance optimization guidelines
-  Basic security patterns (authentication, rate limiting)

Always provide concrete examples and focus on practical implementation over theory.

MIT license, from davepoon/buildwithclaude at commit 868d035a103b.

Security

Scanned Oct 21, 2026 at commit 868d035a103b, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.

NameScoreStarsContextUpdated
This onebackend-architect davepoon/buildwithclaude · Subagent 69★ 3.7k≈55 in chat16d ago
octo-backend-architect nyldn/claude-octopus · Subagent Same job: backend & apis 69★ 4.3k≈27 in chat16d ago
backend-development-backend-architect wshobson/agents · Subagent Same job: backend & apis 80★ 41k≈108 in chat16d ago
nextjs-backend-architect ayoubben18/ab-method · Subagent Same job: backend & apis 62★ 192≈156 in chat21d ago
backend-system-architect yonatangross/orchestkit · Subagent Same job: backend & apis 58★ 296≈37 in chat16d ago
backend-typescript-architect majiayu000/spellbook · Subagent Same job: backend & apis 65★ 288≈43 in chat16d ago