Enterprise Java specialist for Spring Boot 3.x, microservices, and cloud-native development.
Works with
Covers Spring Boot 3.x architecture, WebFlux reactive endpoints, Spring Data JPA optimization, and Spring Security with OAuth2/JWT configuration
Enforces Java 21 LTS features, DDD/Clean Architecture principles, and comprehensive test coverage (85%+ target) with Maven/Gradle verification workflows
Includes domain modeling, service layer design, repository patterns, and REST endpoint implementa
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionjava-architectExecute the skills CLI command in your project's root directory to begin installation:
Fetches java-architect from jeffallan/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate java-architect. Access via /java-architect in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
4
total installs
4
this week
7.9K
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
7.9K
stars
Enterprise Java specialist focused on Spring Boot 3.x, microservices architecture, and cloud-native development using Java 21 LTS.
./mvnw verify -pl <module> to confirm query correctness. If integration tests fail: review Hibernate SQL logs, fix queries or mappings, re-run before proceeding../mvnw verify after security changes to confirm filter chain and JWT wiring. If tests fail: check SecurityFilterChain bean order and token validation config, then re-run../mvnw verify (Maven) or ./gradlew check (Gradle) to confirm all tests pass and coverage reaches 85%+ before closing. If coverage is below threshold: identify untested branches via JaCoCo report (target/site/jacoco/index.html), add missing test cases, re-run.Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Spring Boot | references/spring-boot-setup.md |
Project setup, configuration, starters |
| Reactive | references/reactive-webflux.md |
WebFlux, Project Reactor, R2DBC |
| Data Access | references/jpa-optimization.md |
JPA, Hibernate, query tuning |
| Security | references/spring-security.md |
OAuth2, JWT, method security |
| Testing | references/testing-patterns.md |
JUnit 5, TestContainers, Mockito |
When implementing Java features, provide:
@RestController
@RequestMapping("/api/v1/orders")
@RequiredArgsConstructor
public class OrderController {
private final OrderService orderService;
@GetMapping("/{id}")
public Mono<ResponseEntity<OrderDto>> getOrder(@PathVariable UUID id) {
return orderService.findById(id)
.map(ResponseEntity::ok)
.defaultIfEmpty(ResponseEntity.notFound().build());
}
@PostMapping
@ResponseStatus(HttpStatus.CREATED)
public Mono<OrderDto> createOrder(@Valid @RequestBody CreateOrderRequest request) {
return orderService.create(request);
}
}
public interface OrderRepository extends JpaRepository<Order, UUID> {
// Avoid N+1: fetch association in one query
@Query("SELECT o FROM Order o JOIN FETCH o.items WHERE o.customerId = :customerId")
List<Order> findByCustomerIdWithItems(@Param("customerId") UUID customerId);
// Projection to limit fetched columns
@Query("SELECT new com.example.dto.OrderSummary(o.id, o.status, o.total) FROM Order o WHERE o.status = :status")
Page<OrderSummary> findSummariesByStatus(@Param("status") OrderStatus status, Pageable pageable);
}
@Configuration
@EnableMethodSecurity
public class SecurityConfig {
@Bean
public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
return http
.csrf(AbstractHttpConfigurer::disable)
.sessionManagement(s -> s.sessionCreationPolicy(STATELESS))
.authorizeHttpRequests(auth -> auth
.requestMatchers("/actuator/health").permitAll()
.anyRequest().authenticated())
.oauth2ResourceServer(oauth2 -> oauth2.jwt(Customizer.withDefaults()))
.build();
}
}
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
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jeffallan/claude-skills
jeffallan/claude-skills
jeffallan/claude-skills
jeffallan/claude-skills
jeffallan/claude-skills
jeffallan/claude-skills
java-architect has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend java-architect for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: java-architect is focused, and the summary matches what you get after install.
java-architect reduced setup friction for our internal harness; good balance of opinion and flexibility.
java-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
java-architect has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for java-architect matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend java-architect for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: java-architect is focused, and the summary matches what you get after install.
Useful defaults in java-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 61