Provides expert Java architecture expertise specializing in Java 21, Spring Boot 3, and Jakarta EE ecosystem. Designs enterprise-grade applications with modern Java features (virtual threads, pattern matching), microservices architecture, and comprehensive enterprise integration patterns for scalable, maintainable systems.
Works with
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 404kidwiz/claude-supercode-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
0
total installs
0
this week
75
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
75
stars
Provides expert Java architecture expertise specializing in Java 21, Spring Boot 3, and Jakarta EE ecosystem. Designs enterprise-grade applications with modern Java features (virtual threads, pattern matching), microservices architecture, and comprehensive enterprise integration patterns for scalable, maintainable systems.
Application Requirements
│
├─ Need reactive, non-blocking I/O?
│ └─ Spring WebFlux ✓
│ - Netty/Reactor runtime
│ - Backpressure support
│ - High concurrency (100K+ connections)
│
├─ Traditional servlet-based web app?
│ └─ Spring MVC ✓
│ - Tomcat/Jetty runtime
│ - Familiar blocking model
│ - Easier debugging
│
├─ Microservices with service discovery?
│ └─ Spring Cloud ✓
│ - Eureka/Consul for discovery
│ - Config server
│ - API gateway (Spring Cloud Gateway)
│
├─ Batch processing?
│ └─ Spring Batch ✓
│ - Chunk-oriented processing
│ - Job scheduling
│ - Transaction management
│
└─ Need minimal footprint?
└─ Spring Boot with GraalVM Native Image ✓
- AOT compilation
- Fast startup (<100ms)
- Low memory (<50MB)
| Factor | Use JPA/Hibernate | Use JDBC (Spring JdbcTemplate) |
|---|---|---|
| Complexity | Complex domain models with relationships | Simple queries, reporting |
| Performance | OLTP with caching (2nd-level cache) | OLAP, bulk operations |
| Type safety | Criteria API, type-safe queries | Plain SQL with RowMapper |
| Maintenance | Schema evolution with migrations | Direct SQL control |
| Learning curve | Steeper (lazy loading, cascades) | Simpler, explicit |
| N+1 queries | Risk (needs @EntityGraph, fetch joins) | Explicit control |
Example decision: E-commerce order system with relationships → JPA (Order → OrderItems → Products)
Example decision: Analytics dashboard with aggregations → JDBC (complex SQL, performance-critical)
Concurrency Requirements
│
├─ High thread count (>1000 threads)?
│ └─ Virtual Threads ✓
│ - Millions of threads possible
│ - No thread pool tuning
│ - Blocking code becomes cheap
│
├─ I/O-bound operations (DB, HTTP)?
│ └─ Virtual Threads ✓
│ - JDBC calls don't block platform threads
│ - HTTP client calls scale better
│
├─ CPU-bound operations?
│ └─ Platform Threads (ForkJoinPool) ✓
│ - Virtual threads don't help
│ - Use parallel streams
│
└─ Need compatibility with existing code?
└─ Virtual Threads ✓
- Drop-in replacement for Thread
- No code changes required
| Observation | Why Escalate | Example |
|---|---|---|
| JPA N+1 queries causing 1000+ DB calls | Complex lazy loading issue | "Single page load triggers 500 SELECT queries" |
| Circular dependency in Spring beans | Architectural design problem | "BeanCurrentlyInCreationException during startup" |
| Memory leak despite GC tuning | Complex object retention | "Heap grows to max despite Full GC, heap dump shows mysterious retention" |
| Distributed transaction spanning multiple microservices | SAGA pattern or compensating transactions | "Need ACID across Order, Payment, Inventory services" |
| Reactive stream backpressure overload | Complex reactive pipeline | "Flux overproducing, downstream can't keep up" |
Scenario: Implement event sourcing for order service
Step 1: Configure Spring Kafka
// Configuration/KafkaConfig.java
@Configuration
@EnableKafka
public class KafkaConfig {
@Value("${spring.kafka.bootstrap-servers}")
private String bootstrapServers;
@Bean
public ProducerFactory<String, DomainEvent> producerFactory() {
Map<String, Object> config = Map.of(
ProducerConfig.BOOTSTRAP_SERVERS_CONFIG, bootstrapServers,
ProducerConfig.KEY_SERIALIZER_CLASS_CONFIG, StringSerializer.class,
ProducerConfig.VALUE_SERIALIZER_CLASS_CONFIG, JsonSerializer.class,
ProducerConfig.ACKS_CONFIG, "all",
ProducerConfig.RETRIES_CONFIG, 3,
ProducerConfig.ENABLE_IDEMPOTENCE_CONFIG, true
);
return new DefaultKafkaProducerFactory<>(config);
}
@Bean
public KafkaTemplate<String, DomainEvent> kafkaTemplate() {
return new KafkaTemplate<>(producerFactory());
}
@Bean
public ConsumerFactory<String, DomainEvent> consumerFactory() {
Map<String, Object> config = Map.of(
ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG, bootstrapServers,
ConsumerConfig.KEY_DESERIALIZER_CLASS_CONFIG, StringDeserializer.class,
ConsumerConfig.VALUE_DESERIALIZER_CLASS_CONFIG, JsonDeserializer.class,
ConsumerConfig.GROUP_ID_CONFIG, "order-service",
ConsumerConfig.AUTO_OFFSET_RESET_CONFIG, "earliest",
ConsumerConfig.ENABLE_AUTO_COMMIT_CONFIG, false,
JsonDeserializer.TRUSTED_PACKAGES, "com.example.order.domain.events"
);
return new DefaultKafkaConsumerFactory<>(config);
}
}
Step 2: Define domain events
// Domain/Events/DomainEvent.java
public sealed interface DomainEvent permits
OrderCreated, OrderItemAdded, OrderProcessingStarted, OrderCompleted, OrderCancelled {
UUID aggregateId();
LocalDateTime occurredAt();
long version();
}
public record OrderCreated(
UUID aggregateId,
UUID customerId,
LocalDateTime occurredAt,
long version
) implements DomainEvent {}
public record OrderItemAdded(
UUID aggregateId,
UUID productId,
int quantity,
BigDecimal unitPrice,
LocalDateTime occurredAt,
long version
) implements DomainEvent {}
public record OrderCompleted(
UUID aggregateId,
BigDecimal totalAmount,
LocalDateTime occurredAt,
long version
) implements DomainEvent {}
Step 3: Event publisher
// Infrastructure/EventPublisher.java
@Component
public class DomainEventPublisher {
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.
404kidwiz/claude-supercode-skills
404kidwiz/claude-supercode-skills
404kidwiz/claude-supercode-skills
404kidwiz/claude-supercode-skills
404kidwiz/claude-supercode-skills
github/awesome-copilot
Solid pick for teams standardizing on skills: java-architect is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: java-architect is focused, and the summary matches what you get after install.
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.
We added java-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in java-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in java-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
java-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
java-architect is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for java-architect matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 70