wayfinder-development

Generates type-safe Laravel route objects for Vue/TypeScript frontends.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/babou212/laradisco --skill wayfinder-development-babou212
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder-development
Source: https://github.com/babou212/laradisco/tree/main/.github/skills/wayfinder-development
Command: npx skills add https://github.com/babou212/laradisco --skill wayfinder-development-babou212

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Easily reference and generate type-safe backend routes from frontend code, reducing manual mapping and errors.

Core Features & Use Cases

  • Type-safe route objects for frontend calls
  • Automatic route generation after backend changes
  • Tree-shaking-friendly imports for smaller builds

Quick Start

Regenerate routes after changes and verify that imports resolve correctly.

Frequently Asked Questions about wayfinder-development

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

FAQPage Schema
How do I generate type-safe Laravel routes for a TypeScript frontend?

To use type-safe routing, import named routes from '@/actions' or '@/routes' in your TypeScript code, which generates route objects that automatically align with your Laravel backend definitions to reduce manual mapping errors.

How do I keep frontend route imports tree-shakeable when referencing backend URLs?

You can keep frontend route imports tree-shakeable by using named imports from '@/actions' or '@/routes', ensuring that only the referenced backend routes are bundled to maintain smaller build sizes.

Does Wayfinder routing work with Vue and TypeScript projects?

Yes, Wayfinder routing works with Vue and TypeScript projects by creating route objects that provide type-safe access to backend routes directly within your frontend components.

What is the best way to sync frontend route objects after backend Laravel changes?

The best way to sync frontend route objects after backend Laravel changes is to regenerate the routes and verify that the named imports from '@/routes' or '@/actions' resolve correctly in your TypeScript project.

Why do I need type-safe route objects for frontend backend calls?

You need type-safe route objects to prevent mapping errors when referencing backend routes, ensuring that frontend calls precisely match the Laravel backend definitions without manual string updates.