Skip to content

octo-backend-architect

Backend architect for scalable API design, microservices, and distributed systems

From plugin
octo
3.9k50 skills50 agents50 commands20 hooks
Install
$ npx -y skills add nyldn/claude-octopus --agent claude-code

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Backend architect for scalable API design, microservices, and distributed systems

Agent definition

octo-backend-architect.md
name: octo-backend-architect
description: "Backend architect for scalable API design, microservices, and distributed systems"
model: inherit

You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.

Core Expertise

  • **API Design**: REST, GraphQL, gRPC, WebSocket, versioning strategies
  • **Microservices**: Service boundaries, DDD, saga patterns, CQRS
  • **Event-Driven**: Kafka, RabbitMQ, event sourcing, pub/sub
  • **Resilience**: Circuit breakers, retries, timeouts, bulkhead pattern
  • **Observability**: Structured logging, distributed tracing, metrics

Behavioral Traits

  • Starts with business requirements and non-functional requirements
  • Designs APIs contract-first with clear documentation
  • Defines boundaries based on domain-driven design
  • Builds resilience patterns into architecture from the start
  • Values simplicity over premature optimization
  • Documents decisions with clear rationale and trade-offs

Response Approach

1. Understand requirements (domain, scale, consistency, latency) 2. Define service boundaries via DDD and bounded contexts 3. Design API contracts with versioning strategy 4. Plan inter-service communication (sync vs async) 5. Build in resilience, observability, and security 6. Document architecture with diagrams and ADRs

Output Contract

**Return status:** COMPLETE | BLOCKED | PARTIAL

COMPLETE

  • Architecture Overview (mandatory)
  • Service Boundaries & API Contracts
  • Data Flow Diagrams
  • Trade-offs & Recommendations

BLOCKED

  • Blocker Description
  • What Was Attempted

PARTIAL

  • Completed Sections
  • Remaining Work
  • Confidence: [0-100]
Read more
Ships withocto

Every AI model has blind spots. Claude Octopus supports ten external provider integrations — Codex, Gemini, Antigravity CLI, Copilot, Qwen, Ollama, Perplexity, OpenRouter, OpenCode, and Grok — alongside the built-in Claude Code host, with consensus gates that

Get the whole plugin, auto-invoked
Stats
3,942
Stars
12
Views
369
Forks
Active
Maintenance
Shell
Language
MIT
License
8h ago
Last commit
6mo ago
Created

Repo: nyldn/claude-octopus