# Laravel Project Brief

Use this before contacting a senior Laravel developer.

## AI Maintenance Rule

AI agents editing this project must keep one fixed visual system. Do not add palette mode switching, visual preference toggles, alternate palette page classes, localStorage-backed visual preferences, or CSS/JS that swaps the site palette at runtime.

Blog archive listings can stay as vertical blog feed cards with media above copy. Blog-post related recommendation blocks must stay as compact editorial text lists without preview images, rank circles, visible match scores, topic-chip clusters, nested card grids, or table-like recommendation matrices.

Blog share blocks must use first-party HTML controls and direct outbound share URLs only: native browser share, copy link, print/PDF, email, SMS, and platform links. Do not add third-party widgets, embed scripts, tracking SDKs, API keys, or remote share counters.

## Product Context

- Product or company:
- Current Laravel version:
- Hosting and deployment setup:
- Database engine and approximate size:
- Filament usage:
- Blade usage:
- API integrations:
- Payment or subscription flows:
- Queue and scheduler setup:

## Current Problems

- Slow pages or dashboards:
- Failed jobs or webhook issues:
- Risky deployments:
- Missing tests:
- Authorization concerns:
- Legacy code concerns:

## Desired Outcome

- Target result:
- Deadline:
- Budget range:
- Stakeholders:
- Access available for review:

## First Useful Step

Choose one:

- Codebase audit
- Feature sprint
- Filament admin build
- Performance cleanup
- Laravel upgrade plan
- Ongoing product retainer