General

415-frameworks-quarkus-mongodb - Claude MCP Skill

Use when you need MongoDB persistence in Quarkus — including Panache Mongo entities/repositories, document design, indexes, transactions where applicable, and error handling. This should trigger for requests such as Add MongoDB in Quarkus; Review Quarkus Mongo Panache design; Improve Mongo error handling in Quarkus services; Model MongoDB documents for a Quarkus service; Configure Quarkus MongoDB clients codecs or transactions. Part of Plinth Toolkit

SEO Guide: Enhance your AI agent with the 415-frameworks-quarkus-mongodb tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to use when you need mongodb persistence in quarkus — including panache mongo entities/repositories, do... Download and configure this skill to unlock new capabilities for your AI workflow.

🌟1 stars • 96 forks
📥0 downloads

Documentation

SKILL.md
# Quarkus — MongoDB

Apply Quarkus 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 Quarkus
- Review Quarkus Mongo Panache entities/repositories
- Improve duplicate key handling, retry policy, or optimistic locking in Quarkus Mongo
- Model MongoDB documents for a Quarkus service
- Configure Quarkus MongoDB clients codecs or transactions

## Workflow

1. **Read reference and assess project context**

Read `references/415-frameworks-quarkus-mongodb.md` and inspect persistence setup before proposing changes.

2. **Gather scope and decide target improvements**

Identify model/query consistency needs and define safe improvements.

3. **Apply framework-aligned changes**

Implement/refactor Panache Mongo mappings, repository access, and failure 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/415-frameworks-quarkus-mongodb.md](references/415-frameworks-quarkus-mongodb.md).

Signals

Avg rating⭐ 0.0
Reviews0
Favorites0

Information

Repository
jabrena/cursor-rules-java
Author
jabrena
Last Sync
11/2/2026
Repo Updated
11/1/2026
Created
5/8/2026

Reviews (0)

No reviews yet. Be the first to review this skill!

Related Skills

mongodb-mcp-v3-migration

Migrates external consumer code from the mongodb-mcp-server v1/v2 single-package API to the v3 scoped-package structure. In v3, mongodb-mcp-server is a binary-only package (npx / MCPB); library embedding uses @mongodb-js/mcp-cli, @mongodb-js/mcp-core, @mongodb-js/mcp-http-runners, @mongodb-js/mcp-tools-*, and the other @mongodb-js/mcp-* packages. Use when asked to migrate a project embedding or extending mongodb-mcp-server ("update my code to v3", "fix imports after the v3 release", "migrate my custom server/tools to the new packages"), or by external users following the v3 migration guide.

⭐ 1155

prowler-readme-table

Updates the "Prowler at a Glance" table in README.md with accurate provider statistics. Trigger: When updating README.md provider stats, checks count, services count, compliance frameworks, or categories.

⭐ 389

prowler-api

Prowler API patterns: RLS, RBAC, providers, Celery tasks. Trigger: When working in api/ on models/serializers/viewsets/filters/tasks involving tenant isolation (RLS), RBAC, or provider lifecycle.

⭐ 389

prowler-compliance

Creates, syncs, audits and manages Prowler compliance frameworks end-to-end. Covers the two supported JSON schemas (universal multi-provider and legacy per-provider), the SDK model tree (legacy attribute classes, universal ComplianceFramework, ConfigRequirements guardrails), output formatters (legacy per-framework + universal data-driven), API/UI consumption, upstream sync workflows, and cloud-auditor check-mapping reviews. Trigger: When working with compliance frameworks (CIS, CIS Controls, NIST, PCI-DSS, SOC2, GDPR, ISO27001, ENS, MITRE ATT&CK, CCC, C5, CSA CCM, DORA, KISA ISMS-P, ASD Essential Eight, DISA STIG, CISA SCuBA, SecNumCloud, FedRAMP, HIPAA, NIS2, Prowler ThreatScore), creating a universal multi-provider framework, adding ConfigRequirements guardrails, syncing with upstream catalogs, auditing check-to-requirement mappings, adding output formatters, or fixing compliance JSON bugs (duplicate IDs, empty Version, wrong Section, stale check refs).

⭐ 389

Related Guides