Modularize

Skill fusengine/agents/plugins/ai-pilot/skills/modularize

Redefining development through cognitive automation and collaborative agent systems.

Install

npx -y skills add fusengine/agents --skill modularize

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when converting existing code to modular architecture (Laravel, Next.js, React). Triggers: "modularize", "convert to modules", "migrate to modular", "restructure modules".

SKILL.md

2.9 KB, as published. Nobody here has run it

<objective> Modularize converts an existing, non-modular codebase to a modular architecture. It detects the framework (Laravel + FuseCore, standard Laravel, Next.js with modules/, or plain React) and delegates to the matching framework expert, but owns the process itself: explore the full structure, build and present a file-by-file migration map, wait for explicit user confirmation, execute the move step by step, and run `fuse-ai-pilot:sniper` after every file change.

The core constraint it enforces is that shared logic always routes through a central core -- never module-to-module imports directly. </objective>

Agent Workflow (MANDATORY)

detect framework → explore structure → build migration plan → confirm with user → execute → sniper

Framework Detection

Signal	Framework	Delegate To
`FuseCore/` dir + `artisan` file	Laravel + FuseCore	`fuse-laravel:laravel-expert`
`composer.json` + `artisan` (no FuseCore/)	Laravel standard	`fuse-laravel:laravel-expert`
`src/modules/` or `app/` + `next.config`	Next.js + modules/	`fuse-nextjs:nextjs-expert`
`src/` + `package.json` (React, no Next)	React	`fuse-react:react-expert`

Critical Rules

Analyze first — always explore full structure before proposing anything
Show migration map — present file-by-file plan before touching any code
User confirms — never move or modify files without explicit approval
Cores = central hub — no module-to-module imports; all shared logic goes through core
Sniper after each file — run fuse-ai-pilot:sniper after every file moved or created

Workflow Steps

Detect framework using signals from the table above
Explore codebase: map all files, dependencies, imports, exports
Build migration plan: list every file to create, move, or refactor
Present plan to user — wait for explicit confirmation before proceeding
Execute step by step; stop and report any conflict immediately
Run sniper validation after each file change
Final report: list all changes made and any remaining manual steps

Reference Guide

Stack	Reference File
Laravel (FuseCore or standard)	`references/laravel-fusecore.md`
Next.js / React	`references/nextjs-react-modules.md`

DO / DON'T

DO: explore before planning — plan before executing — confirm before touching files — sniper every step

DON'T: assume structure — skip confirmation — import between modules directly — batch changes without validation