celesto
Secure and persistent computer for AI agents
Claude Code template for Spring Boot and other staff (included in the tags)
Developer toolsGitHub @piominSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗A Claude Code plugin with production-ready skills and agents for building Spring Boot 4.x / Java 21+ applications. Install the plugin and start generating your app — the skills and agents guide Claude to follow best practices for REST APIs with Problem Details errors, JPA, Flyway database migrations, security, testing, cloud-native deployment, and Kubernetes.
Install from Anthropic marketplace
claude plugin install spring-boot-template@piomin
Or install directly from repository
claude plugin marketplace add piomin/claude-ai-spring-boot
claude plugin install spring-boot-template@piomin
Then run Claude Code and type:
/plugin
To test locally during development:
claude --plugin-dir /path/to/claude-ai-spring-boot
The skills in skills/ use the open SKILL.md format (frontmatter with name and description, optional references/ folder), so OpenAI Codex can load them without changes. The repo is also a Codex plugin (.codex-plugin/plugin.json) with a marketplace file (.agents/plugins/marketplace.json).
As a plugin (skills only, no agents):
codex plugin marketplace add piomin/claude-ai-spring-boot
Then restart Codex, open the Plugins Directory, choose the piomin marketplace and install spring-boot-template. Update later with codex plugin marketplace upgrade piomin.
Or as plain skills. Codex discovers skills in .agents/skills (per repository) and $HOME/.agents/skills (per user):
git clone https://github.com/piomin/claude-ai-spring-boot.git
# for all your projects
mkdir -p ~/.agents/skills
cp -r claude-ai-spring-boot/skills/* ~/.agents/skills/
# or for a single project
mkdir -p my-project/.agents/skills
cp -r claude-ai-spring-boot/skills/* my-project/.agents/skills/
Codex follows symlinks, so you can ln -s each skill folder instead of copying to get updates with git pull. Restart Codex if the skills do not show up, then run /skills or type $ to pick one, or just describe the task and Codex selects a matching skill.
The agents/ folder uses the Claude Code subagent format and is Claude Code only. Skills mention the code-reviewer and security-engineer agents as hand-offs; in Codex, ignore those references and apply the skill directly.
agents/)Specialized agents that Claude Code can invoke for specific tasks:
| Agent | Purpose |
|---|---|
spring-boot-engineer | Build Spring Boot 4.x apps with layered architecture and Problem Details errors; adds the OpenAPI contract rules when the API is built for a UI |
code-reviewer | Read-only review of a diff or branch: fixes the scope, loads the conventions and code-quality skills, reports cited findings by severity |
kubernetes-specialist | K8s deployments, probes, ConfigMap/Secret, Prometheus, Skaffold |
devops-engineer | CI/CD pipelines, Paketo Buildpacks, Skaffold |
docker-expert | Multi-stage Dockerfiles, Paketo Buildpacks, image optimization |
security-engineer | Spring Security, OWASP, input validation, SSL Bundles |
skills/)Reusable knowledge that Claude loads contextually:
| Skill | What it teaches |
|---|---|
conventions | Mandatory project rules: No Lombok, constructor injection, RestClient, testing standards, conditional Flyway for relational databases, Problem Details, conditional OpenAPI contract rules for APIs built for a UI |
spring-boot | Core Spring Boot development with 7 reference guides (web incl. Problem Details and paging, OpenAPI with springdoc 3, data incl. Flyway migrations, security, cloud, Spring AI 2.x, testing) |
code-quality | Review checklist loaded on demand from 6 references (correctness, security, performance, Spring signals, REST semantics, code smells); points to conventions and other skills for project rules instead of repeating them |
design-patterns | Classic patterns (Factory, Builder, Strategy) + enterprise (Saga, Outbox, CQRS) |
testing-patterns | JUnit 5, Mockito, MockMvc, RestTestClient, Testcontainers with @ServiceConnection, relation and status-endpoint integration tests, Podman |
java-modern | Java 21+ features: records, sealed classes, pattern matching, virtual threads |
jpa-patterns | JPA/Hibernate pitfalls (N+1, lazy loading), Hibernate 6/7, optimistic locking across HTTP requests, relation writes with OSIV off, schema drift |
logging-patterns | Structured JSON logging, SLF4J, MDC, AI-friendly formats |
The plugin enforces these rules via the conventions skill:
LoggerFactory.getLogger()@Autowired on fields@AutoConfigureRestTestClient for integration tests@ServiceConnection (not @DynamicPropertySource)javax.persistence)PagedModel; optimistic locking with @Version and 409ddl-auto: validate) when the API persists to a Flyway-supported relational database; skipped for APIs without persistence, NoSQL-only APIs, or projects already using Liquibasepl.piomin.services group IDThe cloud.md reference covers:
This is the beginning of the README. Read the rest at the original. Read the full README ↗