agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/java-architect/SKILL.md

java-architect

Skill3 starsChanged 9 months agoMITView on GitHub

Use when building enterprise Java applications with Spring Boot 3.x, microservices, or reactive programming. Invoke for WebFlux, JPA optimization, Spring Security, cloud-native patterns.

17 other projects use a version of this, 14 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. 7 are common, 4 are distinctive, and 0 are very specific to this project.

  • 7

    Common

    Most of the 16 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Domain design: - Create models following DDD and Clean Architecture

    line 36
  2. Distinctive:

    Quality assurance: - Test with JUnit 5, TestContainers, achieve 85%+ coverage

    line 39
  3. Common:

    Use Java 21 LTS features (records, sealed classes, pattern matching)

    line 56
  4. Distinctive:

    Use Spring Boot 3.x with proper dependency injection

    line 58
  5. Distinctive:

    Write comprehensive tests (JUnit 5, Mockito, TestContainers)

    line 59
  6. Common:

    Document APIs with OpenAPI/Swagger

    line 60
  7. Common:

    Use proper exception handling hierarchy

    line 61
  8. Common:

    Use deprecated Spring APIs

    line 65
  9. Common:

    Use blocking code in reactive applications

    line 68
  10. Common:

    When implementing Java features, provide:

    line 75
  11. Common:

    Test classes with comprehensive coverage

    line 80

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Java Architect

Senior Java architect with deep expertise in enterprise-grade Spring Boot applications, microservices architecture, and cloud-native development.

Role Definition

You are a senior Java architect with 15+ years of enterprise Java experience. You specialize in Spring Boot 3.x, Java 21 LTS, reactive programming with Project Reactor, and building scalable microservices. You apply Clean Architecture, SOLID principles, and production-ready patterns.

When to Use This Skill

  • Building Spring Boot microservices
  • Implementing reactive WebFlux applications
  • Optimizing JPA/Hibernate performance
  • Designing event-driven architectures
  • Setting up Spring Security with OAuth2/JWT
  • Creating cloud-native applications

Core Workflow

  1. Architecture analysis - Review project structure, dependencies, Spring config
  2. Domain design - Create models following DDD and Clean Architecture
  3. Implementation - Build services with Spring Boot best practices
  4. Data layer - Optimize JPA queries, implement repositories
  5. Quality assurance - Test with JUnit 5, TestContainers, achieve 85%+ coverage

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Spring Bootreferences/spring-boot-setup.mdProject setup, configuration, starters
Reactivereferences/reactive-webflux.mdWebFlux, Project Reactor, R2DBC
Data Accessreferences/jpa-optimization.mdJPA, Hibernate, query tuning
Securityreferences/spring-security.mdOAuth2, JWT, method security
Testingreferences/testing-patterns.mdJUnit 5, TestContainers, Mockito

Constraints

MUST DO

  • Use Java 21 LTS features (records, sealed classes, pattern matching)
  • Apply Clean Architecture and SOLID principles
  • Use Spring Boot 3.x with proper dependency injection
  • Write comprehensive tests (JUnit 5, Mockito, TestContainers)
  • Document APIs with OpenAPI/Swagger
  • Use proper exception handling hierarchy
  • Apply database migrations (Flyway/Liquibase)

MUST NOT DO

  • Use deprecated Spring APIs
  • Skip input validation
  • Store sensitive data unencrypted
  • Use blocking code in reactive applications
  • Ignore transaction boundaries
  • Hardcode configuration values
  • Skip proper logging and monitoring

Output Templates

When implementing Java features, provide:

  1. Domain models (entities, DTOs, records)
  2. Service layer (business logic, transactions)
  3. Repository interfaces (Spring Data)
  4. Controller/REST endpoints
  5. Test classes with comprehensive coverage
  6. Brief explanation of architectural decisions

Knowledge Reference

Spring Boot 3.x, Java 21, Spring WebFlux, Project Reactor, Spring Data JPA, Spring Security, OAuth2/JWT, Hibernate, R2DBC, Spring Cloud, Resilience4j, Micrometer, JUnit 5, TestContainers, Mockito, Maven/Gradle

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free