[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7830YFD3RCWTT4R3DSB4X86":3,"skill-same:01M7830YFD3RCWTT4R3DSB4X86":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7830YFD3RCWTT4R3DSB4X86","110-java-maven-best-practices",null,"Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should trigger for requests such as Review pom.xml to improve it; Apply Maven best practices to pom.xml; Improve Maven POM configuration. Part of cursor-rules-java project","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_jabrena_cursor-rules-java_110-java-maven-best-practices\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: 110-java-maven-best-practices\ndescription: Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should trigger for requests such as Review pom.xml to improve it; Apply Maven best practices to pom.xml; Improve Maven POM configuration. Part of cursor-rules-java project\nlicense: Apache-2.0\nmetadata:\n  author: Juan Antonio Breña Moral\n  version: 0.15.0\n---\n# Maven Best Practices\n\nImprove Maven POM configuration using industry-standard best practices.\n\n**What is covered in this Skill?**\n\n- Dependency management via `\u003CdependencyManagement>` and BOMs\n- Standard directory layout (`src\u002Fmain\u002Fjava`, `src\u002Ftest\u002Fjava`)\n- Centralized plugin management\n- Build profiles for environment-specific settings\n- Readable POM structure with version properties\n- Explicit repository declaration\n- Version centralization\n- Multi-module project structure with proper inheritance\n- Cross-module version consistency\n- Multi-module scope: After reading the root `pom.xml`, check for a `\u003Cmodules>` section. If present, read **every** child module's `pom.xml` before making any recommendations.\n- Check each child for hardcoded versions that duplicate parent `\u003CdependencyManagement>`, redundant `\u003CpluginManagement>` blocks, properties that should be centralized, and version drift across sibling modules.\n\n## Constraints\n\nBefore applying Maven best practices recommendations, ensure the project is in a valid state by running Maven validation. This helps identify any existing configuration issues that need to be resolved first. For multi-module projects, scope analysis must cover every child module POM — not just the root.\n\n- **MANDATORY**: Run `.\u002Fmvnw validate` or `mvn validate` before applying any Maven best practices recommendations\n- **VERIFY**: Ensure all validation errors are resolved before proceeding with POM modifications\n- **SAFETY**: If validation fails, do not continue and ask the user to fix the issues before continuing\n- **MULTI-MODULE DISCOVERY**: After reading the root `pom.xml`, check whether it contains a `\u003Cmodules>` section. If it does, read every child module's `pom.xml` before making any recommendations — analysis scope is the full module tree, not only the root\n- **CROSS-MODULE SCOPE**: When child modules exist, check each one for: hardcoded dependency versions that duplicate `\u003CdependencyManagement>` in the parent, plugin configurations that duplicate `\u003CpluginManagement>`, properties that should be centralized in the parent, and version drift (same artifact declared at different versions across sibling modules)\n- **BEFORE APPLYING**: Read the reference for detailed examples, good\u002Fbad patterns, and constraints\n\n## When to use this skill\n\n- Review pom.xml to improve it\n- Apply Maven best practices to pom.xml\n- Improve Maven POM configuration\n\n## Workflow\n\n1. **Validate project before recommendations**\n\nRun `.\u002Fmvnw validate` or `mvn validate` and stop if validation fails.\n\n2. **Read reference and analyze root POM**\n\nRead `references\u002F110-java-maven-best-practices.md`, then inspect root `pom.xml` structure, dependency management, plugin management, properties, and profiles.\n\n3. **Expand to full module tree when present**\n\nIf root has a `\u003Cmodules>` section, read every child `pom.xml` and evaluate cross-module duplication, centralization opportunities, and version drift.\n\n4. **Provide prioritized best-practice recommendations**\n\nPropose concrete, safe improvements aligned with Maven best practices and full-module findings.\n\n## Reference\n\nFor detailed guidance, examples, and constraints, see [references\u002F110-java-maven-best-practices.md](references\u002F110-java-maven-best-practices.md).\n","# Maven Best Practices\n\nImprove Maven POM configuration using industry-standard best practices.\n\n**What is covered in this Skill?**\n\n- Dependency management via `\u003CdependencyManagement>` and BOMs\n- Standard directory layout (`src\u002Fmain\u002Fjava`, `src\u002Ftest\u002Fjava`)\n- Centralized plugin management\n- Build profiles for environment-specific settings\n- Readable POM structure with version properties\n- Explicit repository declaration\n- Version centralization\n- Multi-module project structure with proper inheritance\n- Cross-module version consistency\n- Multi-module scope: After reading the root `pom.xml`, check for a `\u003Cmodules>` section. If present, read **every** child module's `pom.xml` before making any recommendations.\n- Check each child for hardcoded versions that duplicate parent `\u003CdependencyManagement>`, redundant `\u003CpluginManagement>` blocks, properties that should be centralized, and version drift across sibling modules.\n\n## Constraints\n\nBefore applying Maven best practices recommendations, ensure the project is in a valid state by running Maven validation. This helps identify any existing configuration issues that need to be resolved first. For multi-module projects, scope analysis must cover every child module POM — not just the root.\n\n- **MANDATORY**: Run `.\u002Fmvnw validate` or `mvn validate` before applying any Maven best practices recommendations\n- **VERIFY**: Ensure all validation errors are resolved before proceeding with POM modifications\n- **SAFETY**: If validation fails, do not continue and ask the user to fix the issues before continuing\n- **MULTI-MODULE DISCOVERY**: After reading the root `pom.xml`, check whether it contains a `\u003Cmodules>` section. If it does, read every child module's `pom.xml` before making any recommendations — analysis scope is the full module tree, not only the root\n- **CROSS-MODULE SCOPE**: When child modules exist, check each one for: hardcoded dependency versions that duplicate `\u003CdependencyManagement>` in the parent, plugin configurations that duplicate `\u003CpluginManagement>`, properties that should be centralized in the parent, and version drift (same artifact declared at different versions across sibling modules)\n- **BEFORE APPLYING**: Read the reference for detailed examples, good\u002Fbad patterns, and constraints\n\n## When to use this skill\n\n- Review pom.xml to improve it\n- Apply Maven best practices to pom.xml\n- Improve Maven POM configuration\n\n## Workflow\n\n1. **Validate project before recommendations**\n\nRun `.\u002Fmvnw validate` or `mvn validate` and stop if validation fails.\n\n2. **Read reference and analyze root POM**\n\nRead `references\u002F110-java-maven-best-practices.md`, then inspect root `pom.xml` structure, dependency management, plugin management, properties, and profiles.\n\n3. **Expand to full module tree when present**\n\nIf root has a `\u003Cmodules>` section, read every child `pom.xml` and evaluate cross-module duplication, centralization opportunities, and version drift.\n\n4. **Provide prioritized best-practice recommendations**\n\nPropose concrete, safe improvements aligned with Maven best practices and full-module findings.\n\n## Reference\n\nFor detailed guidance, examples, and constraints, see [references\u002F110-java-maven-best-practices.md](references\u002F110-java-maven-best-practices.md).\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Juan Antonio Breña Moral","0.15.0","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fskills_sh\u002Fs\u002Fskills-sh_jabrena_cursor-rules-java_110-java-maven-best-practices",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill 110-java-maven-best-practices",{"tool":42,"command":43},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill 110-java-maven-best-practices",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill 110-java-maven-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_jabrena_cursor-rules-java_110-java-maven-best-practices\u002FSKILL.md",true,[],[51,59,66,73,80,87],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]