DaybydayCRM

Defines structural rules for Laravel architecture, layering, and code organization

Defines DTO structure, lifecycle, and transformation rules across the application

Defines application service structure and business orchestration boundaries

Governs safe, incremental, repository-wide development workflow with continuous validation gates

Ensures correct execution order of migrations, seeders, and tests in CI

Defines the schema-to-factory-to-seeder contract chain — NOT NULL alignment, factory/seeder ownership boundaries, and schema drift rules

Defines GitHub Actions configuration for running PHP/Laravel CI pipeline

Enforces PHPUnit-only testing in this project. Activates when writing tests, reviewing test files, or when any Pest syntax appears (it(), test(), describe(), uses(), expect() chains, beforeEach/afterEach hooks). Scans for and eliminates all Pest references from code, config, and documentation.

Enforces grammatically correct, intention-revealing PHPUnit test method names

Ensures all refactoring is deterministic, behavior-preserving, and non-breaking

Static review rules for authorization, validation, and privilege escalation risks

Orchestrates existing Laravel skills to produce structured PR reviews

Cleans and interprets raw PHPUnit CI logs into a compact, AI-friendly failure report. Use this skill whenever the user pastes or uploads a PHPUnit log, GitHub Actions test output, CI test results, or asks to interpret/summarize/analyze failing tests. Trigger even if the user says things like "here's my test output", "tests are failing", "can you look at my PHPUnit log", or pastes a block of text that contains PHPUnit output. Always use this skill before attempting to diagnose failures.

Brings diverged remote branches up to date with develop — classifies, rescues unique work, then resets or deletes stale branches