Skip to content
  • AI Toolkit plugin
  • v0.1.3
  • 6 skills
  • 1 agent
  • 2 rules

inertia-react: Inertia and React frontend skills

Have an agent write Inertia and React pages to the patterns your project already uses, with typed page props, forms built from shadcn parts and a browser-mode test beside each component it touches.

  1. /plugin marketplace add noppu-labs/ai-toolkit
  2. /plugin install inertia-react@ai-toolkit

01 — What it does

What the inertia-react plugin gives a frontend.

  • inertia

    Inertia pages, forms and navigation

    laravel-inertia-react groups its rules by prefix, among them page-, form-, nav-, shared- and layout-. They run from typing page props and showing validation errors from useForm to partial reloads, flash messages and persistent layouts.

  • shadcn

    shadcn guidance that reads the project

    shadcn loads npx shadcn@latest info --json, the project config and installed components. Its critical rules include forms built from FieldGroup and Field, flex with gap-* in place of space-y-*, and a title on every Dialog, Sheet and Drawer.

  • tailwind

    Tailwind advice that checks the version first

    tailwind-best-practices checks package.json before advising, since v3 and v4 differ. An @import "tailwindcss" line or an @theme {} block points to v4, and a tailwind.config.js file points to v3.

  • state

    React Query and Zustand, with a persist warning

    state-management is written for TanStack Query v5 and Zustand v5. It says never to persist auth tokens, passwords or secrets to localStorage or sessionStorage, and to persist only non-sensitive state through partialize.

  • types

    Typed components and a faster Vite build

    typescript-react-patterns starts with props and hook types, then events, refs, generics, context and utility types. react-vite-best-practices starts with the build and code splitting, then the dev server, assets, environment variables and bundle analysis.

  • agent

    A frontend agent written around Inertia v3 and React 19

    frontend-developer assumes a Laravel 13 app on Inertia v3, React 19, TypeScript 6, Vite 8, Tailwind v4 and TanStack Table v8. It runs on the sonnet model and keeps project memory between sessions.

02 — Skills

The inertia-react skills.

03 — How it works

What a frontend task looks like.

  1. Each skill's description lists the work it covers. laravel-inertia-react names page components and useForm, and state-management names useQuery and Zustand stores. Installed from the marketplace, the skills are namespaced, as in inertia-react:shadcn.
  2. The agent builds URLs with Wayfinder route helpers and never by hand, validates forms with Zod on top of Inertia's useForm, sorts and pages tables on the server, and wraps UI that needs a permission in a gate component.
  3. Before it reaches for a new library or hook, the agent looks at what features/, hooks/ and components/ already do, and it asks before creating a top-level folder.
  4. Each new or changed component gets a .test.tsx and a .stories.tsx, with tests in Vitest 4 browser mode through vitest-browser-react. The agent finishes a task with npm run format && npm run agent-checks.
  5. /inertia-react:install-rules copies the rule files into .claude/rules/. An identical file is skipped. A different one is reported as a conflict, shown as a diff and left to you.
  6. code-quality-ts covers resources/js/**/*.{ts,tsx}, .storybook/**/*.{ts,tsx} and *.config.ts. testing-vitest covers resources/js/**/*.test.{ts,tsx}: it instead of test, a describe per function, tests beside the file, no React Testing Library.

04 — Requirements

What you need.

  • A frontend in resources/js, which is where the rules apply and where the agent looks for pages, hooks and components.
  • format and agent-checks npm scripts, which the agent and the code-quality-ts rule run at the end of a task. Change the copied rule if your scripts have other names.
  • For shadcn, a project with a components.json, which the skill reads through the shadcn CLI.

05 — Questions

Before you install.

Which versions do the Inertia and React skills assume?

laravel-inertia-react names Laravel 13.x on PHP 8.3 or later, and tailwind-best-practices covers Tailwind v3.4 and later, v4 included. The agent is pinned to Inertia v3 and React 19.2, so it writes lazy props with Inertia::optional(). Some laravel-inertia-react examples are older: they still use Inertia::lazy(), which v3 removed, and Ziggy routes, where the agent uses Wayfinder.

Does it need the laravel plugin?

No. Each plugin installs on its own. The two do expect the same kind of app: the agent looks for pages under resources/js/pages that Laravel controllers return through Inertia::render.

How does it differ from the laravel plugin?

inertia-react covers what runs in the browser: pages, forms, components, styling, client state and the Vite build. laravel covers the PHP side, from controllers and models to policies and tests. A Laravel and Inertia app can use both, with frontend-developer on resources/js and laravel-backend-specialist on the PHP.

Does the inertia-react plugin work in OpenCode?

Not as a package, since only review and investigate have OpenCode packages. The skills CLI copies the skill folders alone, which leaves frontend-developer and the rules behind.

Where do the skills come from?

shadcn comes from the shadcn/ui repository and the rest from AsyrafHussin/agent-skills, each copied in at a pinned upstream commit.

Is the frontend agent tied to one codebase?

Partly. It was written around one app's layout and helpers: it expects a useZodForm hook, a shared DataTable with useTableState, and permission gates in components/auth/PermissionGates.tsx, none of which the plugin ships. In another project, expect to point it at your own equivalents or adjust it.

More plugins

All plugins