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

mwart-quality

Detect backend-to-frontend contract issues in MWART screen migrations.

Updated May 14, 2024
Search Tags:#schema validation#inertia#react migration#production guardrails#mwarr#frontend contracts#runtime smoke test
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill mwart-quality
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mwart-quality
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/mwart-quality
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill mwart-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents MWART UI regressions by catching backend↔frontend contract mistakes, schema mismatches, and routing/component API errors that commonly lead to runtime crashes and blank pages in production.

Core Features & Use Cases

  • Pre-flight validation for MWART screens: Applies targeted checks before enabling or reviewing a new MWART page migration or controller Inertia render.
  • Audit and pinpoint fixes: Reports violations with file and line context so reviewers can correct the exact issue instead of chasing symptoms in the UI.
  • Production guardrails for known bug patterns: Enforces strict payload shaping (arrays vs collections, no Highcharts/CommonChart objects), route/URL constraints, and canonical component prop contracts to avoid recurring PR failures.

Quick Start

Ask to migrate a specific Blade screen to MWART and request an audit-ready list of pre-flight issues to fix before the PR is marked done.

Frequently Asked Questions about mwart-quality

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

FAQPage Schema
How do I prevent blank pages when migrating Blade views to Inertia and React?▼

Preventing blank pages during Blade to Inertia/React migration requires pre-flight checks that detect backend-to-frontend payload, schema, routing, and component contract mismatches before enabling or merging. This validates prop contracts to stop runtime crashes before they reach production.

What causes white screen regressions in React frontend migrations from Laravel Blade?▼

White screen regressions in React frontend migrations stem from backend-to-frontend payload mismatches, schema drift, routing errors, and component prop contract violations occurring when controllers call Inertia::render with incorrect data shapes or unsupported objects.

How do I validate Inertia::render payload contracts before merging a React page migration?▼

Validating Inertia::render payload contracts before merging involves running pre-flight checks on controllers and TSX pages under resources/js/Pages to enforce strict payload shaping, route URL constraints, and canonical component prop contracts, ensuring contract parity.

Can I enforce production guardrails for Inertia React schema validation and routing?▼

Yes, enforcing production guardrails for Inertia React schema validation and routing involves applying checks that restrict payload shaping, prevent unsupported objects like Highcharts or CommonChart, and verify cockpit top navigation parity before deployment.

What pre-flight checks are needed for MWART screen migrations to Inertia and React?▼

MWART screen migrations to Inertia and React require 9 pre-flight checks enforcing payload shaping, schema validation, routing constraints, and component prop contracts, plus an additional visual hard gate for cockpit top navigation parity to prevent regressions.

How do I run a runtime smoke test for Inertia React pages in production-like conditions?▼

Running a runtime smoke test for Inertia React pages in production-like conditions requires MCP or browser console validation to verify payload delivery, routing, and component rendering behave correctly without runtime errors or blank screens.

Related Skills

Explore More Software Engineering Skills→
majiayu000majiayu000
12

sage-architecture

Define modular boundaries and naming conventions for Sage applications.

Community
Basic
spencerpaulyspencerpauly
672

visual-qa-testing

Verify web application UI behavior and visual output in Cursor's built-in browser.

Community
Intermediate
discord-phpdiscord-php
1.1k

builder-payload-smith

Maintain Discord API payload builders with validation and serialization rules.

Official
Advanced
wagnerra23wagnerra23

mwart-comparative

Generate a 15-dimension visual comparison artifact for MWART page migrations.

Community
Advanced