{
  "markdown": "# Spring Standards — Claude Code Plugin\n\nProduction-grade engineering standards for Spring Boot projects. One skill that adapts to both **modular monoliths** and **microservices**.\n\n## What It Does\n\nWhen you work on a Spring Boot project with Claude Code, this plugin enforces:\n\n- **Hexagonal architecture** with clear domain/application/infrastructure separation\n- **Feature-oriented package structure** instead of framework-driven sprawl\n- **Explicit layer rules** — domain never depends on Spring, JPA entities stay in infrastructure, controllers delegate to use cases\n- **API design standards** — OpenAPI, consistent error contracts, validation at all levels\n- **Security baseline** — deny-by-default, least privilege, protected actuators\n- **Testing strategy** — unit, integration, contract, and non-functional tests with Testcontainers\n- **Observability** — structured logging, trace IDs, metrics, health endpoints\n- **Database discipline** — Flyway migrations, no Hibernate DDL in production\n\nThe skill automatically detects whether your project is a modular monolith or microservices system and loads the appropriate guide.\n\n## Install\n\n```bash\nclaude plugin add alexanderCanon/spring-standards\n```\n\n## Usage\n\nThe skill activates automatically when Claude detects Spring Boot work. You can also invoke it explicitly:\n\n```\n/spring-standards\n```\n\n## Architecture Coverage\n\n### Always Applied (Shared Foundation)\n- Hexagonal architecture + DDD-inspired boundaries\n- Package and module governance\n- API design, error handling, validation standards\n- Security, observability, configuration management\n- Database migrations, Docker, testing, CI/CD\n- AI coding tool operating rules\n\n### Modular Monolith\n- Module boundary rules by business capability\n- Transaction strategy using local ACID advantage\n- Data ownership within a shared database\n- Internal module interaction patterns\n- Performance and scalability guidance\n\n### Microservices\n- Service boundary and data ownership rules\n- Synchronous and asynchronous communication standards\n- Resilience patterns (timeouts, retries, circuit breakers, idempotency)\n- Distributed observability with tracing\n- Service-to-service security\n- Data consistency strategy\n\n## Technology Baseline\n\n- Spring Boot\n- Spring Security\n- Spring Boot Actuator\n- PostgreSQL\n- Flyway\n- Docker\n- Testcontainers\n- OpenAPI / Swagger\n- Hexagonal Architecture + DDD\n\n## License\n\nMIT\n",
  "bytes": 2408,
  "sha": "65a249ac50a29818b903ec0d8f97e8bce9560f2a12aaf0e3e78593bc613347c9",
  "repo_slug": "alexandercanon/spring-standards",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_alexandercanon_spring_standards_spring_s_4b19a287/readme"
}