fusecore_skill

Overview

This skill describes FuseCore, a Laravel 12 modular monolith architecture with auto-discovery, isolated React integration, and SOLID-driven conventions. It guides creating modules, enforcing directory rules, and integrating frontend pieces per module for predictable, maintainable projects.

How this skill works

The guide inspects and enforces FuseCore conventions: module placement under /FuseCore/{Module}/, a required module.json for auto-discovery, and a ServiceProvider per module using the HasModule trait. It also prescribes an agent workflow: spawn three agents (fuse-ai-pilot:explore-codebase, fuse-ai-pilot:research-expert, fuse-laravel:laravel-expert) before implementation and run fuse-ai-pilot:sniper after changes for validation.

When to use it

• Starting a new feature as an isolated module within a Laravel 12 monolith.
• Onboarding to an existing FuseCore project to understand directory and contract rules.
• Integrating React UI per feature while preserving module boundaries.
• Implementing migrations, routes, or services that must remain modular and discoverable.
• Validating architecture compliance and SOLID constraints before merging code.

Best practices

• Keep all module code inside /FuseCore/{Module}/; never place module code in /app/.
• Provide one module.json per module with name, version, enabled flag, and dependencies.
• Add a ServiceProvider using the HasModule trait and register migrations in boot().
• Limit files to under 100 lines; split files at ~90 lines to maintain SOLID and readability.
• Place interfaces under App/Contracts/ and keep migrations and routes inside the module.
• Use isolated Resources/React/ and per-module i18n locales for frontend separation.

Example use cases

• Create a BlogPost module with Models, Controllers, Migrations, Routes/api.php, Resources/React, and module.json declaring User dependency.
• Add a new API resource: implement controller and routes inside the module and register via the module ServiceProvider.
• Migrate a legacy feature into FuseCore by relocating files into a module folder, creating module.json, and adding a ServiceProvider.
• Build a React admin widget shipped inside a module’s Resources/React with its own i18n locales.
• Run the recommended agent workflow to analyze the codebase, verify Laravel 12 patterns, and validate changes after implementation.