Helidon
Helidon covers both Helidon SE (reactive, lightweight) and Helidon MP (MicroProfile / Jakarta EE style) programming models. Skills should make the chosen model explicit in prompts and generated structure.
Framework overview
Section titled “Framework overview”AI Coding Skills Helidon work focuses on:
- REST/HTTP endpoints
- Configuration
- Service layering appropriate to SE or MP
- Health checks
- Tests that exercise HTTP behavior
Supported Java versions
Section titled “Supported Java versions”| Java | Notes |
|---|---|
| 21 | Preferred for new projects |
| 17 | Supported where Helidon version requires it |
Supported framework versions
Section titled “Supported framework versions”Target a current stable Helidon 4.x line unless a skill page pins a different version. Document SE vs MP clearly in skill output.
Programming model
Section titled “Programming model”Helidon SE
Section titled “Helidon SE”- Explicit server and routing setup
- Functional/handler-oriented endpoints
- Config loaded from Helidon Config APIs
Helidon MP
Section titled “Helidon MP”- CDI-based application model
- JAX-RS resource classes
- MicroProfile Config, Health, and related conventions
Common project structure
Section titled “Common project structure”src/├── main/│ ├── java/│ │ └── com/example/app/│ │ ├── Main.java│ │ └── service/│ └── resources/│ └── application.yaml└── test/ └── java/Exact layout differs between SE and MP; skills should document the variant they generate.
Relevant skills
Section titled “Relevant skills”| Skill | Status |
|---|---|
| Helidon Bootstrap | In Progress |
Available examples
Section titled “Available examples”Helidon SE ServiceReference Helidon SE HTTP service.
Platform availability
Section titled “Platform availability”| Platform | Bootstrap skill status |
|---|---|
| GitHub Copilot | Planned |
| Grok | In Progress |
| Claude Code | Planned |
Official documentation
Section titled “Official documentation”Compatibility notes
Section titled “Compatibility notes”- Do not mix SE and MP patterns in a single generated application unless the user explicitly requests a migration path.
- Prefer health and readiness endpoints that match Helidon conventions for the chosen model.
- Keep dependencies aligned with the Helidon BOM for the selected version.