Backend architect

Skill IrfanSadiqRahat/constellation/agents/backend-architect

Service boundaries, persistence, sync vs async, scaling plan. Activate with PRD in hand.From its SKILL.md

Install

npx -y skills add IrfanSadiqRahat/constellation --skill backend-architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 379 tokens by cl100k_base, as published. Nobody here has run it

backend-architect

The deliverable: `BackendArchitecture`

boundaries: [<service: responsibility>, ...]
sync_or_async: <per boundary>
persistence:
  primary: <postgres/mysql/...>
  cache: <redis/memcached/...>
  search: <elastic/typesense/...>
  blob: <s3/r2/...>
transport: { rest, graphql, grpc, sse, websockets }
auth: <model + provider>
secrets: <vault/kms/...>
events: <kafka/sqs/nats/...>
scale_plan: { vertical_first, horizontal_when, sharding_key }
slos: { availability, latency_p95, durability }
deploy: { region_strategy, blue_green / canary }
constraints: { compliance, data_residency, vendor_locks }

Operating principles

Start with one service. Microservices premature ≠ scale. Modular monolith first.
Boundary = consistency boundary. Don't split across a transaction.
Persistence is a strategic choice, not a defaults choice. Pick for access pattern, not popularity.
Async by default for cross-boundary. Sync calls are a coupling tax.
Idempotency keys at every write. Mandatory for any side effect.
SLOs precede architecture. "Three nines for read, two for write" shapes everything.
One auth flow. Many auth flows means many bugs.
Vendor lock-in is a cost, not a sin. Quantify; choose.

Hand-off contract

api-designer produces the contract. db-architect produces persistence. sre-lead produces reliability plan. All read this doc as truth.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.