migracao-blade-react
CommunityMigrate Blade screens to Inertia without regressions
Software Engineering#runbooks#visual parity#migration orchestration#react tsx#multi-tenant safety#pest tests#blade to inertia
Authorwagnerra23
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This Skill prevents visual and functional regressions when migrating legacy Blade views to an Inertia/React front end in a multi-tenant Laravel ERP, by enforcing a controlled, parity-first workflow.
Core Features & Use Cases
- Guided 6-step migration pipeline for each requested screen: snapshot parity, visual translation, minimal controller adaptation, visual gate approval, automated Pest + smoke, and a disciplined PR limited by intent.
- Runbook templates by screen type (LIST, DETAIL, FORM, DASHBOARD, REPORT) to standardize the produced migration artifacts and checks.
- Safety guardrails for Tier 0 migration including preserving
business_idscoping, keeping permission checks, and refusing partial/inapplicable migrations (partials/emails/PDF/vendor, or already-migrated TSX).
Quick Start
Ask the AI to run a migration for a specific screen, for example: "Migrate Blade view Crm/Compras index.blade.php to Inertia for the Crm module, preserving all routes, permissions, and business_id scoping."
Dependency Matrix
Required Modules
None requiredComponents
references
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: migracao-blade-react Download link: https://github.com/wagnerra23/oimpresso.com/archive/main.zip#migracao-blade-react Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.