guicedee-installer

Retrofit existing Maven projects to GuicedEE baseline standards with JPMS module boundaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Retrofit existing Maven projects to GuicedEE baseline standards, including Maven 4 wrapper, BOM import, enforcer rules, and JPMS module boundaries to improve consistency and maintainability.

Core Features & Use Cases

  • Patch pom.xml to align with retrofit checklist (Java baseline 25+, BOM import, enforcer rules)
  • Update Maven wrapper to Maven 4 and create/repair module-info.java for main and test modules
  • Ensure test packages open and module exports/opens reflect safe defaults
  • Bootstrap a main class with Guice context injection and logging
  • Validate and register lifecycle SPI implementations where applicable
  • Use case: An existing Java project with a multi-module structure gets infrastructure-ready for GuicedEE baseline and JPMS compatibility.

Quick Start

Run the installer on your project root to apply the GuicedEE baseline retrofit.

Frequently Asked Questions about guicedee-installer

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

FAQPage Schema
How do I retrofit an existing Maven project to use JPMS module boundaries?

To retrofit a Maven project to JPMS, you need to create or repair module-info.java files for main and test modules, ensuring safe package open and export directives are applied for proper module separation.

What is the best way to align Maven wrapper and dependency management for a Java project?

Aligning Maven dependency management involves patching pom.xml to import a BOM, applying enforcer rules, and updating the Maven wrapper to align project infrastructure with standardized baseline requirements.

How do I set up JUnit and Mockito testing when migrating to JPMS?

Setting up JUnit and Mockito during a JPMS migration requires ensuring test packages are open and configuring module-info.java so test modules have the necessary access to run tests correctly.

Can I apply GuicedEE baseline standards to a multi-module Java project structure?

Yes, applying GuicedEE baseline standards to a multi-module Java project patches the pom.xml, updates the Maven wrapper, and establishes JPMS module boundaries to make the infrastructure ready.

What do I need to bootstrap a main class with Guice context injection and logging?

Bootstrapping a main class with Guice context injection and logging is part of applying GuicedEE baseline standards, which also includes validating and registering lifecycle SPI implementations.

Does retrofitting to GuicedEE baseline require a specific Java version?

Yes, retrofitting a project to GuicedEE baseline standards applies a checklist that targets a Java baseline of 25 or higher, alongside Maven 4 wrapper alignment and BOM dependency management.