migracao-blade-react

Migrate Laravel Blade screens to Inertia/React TSX with parity checks.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill migracao-blade-react
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migracao-blade-react
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/migracao-blade-react
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill migracao-blade-react

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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_id scoping, 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."

Frequently Asked Questions about migracao-blade-react

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Laravel Blade views to Inertia React without visual regressions?

Migrating Laravel Blade views to Inertia React without visual regressions requires a parity-first workflow that captures visual snapshots, translates layouts to React TSX, and gates progression on visual comparison approval before running automated validation.

What is the best way to preserve business_id scoping when converting Blade templates to React TSX?

Preserving business_id scoping during Blade to React TSX conversion requires enforcing Tier 0 guardrails that explicitly forbid removing multi-tenant safety checks, permission validations, and existing business logic from the adapted controllers.

Can I migrate partial Blade files or email templates to Inertia React TSX?

Partial Blade files, email templates, PDF generators, and vendor views cannot be migrated to Inertia React TSX through this workflow, which strictly applies to LIST, DETAIL, FORM, DASHBOARD, and REPORT pages with active legacy routes.

How do you run automated Pest tests after migrating a Blade screen to Inertia?

Running automated Pest tests after migrating a Blade screen to Inertia involves executing a smoke validation step that checks the generated React TSX components and adapted controllers against the legacy behavior before submitting a pull request.

Does Blade to Inertia migration work for multi-tenant ERP systems?

Blade to Inertia migration works for multi-tenant ERP systems by enforcing safety guardrails that protect business_id scoping, maintain permission checks, and orchestrate a controlled six-step workflow from visual snapshot to approved PR.

What do I need before migrating Blade screens to React TSX using a parity workflow?

Before migrating Blade screens to React TSX, you need active legacy routes for the target page and available Cowork UI mockups to establish visual parity, along with runbook templates tailored to the screen type.