skills.rest
wagnerra23
wagnerra23COMMUNITY
Explore all skills by this author →
GitHub

mwart-process

Enforce the 5-phase MWART Blade-to-Inertia/React migration workflow for oimpresso screens.

Updated May 14, 2024
Search Tags:#feature flags#migration runbook#pest tests#mwarts-process#blade migration#inertia react#ui enforcement
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill mwart-process
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mwart-process
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/mwart-process
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill mwart-process

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents breaking changes and inconsistent UI outcomes when migrating legacy Blade screens to the oimpresso MWART Inertia/React architecture by enforcing a single, mandatory 5-phase path.

Core Features & Use Cases

  • End-to-end migration guardrails (MWART canônico, único caminho): enforces the required sequential phases PLAN → BACKEND BASELINE → FRONTEND INCREMENTAL → QA → CUTOVER, with explicit denial of premature edits.
  • Safe enforcement before code changes: blocks any Edit/Write to resources/js/Pages/<Mod>/<Tela>.tsx or controllers calling Inertia::render(<Mod>/<Tela>) unless RUNBOOK and SPEC exist and backend baseline is marked done.
  • Quality and risk controls per phase: requires dual/feature-flag strategy, Pest baseline coverage, audit thresholds, smoke and canary validation, and a monitored cutover with DB backup and rollback plan.

Quick Start

Ask the AI to migrate the Blade screen into MWART by following the mwart-process canônico using the required RUNBOOK and SPEC, producing a dual+flag backend baseline, then an incremental Inertia/React implementation with audits and QA until cutover readiness.

Frequently Asked Questions about mwart-process

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

FAQPage Schema
How do I safely migrate Blade screens to Inertia and React?▼

Safely migrating Blade screens to Inertia and React requires a sequential 5-phase process: PLAN, BACKEND baseline, FRONTEND incremental, QA, and CUTOVER. This enforces validation gates and prevents breaking changes during the transition.

What is the required workflow for migrating controllers calling Inertia render to React?▼

Migrating controllers calling Inertia render requires a RUNBOOK and SPEC before any edits are allowed. The workflow enforces a completed backend baseline with feature flags, followed by incremental Inertia and React frontend implementation.

Do I need Pest tests and feature flags for a Blade to React migration?▼

Yes, a Blade to React migration requires Pest tests and feature flags. The process mandates a dual strategy with feature flags and Pest baseline coverage to ensure quality and risk controls across all migration phases.

What are the limitations of skipping the backend baseline phase in Inertia React migrations?▼

Skipping the backend baseline phase in Inertia React migrations blocks all frontend edits. The workflow requires the backend baseline epic to be marked done before allowing incremental frontend implementation to proceed safely.

Can I edit Inertia React Pages directly without a migration runbook?▼

No, you cannot edit Inertia React Pages directly without a migration runbook. The workflow enforces safe guards that block writes unless both the RUNBOOK and SPEC documentation exist and pass validation completeness checks.

When do I need a monitored cutover with DB backup for UI migrations?▼

You need a monitored cutover with DB backup for UI migrations during the final phase. It requires smoke and canary validation, audit thresholds, and a rollback plan to ensure a safe transition to the new Inertia React architecture.

Related Skills

Explore More Software Engineering Skills→
wagnerra23wagnerra23

migracao-blade-react

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

Community
Advanced
AI-Foundry-CoreAI-Foundry-Core
4

launch-rollout-patterns

Plan phased feature rollouts with canary deployments and rollback thresholds.

Official
Advanced
BEE-CODEDBEE-CODED
1

laravel-inertia-react

Enforce Laravel 12, Inertia 2, and React 19 development standards with TailwindCSS.

Official
Advanced
sraloffsraloff
2

ui-frontend-design

Provide UI/UX guidelines for Laravel Blade and modern frontend ecosystems.

Community
Advanced