Ask GitHub Copilot to build you a Helidon application and it has to guess. Helidon SE or MP? Helidon 3 APIs or Helidon 4? HttpService or Jakarta REST? Explicit composition or CDI? Without framework-specific context it produces code that looks correct, quietly mixes two programming models, and doesn't compile.

That's not a model problem. It's a context problem, and it's fixable.

In this session we'll build a Helidon 4 application with Copilot from an empty directory, a small customer service with routing, configuration, health checks and tests. Along the way, the API changes that trip Copilot up most and how to write a skill for your own framework.

You'll leave able to install the skill, bootstrap a Helidon 4 project with it and write one for the framework your team actually uses.

Suren Konathala