Claude-skill-registry java-standards
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/java-standards" ~/.claude/skills/majiayu000-claude-skill-registry-java-standards && rm -rf "$T"
manifest:
skills/data/java-standards/SKILL.mdsource content
Java Standards
Java service standards for Bitso projects.
When to use this skill
- Creating new Java services or modules
- Understanding project organization patterns
- Reviewing Java code for standards compliance
- Configuring MapStruct for object mapping
- Verifying builds after code changes
Skill Contents
Sections
- When to use this skill (L24-L31)
- Tech Stack (L54-L67)
- Project Organization (L68-L83)
- Build Verification (L84-L97)
- References (L98-L105)
- Related Rules (L106-L111)
- Related Skills (L112-L118)
Available Resources
📚 references/ - Detailed documentation
Tech Stack
| Component | Version | Notes |
|---|---|---|
| Java | 21 (LTS) | Current LTS version |
| Gradle | 9.2.1 | Recommended for all projects |
| Spring Boot | 3.5.9 | Latest (min 3.5.9) - preparing for Spring Boot 4 |
| Database Access | jOOQ | For accessing PostgreSQL |
| Databases | PostgreSQL, Redis | Primary data stores |
| Inter-service Communication | gRPC | Standard protocol |
| Object Mapping | MapStruct | For DTO/domain mapping |
For Spring Boot upgrades, use
/upgrade-to-recommended-versions.
Project Organization
Projects should be organized with domain-based modules:
root-project/ ├── build.gradle ├── settings.gradle ├── docs/ # Documentation ├── bitso-libs/ # Library modules │ ├── <subdomain>/ # Domain logic │ └── <subdomain-proto>/ # Protobuf definitions └── bitso-services/ # Service modules └── <domain>/ # Spring Boot application
Build Verification
After updating Java or Groovy code, verify changes:
# Run tests to verify changes ./gradlew test 2>&1 | grep -E "FAILED|Error" || echo "All tests passed" # Or run full build with tests ./gradlew build 2>&1 | grep -E "FAILED|Error" || echo "Build successful"
If problems are found, fix them before committing.
References
| Reference | Description |
|---|---|
| references/services.md | Tech stack, project structure, dependency management, MapStruct |
| references/code-review.md | Java 21 standards, coding style, var keyword usage |
| references/build-verification.md | Build commands and verification practices |
Related Rules
- java-services-standards - Full-service standards
- java-code-review-standards - Code review guidelines
- java-run-build-after-changes - Build verification
Related Skills
| Skill | Purpose |
|---|---|
| gradle-standards | Gradle configuration |
| grpc-services-rfc-33 | gRPC service implementation |
| database-integration | jOOQ and Flyway |