boost-search-docs-first
Use Laravel Boost search-docs to verify the correct, version-specific approach before implementing Laravel ecosystem features.
When & Why to Use This Skill
This Claude skill enhances Laravel development accuracy by integrating Laravel Boost's search-docs tool. It ensures that implementations for the Laravel ecosystem—including Livewire, Tailwind CSS v4, and Pest—are version-specific and follow the latest best practices, effectively preventing the use of outdated patterns and reducing technical debt.
Use Cases
- Verifying version-specific syntax for Laravel framework features like routing, middleware, and validation before implementation to avoid legacy patterns.
- Implementing modern UI components using Tailwind CSS v4 and Flux UI by confirming the latest utility classes and component behaviors.
- Ensuring correct usage of Livewire 3 features and Volt functional components to maintain project consistency and performance.
- Setting up first-party Laravel packages such as Fortify, Horizon, or Pulse using verified, up-to-date documentation.
- Writing robust test suites with Pest v4 by confirming the latest testing APIs and browser testing features before writing test code.
| name | boost-search-docs-first |
|---|---|
| description | Use Laravel Boost search-docs to verify the correct, version-specific approach before implementing Laravel ecosystem features. |
Use Boost Docs First
Goal
Avoid incorrect or outdated implementations by verifying the approach using Laravel Boost’s search-docs tool before
writing code.
This skill applies to Laravel ecosystem features where behaviour, APIs, or best practices vary by version.
When to Apply
Use Boost search-docs before coding when the task involves any of the following:
- Laravel framework features (routing, middleware, validation, queues, auth)
- Livewire (including Volt and Livewire 3 behaviour)
- Flux UI (free or pro components)
- Fortify authentication features
- Tailwind CSS v4 utilities or patterns
- Pest v4 testing features
- Horizon, Pulse, Nightwatch, or other Laravel first-party packages
If you are unsure about syntax, behaviour, or best practice, assume this skill applies.
How to Apply
Start with
search-docsusing broad, simple queries
Examples:['livewire pagination']['fortify registration']['tailwind v4 grid']['pest browser test']
Narrow the query only if needed after reviewing initial results.
Verify the approach against:
- Installed package versions
- Existing project patterns in sibling files
Only proceed to implementation once the documented approach is confirmed.
What NOT to Do
- Do not rely on general Laravel knowledge if documentation is available.
- Do not guess APIs or options when Boost can confirm them.
- Do not copy patterns from older Laravel, Livewire, or Tailwind versions without verification.
Exceptions
You may skip search-docs if:
- The change is trivial and already follows an existing, identical pattern in the codebase.
- The user explicitly instructs you to proceed without documentation lookup.
Anti-patterns
- Writing code first and checking docs afterward.
- Mixing documentation from different major versions.
- Assuming behaviour based on pre-Laravel 11 conventions.