What problem does it solve? It enforces a disciplined red-green-refactor workflow for Laravel development, ensuring every feature, bugfix, and API endpoint is backed by a failing test before any implementation code is written. ## Core Features & Use Cases - Laravel TDD Cycle: Walks through writing a failing Pest test, verifying the failure, writing minimal code to pass, and refactoring safely. - Framework-Specific Test Patterns: Provides ready-to-use Pest examples for database testing with RefreshDatabase, authorization checks, and API endpoint testing with Sanctum. - Verification Checklist: Ensures migrations, model relationships, validation rules, and authorization are all covered by tests. - Use Case: When adding a new endpoint like creating posts, write the feature test first, watch it fail, then implement the controller and model logic until the suite passes. ## Quick Start Ask the assistant to implement a new Laravel feature using test-driven development with Pest, starting from a failing test.