spring-microservices-architectlisted
Production-grade governance agent for Spring Boot microservices. Scaffolds projects iteratively using capability-based layering, enforces coding standards, and validates against battle-tested reference patterns. Fully portable — works with any domain. USE FOR: microservice, Spring Boot, scaffold, Docker compose, kubernetes, helm, eureka, gateway, resilience4j, reactive, spring cloud, openapi, persistence, security, oauth, tracing, zipkin, monitoring, prometheus, grafana, native compilation, graalvm, code review, architecture review, quality gate, governance, spring cloud stream, rabbitmq, kafka, testcontainers, mapstruct, service discovery, edge server, config server, circuit breaker, distributed tracing, entity, entities, domain model, generate entity, persistence model, create entity, MongoDB document, JPA entity, MapStruct mapper, repository, test, verify, validate, TDD, test-driven, failing test, integration test, build check, regression test, quality check, security database, MFA, multi-factor, WebAuthn,
jaykumarpatil/commerce · ★ 0 · DevOps & Infrastructure · score 61
Install: claude install-skill jaykumarpatil/commerce
# Spring Microservices Architect Skill
Production-grade **software architect governance agent** for Spring Boot microservice projects. Scaffolds new microservices iteratively using capability-based layering, enforces coding standards, and validates against battle-tested reference patterns.
**Fully portable** — not tied to any specific domain. Works for e-commerce, logistics, fintech, SaaS, or any microservice architecture. See [project-config.md](references/project-config.md) for adoption.
---
## Transferability
This skill generates code for **your** services, not a fixed set. To adopt it for a new project:
1. Read [project-config.md](references/project-config.md) and create `.agents/project.yml`
2. Set `${basePackage}`, define your services, assign ports
3. Run `scaffold` — the skill generates YOUR project structure
4. All patterns (persistence, messaging, security, k8s) apply to any service names
> Templates use `<Entity>`, `<Service>`, and `${basePackage}` placeholders. You provide the concrete names.
---
## Context Gathering
Before each interaction, gather project state with these commands:
| Command | Purpose |
|---------|---------|
| `git log --oneline -10` | Detect current capability layer from commit history |
| `docker compose ps --format json 2>/dev/null` | Running containers to understand runtime landscape |
| `./gradlew projects --quiet 2>/dev/null` | Gradle multi-project structure — which modules exist |
| `cat .agents/project.yml 2>/dev/null` | Projec