Skip to content

Conversation

melix
Copy link
Contributor

@melix melix commented Sep 23, 2025

This is a first set of rules when developing Micronaut modules using Cline.

This is a first set of rules when developing Micronaut modules using Cline.

You SHOULD prefer modern Java idioms: records, pattern matching, sealed interfaces/classes, `var` for local variables.
You MUST NOT use fully qualified class names unless there is a conflict between 2 class names in different packages.
You MUST annotate the code with nullability annotations (`io.micronaut.core.annotation.Nullable`, `io.micronaut.core.annotation.NonNull`).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thought we wanted JSpecify now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We haven't made a decision yet. And since this will also apply to 4.x repositories, we should still prefer the Micronaut annotations for now.

- You SHOULD list assumptions and uncertainties that need clarification before completing a task.
- You SHOULD check project configuration/build files before proposing structural or dependency changes.

## Context7 Usage (Documentation and Examples)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tried with many different phrasings, and it never uses Context7 unless I add "use Context7" in my prompts. Let me know if you got it to follow the rules.

@melix melix merged commit c46bca6 into master Sep 23, 2025
5 checks passed
@melix melix deleted the cc/cline branch September 23, 2025 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants