bottelet
- 14 skills
- 0 followers
- 6 hours ago last updated
- ▌ Dto Contract · botteletDefines DTO structure, lifecycle, and transformation rules across the application
- ▌ Pest Control · botteletEnforces 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.
- ▌ Service Layer · botteletDefines application service structure and business orchestration boundaries
- ▌ Github Actions PHP · botteletDefines GitHub Actions configuration for running PHP/Laravel CI pipeline
- ▌ Phpunit Test Naming · botteletEnforces grammatically correct, intention-revealing PHPUnit test method names
- ▌ Sync Stale Branches · botteletBrings diverged remote branches up to date with develop — classifies, rescues unique work, then resets or deletes stale branches
- ▌ Data Layer Contracts · botteletDefines the schema-to-factory-to-seeder contract chain — NOT NULL alignment, factory/seeder ownership boundaries, and schema drift rules
- ▌ Safe Refactoring Rules · botteletEnsures all refactoring is deterministic, behavior-preserving, and non-breaking
- ▌ CI Schema Invariant Gate · botteletEnsures correct execution order of migrations, seeders, and tests in CI
- ▌ Security Review Checklist · botteletStatic review rules for authorization, validation, and privilege escalation risks
- ▌ Autonomous Coding Workflow · botteletGoverns safe, incremental, repository-wide development workflow with continuous validation gates
- ▌ Application Architecture Standard · botteletDefines structural rules for Laravel architecture, layering, and code organization
- ▌ Senior Laravel Developer Code Reviewer · botteletOrchestrates existing Laravel skills to produce structured PR reviews
- ▌ Senior Laravel Developer Phpunit Interpreter · botteletCleans 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.