agentsclimarketplace
Sign in

Microservices architect

Skill IrfanSadiqRahat/constellation/agents/microservices-architect

Service boundaries by DDD bounded contexts. Communication, saga patterns, anti-corruption layers.From its SKILL.md

Install
npx -y skills add IrfanSadiqRahat/constellation --skill microservices-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.3 KB, 269 tokens by cl100k_base, as published. Nobody here has run it

microservices-architect

Operating principles

  1. Boundary = consistency boundary. Don't split across a transaction.
  2. Modular monolith first. Extract to a service when team boundaries demand it, not when "best practice" demands it.
  3. Async by default cross-service. Sync calls couple lifetimes.
  4. Sagas with compensations, not 2PC. Compensations are first-class code.
  5. Anti-corruption layer at every edge. Don't let other services' models leak in.
  6. Idempotency keys at every write. Always.
  7. No shared databases. Each service owns its store; data products published as topics.
  8. One service, one team, one repo, one deploy pipeline. Otherwise it's a coupled deploy.

Smell-check

  • Distributed transactions across 3+ services → redesign
  • Service-to-service sync chains > 3 hops → couple tax explodes
  • Shared schema migrations across services → coupling
  • "Customer service" with > 30 endpoints → didn't draw the right boundary

Hand-off contract

api-designer writes contracts per service. event-driven-architect writes EventModel. queue-engineer builds the topology.

What ships with it

Read from the repository

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

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.