What problem does it solve? Building consistent Laravel + Inertia + Vue interfaces requires coordinating PHP controllers, Vue components, and a shared component registry, and ad-hoc local components quickly diverge from the design system. This Skill guides the selection, installation, and composition of StackTrace UI registry components and its Composer-shipped frontend package so both sides of an Inertia feature stay consistent. ## Core Features & Use Cases - Component selection and installation: Choose from a catalog of registry components (Button, Dialog, Table, Calendar, Chart, and more) and install missing ones via the shadcn-vue registry CLI instead of copying approximations. - Frontend package guidance: Use @stacktrace/ui composables such as useFilter, useNavigation, useToggle, and asyncRouter, with correct Vite and TypeScript alias configuration. - PHP-rendered UI: Build tables, menus, breadcrumbs, links, icons, select options, and toasts with StackTrace\Ui PHP value objects passed as Inertia props. - Use Case: When adding a data table page, the Skill directs you to check components.json aliases, install the Data Table registry component, build the table definition in the controller with the PHP API, and verify the Vue renderer consumes the props correctly. ## Quick Start Ask the agent to add a StackTrace UI confirmation dialog to an existing Inertia Vue page and wire it to the corresponding Laravel controller action.
