How do I install the 512 Frameworks Micronaut Data skill?

Run npx skillmds add majiayu000/512-frameworks-micronaut-data in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 512 Frameworks Micronaut Data safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 512 Frameworks Micronaut Data?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 512 Frameworks Micronaut Data free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 512 Frameworks Micronaut Data?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

512 Frameworks Micronaut Data by majiayu000

Name: 512 Frameworks Micronaut Data
Rating: 4.2 (5 reviews)
Author: majiayu000

512 Frameworks Micronaut Data

Use when you need data access with Micronaut Data — @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers. For raw java.sql access without generated repositories, use @511-frameworks-micronaut-jdbc. This should trigger for requests such as Review or implement Micronaut Data repositories and entities; Add transactions, pagination, or projections in Micronaut persistence layer. Part of cursor-rules-java project

majiayu000 58ba63f 2 files · 3.9 KB Updated Sep 9, 2026 567 repo stars

File contents

Micronaut Data Guidelines

Apply Micronaut Data patterns for relational repositories and safe SQL.

What is covered in this Skill?

@MappedEntity, @Id, @GeneratedValue, @MappedProperty for column mapping
@Repository interfaces extending CrudRepository / PageableRepository
Derived finder methods and @Query with named parameters
@Transactional on @Singleton services (readOnly where appropriate)
Page and Pageable for list endpoints
DTO/interface projections for read-heavy queries
@Version for optimistic locking
Integration tests: @MicronautTest + TestPropertyProvider + Testcontainers

Scope: Apply recommendations based on the reference rules and good/bad code examples.

Constraints

Compile before persistence changes; verify the full build after.

MANDATORY: Run ./mvnw compile or mvn compile before applying any change
SAFETY: If compilation fails, stop immediately
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
BEFORE APPLYING: Read the reference for detailed rules and examples
EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off

When to use this skill

Review or implement Micronaut Data repositories and entities
Add transactions, pagination, or projections in Micronaut persistence layer

Workflow

Read reference and assess project context

Read references/512-frameworks-micronaut-data.md and inspect the current project setup before proposing changes.

Gather scope and decide target improvements

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

Apply framework-aligned changes

Implement or refactor configuration/code following the reference patterns and project conventions.

Run verification and report results

Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.

Reference

For detailed guidance, examples, and constraints, see references/512-frameworks-micronaut-data.md.

---name: 512-frameworks-micronaut-datadescription: Use when you need data access with Micronaut Data — @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers. For raw java.sql access without generated repositories, use @511-frameworks-micronaut-jdbc. This should trigger for requests such as Review or implement Micronaut Data repositories and entities; Add transactions, pagination, or projections in Micronaut persistence layer. Part of cursor-rules-java projectlicense: Apache-2.0---# Micronaut Data Guidelines Apply Micronaut Data patterns for relational repositories and safe SQL. **What is covered in this Skill?** - @MappedEntity, @Id, @GeneratedValue, @MappedProperty for column mapping - @Repository interfaces extending CrudRepository / PageableRepository - Derived finder methods and @Query with named parameters - @Transactional on @Singleton services (readOnly where appropriate) - Page and Pageable for list endpoints - DTO/interface projections for read-heavy queries - @Version for optimistic locking - Integration tests: @MicronautTest + TestPropertyProvider + Testcontainers **Scope:** Apply recommendations based on the reference rules and good/bad code examples. ## Constraints Compile before persistence changes; verify the full build after. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed rules and examples - **EDGE CASE**: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands - **EDGE CASE**: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance - **EDGE CASE**: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off ## When to use this skill - Review or implement Micronaut Data repositories and entities - Add transactions, pagination, or projections in Micronaut persistence layer ## Workflow 1. **Read reference and assess project context** Read `references/512-frameworks-micronaut-data.md` and inspect the current project setup before proposing changes. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply framework-aligned changes** Implement or refactor configuration/code following the reference patterns and project conventions. 4. **Run verification and report results** Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions. ## Reference For detailed guidance, examples, and constraints, see [references/512-frameworks-micronaut-data.md](references/512-frameworks-micronaut-data.md).

Frequently asked questions