515-frameworks-micronaut-mongodb
Use when you need MongoDB persistence in Micronaut — including @MongoRepository design, document modeling, indexes, query patterns, and error handling. This should trigger for requests such as Add MongoDB in Micronaut; Review Micronaut Data Mongo design; Improve error handling for Micronaut Mongo operations; Model MongoDB documents for a Micronaut service; Configure Micronaut MongoDB codecs indexes or transactions. Part of Plinth Toolkit
Works with
--- name: 515-frameworks-micronaut-mongodb description: Use when you need MongoDB persistence in Micronaut — including @MongoRepository design, document modeling, indexes, query patterns, and error handling. This should trigger for requests such as Add MongoDB in Micronaut; Review Micronaut Data Mongo design; Improve error handling for Micronaut Mongo operations; Model MongoDB documents for a Micronaut service; Configure Micronaut MongoDB codecs indexes or transactions. Part of Plinth Toolkit license: Apache-2.0 --- # Micronaut — MongoDB Apply Micronaut MongoDB guidance with concrete examples for design, implementation, and error handling. ## Constraints Compile before MongoDB refactors; verify after changes. - **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 ## When to use this skill - Add MongoDB in Micronaut - Review Micronaut Mongo entities/repositories - Improve duplicate key handling, retries, or optimistic locking in Micronaut Mongo - Model MongoDB documents for a Micronaut service - Configure Micronaut MongoDB codecs indexes or transactions ## Workflow 1. **Read reference and assess project context** Read `references/515-frameworks-micronaut-mongodb.md` and inspect persistence setup before proposing changes. 2. **Gather scope and decide target improvements** Identify model and consistency requirements and define safe improvements. 3. **Apply framework-aligned changes** Implement/refactor documents, repositories, indexes, and error handling. 4. **Run verification and report results** Execute build/tests and summarize what changed, what was verified, and follow-up actions. ## Reference For detailed guidance, examples, and constraints, see [references/515-frameworks-micronaut-mongodb.md](references/515-frameworks-micronaut-mongodb.md).
More Database skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-database-setup
prisma/skills
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
prisma-postgres
prisma/skills
Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db/create-pg/create-postgres, or integrating programmatic provisioning with service tokens or OAuth.
