AI SummaryGearhead provides Laravel-specific copilot instructions for a Software Engineering 1 & Application Development project, defining ecosystem package versions, coding conventions, and architectural guidelines to maintain consistency across a Laravel + Inertia + React stack.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "Gearhead — Copilot Instructions" prompt rules to my project. Repository: https://github.com/FlareItsh/Gearhead Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Gearhead Carwash. Software Engineering 1 & Application Development project.
Inertia v2 New Features
• Polling • Prefetching • Deferred props • Infinite scrolling using merging props and WhenVisible • Lazy loading data on scroll
Laravel Boost Guidelines
The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to enhance the user's satisfaction building Laravel applications.
Foundational Context
This application is a Laravel application and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure you abide by these specific packages & versions. • php - 8.2.12 • inertiajs/inertia-laravel (INERTIA) - v2 • laravel/fortify (FORTIFY) - v1 • laravel/framework (LARAVEL) - v12 • laravel/prompts (PROMPTS) - v0 • laravel/sanctum (SANCTUM) - v4 • laravel/wayfinder (WAYFINDER) - v0 • tightenco/ziggy (ZIGGY) - v2 • laravel/mcp (MCP) - v0 • laravel/pint (PINT) - v1 • laravel/sail (SAIL) - v1 • pestphp/pest (PEST) - v3 • phpunit/phpunit (PHPUNIT) - v11 • @inertiajs/react (INERTIA) - v2 • react (REACT) - v19 • tailwindcss (TAILWINDCSS) - v4 • @laravel/vite-plugin-wayfinder (WAYFINDER) - v0 • eslint (ESLINT) - v9 • prettier (PRETTIER) - v3
Conventions
• You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, naming. • Use descriptive names for variables and methods. For example, isRegisteredForDiscounts, not discount(). • Check for existing components to reuse before writing a new one.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts