Skip to content
Prompt

getresi-software-engineer-filamentphp-demo — Copilot Instructions

by danielh-official

AI Summary

A Copilot instruction set that provides Laravel and Filament PHP development guidelines, conventions, and best practices for a real-estate application. Developers building Laravel applications with Filament will benefit from standardized coding patterns and dependency versions.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "getresi-software-engineer-filamentphp-demo — Copilot Instructions" prompt rules to my project.
Repository: https://github.com/danielh-official/getresi-software-engineer-filamentphp-demo

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

Demo site created for https://getresi.bamboohr.com/careers/40

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.15 • filament/filament (FILAMENT) - v4 • laravel/framework (LARAVEL) - v12 • laravel/nightwatch (NIGHTWATCH) - v1 • laravel/prompts (PROMPTS) - v0 • laravel/sanctum (SANCTUM) - v4 • livewire/livewire (LIVEWIRE) - v3 • laravel/mcp (MCP) - v0 • laravel/pint (PINT) - v1 • laravel/sail (SAIL) - v1 • pestphp/pest (PEST) - v4 • phpunit/phpunit (PHPUNIT) - v12 • prettier (PRETTIER) - v3 • tailwindcss (TAILWINDCSS) - v4

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.

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

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 2mo ago
Active
AdoptionUnder 100 stars
1 ★ · Niche
DocsMissing or thin
Undocumented

GitHub Signals

Stars1
Issues0
Updated2mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more