fusengine 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:sniperafter 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