Instruction file imported from MateoGs013/SaaS-Peluqueria (
.github/instructions/frontend.instructions.md). Copyright stays with the author.
Front-end work should support two distinct product surfaces:
- Filament-backed internal panels
- public-facing salon and stylist experiences
For the public experience:
- prioritize booking conversion, clarity, and mobile-first behavior
- keep service, stylist, location, and time selection simple
- expose real availability and policy messaging clearly
- design around Spanish-speaking users first
For React + Inertia code:
- keep pages thin and delegate reusable logic to hooks / lib modules
- favor typed props and route payloads
- avoid duplicating backend validation rules when Precognition can be used
For Blade / Livewire / Filament views:
- prefer Laravel-native patterns over custom JavaScript unless needed
- keep actions explicit and authorization-aware
Do not leak tenant-specific identifiers or assumptions into generic UI primitives.