spring-standards vs. onboard

What It Does When you work on a Spring Boot project with Claude Code, this plugin enforces: Hexagonal architecture with clear domain/application/infrastructure separation Feature-oriented package structure instead of framework-driven sprawl Explicit layer rules — domain never depends on Spring, JPA entities stay in infrastructure, controllers delegate to use cases API design standards — OpenAPI, consistent error contracts, validation at all levels Security baseline — deny-by-default, least privilege, protected actuators Testing strategy — unit, integration, contract, and non-functional tests with Testcontainers Observability — structured logging, trace IDs, metrics, health endpoints Database discipline — Flyway migrations, no Hibernate DDL in production The skill automatically detects whether your project is a modular monolith or microservices system and loads the appropriate guide.

End-to-end Claude tooling generator for existing codebases. Performs deep codebase analysis (languages, frameworks, conventions, complexity), walks you through an interactive wizard, then generates a complete suite of Claude artifacts — CLAUDE.md files, path-scoped rules, project-specific skills and agents, hook configuration, PR templates, and commit conventions. Unlike recommendation-only tools, onboard produces actual files tailored to your project's detected patterns and enforced configs. Includes drift detection via /onboard:evolve to keep tooling aligned as your codebase changes. Also serves as the generation engine for the companion forge plugin (new projects) via headless invocation.