guicedee-creator

Scaffold GuicedEE-compliant Maven modules with Maven 4 and JDK 25+ baselines.

5|Updated Jul 6, 2025
One-click install
npx skills add https://github.com/GuicedEE/ai-rules --skill guicedee-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guicedee-creator
Source: https://github.com/GuicedEE/ai-rules/tree/main/skills/.system/guicedee-creator
Command: npx skills add https://github.com/GuicedEE/ai-rules --skill guicedee-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

GuicedEE-ready Maven module scaffolding that enforces Maven 4, Java 25+, BOM import, and JPMS module boundaries, so teams can start compliant modules with confidence.

Core Features & Use Cases

  • Generate a GuicedEE-compliant Maven module skeleton including main and test sources and a proper module-info.java.
  • Enforce baseline constraints: Maven wrapper pinned to Maven 4, Java release/source/target 25+, GuicedEE BOM import, and a JUnit/Mockito testing stack.
  • Validate and ensure main/test package separation (test packages end with .test and do not share packages with main), plus a bootstrap main class that initializes Guice context.

Quick Start

Provide module details to GuicedEE Creator to scaffold a new Maven module with baseline constraints.

Frequently Asked Questions about guicedee-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a Maven module with JPMS module-info.java for both main and test sources?

Scaffolding a Maven module with JPMS boundaries generates separate module-info.java files for main and test sources, ensuring test packages end with .test and do not share packages with main to maintain strict module isolation.

What baseline do I need for a GuicedEE-compliant Maven module?

A GuicedEE-compliant Maven module requires a Maven wrapper pinned to Maven 4, Java release and source targets set to 25+, a GuicedEE BOM import, and a JUnit/Mockito testing stack to meet baseline constraints.

How do I set up a bootstrap main class that initializes Guice context in a new Maven module?

Setting up a Guice context bootstrap involves generating a main class within the scaffolded Maven module that initializes the Guice injector context automatically during application startup to provide dependency injection.

Does Maven 4 scaffolding enforce BOM import and JPMS package separation between main and test?

Yes, Maven 4 scaffolding enforces GuicedEE BOM import and JPMS package separation by validating that test packages end with .test and do not overlap with main source packages across module boundaries.

Why does my JPMS test module need to open packages to required runtimes like Mockito?

JPMS test modules need to open packages to required runtimes like Mockito so the testing framework can access internal classes via reflection to inject mocks and verify behavior during test execution.