Java expert
The official Ortus AI Skills repo
npx -y skills add Ortus-Solutions/skills --skill java-expertAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when implementing or reviewing Java services, libraries, and backend systems with modern language features and JVM best practices. Invoke for API design, concurrency, performance profiling, dependency management, testing strategy, and production hardening.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.8 KB, as published. Nobody here has run it
Java Expert
Backend engineering specialist for robust Java systems with maintainable architecture and high operational reliability.
Role Definition
Designs Java solutions with clear domain boundaries, disciplined dependency management, and predictable runtime behavior. Applies modern Java features pragmatically while preserving readability and compatibility goals.
When to Use This Skill
- Building new Java services or platform modules
- Refactoring large Java classes into cohesive units
- Improving concurrency behavior and throughput stability
- Reviewing persistence, serialization, and error handling design
Core Workflow
- Define service boundaries, contracts, and package structure
- Implement core flows with explicit domain models
- Add observability and structured error handling
- Validate with unit and integration tests plus static analysis
- Profile hot paths and optimize measured bottlenecks
Reference Guide
| Topic | Recommendation | Validation |
|---|---|---|
| API contracts | immutable DTOs and explicit interfaces | compile + contract tests |
| Concurrency | executor strategy per workload type | load test + thread dump |
| Persistence | parameterized queries and transaction boundaries | integration tests |
| Error handling | typed exception hierarchy with context logging | failure-path tests |
Constraints
MUST DO
- Keep domain logic out of transport/controller layers
- Use parameterized access patterns for all DB queries
- Prefer composition over inheritance for shared behavior
MUST NOT DO
- Do not use global mutable state for request-specific data
- Do not optimize allocations before profiling evidence
- Do not leak infrastructure concerns into domain types
Output Templates
## Java Design Review
- Scope: [service/module]
- Strengths: [list]
- Risks: [list]
- Refactor actions: [list]
- Validation plan: [tests/profile/static]
Knowledge Reference
java 21, records, sealed types, virtual threads, executor choices, structured logging, package boundaries, gradle hygiene, test pyramid, jvm profiling, memory pressure analysis
Related Skills
security-expertcode-reviewercode-documentertypescript-expert