agentsclimarketplace

Modularize

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

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

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.

2 things 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.
  • runs commandsInstructs the agent to run 3 commands, including `run `fuse-ai-pilot:sniper` after every file change` and 2 more.

SKILL.md

2.9 KB, 596 tokens by cl100k_base, 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

SignalFrameworkDelegate To
FuseCore/ dir + artisan fileLaravel + FuseCorefuse-laravel:laravel-expert
composer.json + artisan (no FuseCore/)Laravel standardfuse-laravel:laravel-expert
src/modules/ or app/ + next.configNext.js + modules/fuse-nextjs:nextjs-expert
src/ + package.json (React, no Next)Reactfuse-react:react-expert

Critical Rules

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

Workflow Steps

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

Reference Guide

StackReference File
Laravel (FuseCore or standard)references/laravel-fusecore.md
Next.js / Reactreferences/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

What ships with it: 2 files

4.6 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.