Skip to content
Skills Library
Programming · Building & coding

modularize

/modularize

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

Repository
agents ↗
Licence
MIT
Last repository change
12.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Triggers from the description

modularize\convert to modules\migrate to modular\restructure modules\
Original author description

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

How it works

  1. Agent Workflow (MANDATORY)
  2. Framework Detection
  3. Critical Rules
  4. Workflow Steps
  5. Reference Guide
  6. DO / DON'T
Original SKILL.md headings · 51 lines, 376 words
SKILL.md preview
---
name: modularize
description: "Use when converting existing code to modular architecture (Laravel, Next.js, React). Triggers: \"modularize\", \"convert to modules\", \"migrate to modular\", \"restructure modules\"."
user-invocable: true
references: references/laravel-fusecore.md, references/nextjs-react-modules.md
related-skills: apex-methodology, exploration
---

<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

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

| 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
Files in this package (3)
  • SKILL.md 3 KB
  • references/laravel-fusecore.md 2 KB
  • references/nextjs-react-modules.md 3 KB

Versions

RepositoryScoreLicence
This page · fusengine/agents90MIT
anthony-chaudhary/fak100Apache-2.0
yamcodes/arkenv90MIT

Database snapshot: 13.11.2026 · package version c66bf6cfae4f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90modular-architecture-refactor
    Plans and performs behavior-preserving architectural refactoring of an existing codebase toward orthogonal, loosely coupled, highly cohesive, plugin-ready modules. Use when the user asks to restructure or modularize a project, split a god class or monolithic module, break…
  • 100modularize-brave-browser
    Modularize Brave browser code: move a //brave/browser directory out of the brave_chrome_browser_sources monolith into its own headers/impl/test targets, or remove an allow_circular_includes_from entry from Brave GN files. Triggers on: modularize, componentize, Project Bedrock,…
  • 100modularize-chrome-browser
    Modularize a chrome/browser/ subfolder by splitting its sources out of the monolithic //chrome/browser:browser target into dedicated source_set targets in the subfolder's own BUILD.gn. Use when the user asks to modularize, extract, or create BUILD targets for a chrome/browser/…
  • 100fusecore
    Use when creating modules, understanding FuseCore structure, or implementing features in a FuseCore modular-monolith Laravel project.
  • 100refactor-plan
    Code-level refactoring analysis and roadmap. Detects duplication and complexity. Triggers on: refactor, tech debt, simplify, clean up, modularize, DRY, restructure.
  • 100acp-refactor
    Use when the user asks to refactor, clean up, simplify, modularize, deduplicate, rename, or improve the structure of existing code WITHOUT changing behavior. If the user wants new behavior, do not use this skill. Enforces small reversible steps and behavior preservation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.