skills.rest
ohnotnow
ohnotnowCOMMUNITY
Explore all skills by this author →
GitHub

ui-to-flux

Migrate legacy Laravel applications to Flux UI with template-first workflows.

1|Updated Feb 22, 2026
Search Tags:#migration#patterns#laravel#livewire#flux-ui#template-migration
One-click install
npx skills add https://github.com/ohnotnow/agentic-stuff --skill ui-to-flux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-to-flux
Source: https://github.com/ohnotnow/agentic-stuff/tree/main/skills/ui-to-flux
Command: npx skills add https://github.com/ohnotnow/agentic-stuff --skill ui-to-flux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate legacy Laravel applications to modern Livewire + Flux UI by outlining what to change and in what order to achieve a smooth transition.

Core Features & Use Cases

  • Provides a template-first migration approach that avoids premature Livewire conversion.
  • Offers a layout-first strategy, then component migration, with references to flux-ui and modern-livewire for target patterns.
  • Includes a recommended workflow and optional use of the MCP tool for up-to-date Flux documentation.

Quick Start

Begin migration by mapping templates and updating the layout first, then migrate components using Flux UI patterns and Livewire guidance.

Frequently Asked Questions about ui-to-flux

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

FAQPage Schema
How do I migrate legacy Laravel applications to Flux UI?▼

Migrate legacy Laravel applications to Flux UI by mapping templates first, updating the layout, then migrating components using Flux UI patterns and Livewire integration guidance.

What is the best way to transition Laravel templates to Livewire and Flux UI?▼

Transition Laravel templates to Flux UI by using a template-first migration approach that avoids premature Livewire conversion, ensuring a smooth layout-first strategy before component updates.

Do I need to convert all Laravel components to Livewire before using Flux UI patterns?▼

You do not need to convert all Laravel components to Livewire prematurely; the migration strategy is template-first, updating layouts and components sequentially using Flux UI patterns.

Can I use the Laravel MCP tool to get up-to-date Flux UI documentation during migration?▼

Use the optional Laravel MCP tool during your Flux UI migration to fetch up-to-date Flux documentation and reference modern-livewire patterns for accurate component conversion.

What order of operations should I follow when updating to Flux UI in Laravel?▼

Follow a layout-first order of operations for Flux UI migration: begin by mapping templates, update the primary layout, then migrate individual components sequentially using target patterns.

Are there specific patterns to reference when moving Laravel templates to Flux UI?▼

When moving Laravel templates to Flux UI, reference flux-ui and modern-livewire patterns to guide your component migration and ensure proper Livewire integration throughout the application.

Related Skills

Explore More Software Engineering Skills→
elab-developmentelab-development

fluxui-development

Create Flux UI components in Laravel Blade and Livewire workflows.

Official
Basic
bmadiganbmadigan
1

livewire-form

Creates validated, WCAG-aware, interactive prototypes with Tailwind and React components.

Community
Intermediate
karuhun-developerkaruhun-developer
5

fluxui-development

Develop custom UI components for Laravel Livewire applications using Flux UI.

Official
Intermediate
HubDigitalEPNHubDigitalEPN
1

livewire-development

Build and optimize Livewire components in Laravel with migration guidance.

Official
Intermediate