Onboard Existing Source into a Proper Module - Fluent AI Skills
How-to Guide
Author:
Fluent Commerce
Changed on:
31 Mar 2026
Key Points
[Warning: empty required content area]Prerequisites
Steps
Onboard the Source
`Refactor this code into a Fluent module: accounts/MY_PROFILE/SOURCE/backend/.decompiled/fc-module-ext/`Or for loose Java files:
`/fluent-module-convert ./my-rules/ --module-name my-returns`The skill: 1. Analyzes the existing layout (decompiled JAR? loose files? Gradle project? partial module?) 2. Discovers all rule classes (by
`@RuleInfo`, `BaseRule` extension, `run()` methods) 3. Plans the target Maven multi-module structure with a full file operations table 4. Waits for your approval before changing anythingReview the Plan
The plan shows exactly what will happen: - Which files move where - What code changes are needed (package renames, base class fixes, missing annotations) - Risk assessment (package renames breaking imports, decompiled artifacts, key conflicts)
Execute and Validate
After approval:
- Creates the Maven multi-module directory structure
- Moves and repackages Java files
- Fixes structural issues (wrong base class, missing
`@RuleInfo`, etc.) - Generates
`module.json`with all rule registrations - Generates build scripts, POMs,
`.gitignore` - Generates test skeletons for untested rules
- Runs
`/fluent-module-validate`to verify structure - Attempts a Maven build to verify compilation
- Cross-references against deployed rules
