AI SummaryAimTrack Copilot Instructions provides Laravel developers with expert guidance on building a shooting logging application using Laravel 12, Filament v4, and modern PHP 8.4 stack with privacy-first architecture. It benefits developers working on sports tech applications or those needing specialized domain knowledge for ballistics/shooting sport software.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "AimTrack — Copilot Instructions" prompt rules to my project. Repository: https://github.com/Marcvdc/AimTrack 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
AimTrack is een moderne AI-gedreven schietlogapp voor sportschutters. Registreer sessies, wapens en munitie, upload kaarten, ontvang automatische AI-reflecties en inzichten, beheer je wapens en genereer exports (CSV/PDF) voor o.a. WM-4. Privacy-first, self-hosted en gebouwd met Laravel + Filament.
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.4.11 • filament/filament (FILAMENT) - v4 • laravel/framework (LARAVEL) - v12 • laravel/pennant (PENNANT) - v1 • laravel/prompts (PROMPTS) - v0 • livewire/livewire (LIVEWIRE) - v3 • laravel/mcp (MCP) - v0 • laravel/pint (PINT) - v1 • pestphp/pest (PEST) - v4 • phpunit/phpunit (PHPUNIT) - v12
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, and naming. • Use descriptive names for variables and methods. For example, isRegisteredForDiscounts, not discount(). • Check for existing components to reuse before writing a new one.
Verification Scripts
• Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important.
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