Laravel Guild Cookbooks

Eight Laravel cookbooks: conventions and antipatterns, testing, Eloquent performance, security, deployment, accessibility, docs and delivery templates.

What's included

• laravel-guild-cookbooks: Eight Laravel cookbooks from the Laravel Guild — conventions and antipatterns, testing, Eloquent performance, security review, deployment, accessibility, docs authoring, and delivery templates. Use when writing, reviewing, testing, securing, speeding up, or shipping Laravel/PHP code and you want the idiomatic answer, not a guess.
• accessibility-design: The WCAG 2.2 AA audit cookbook for Laravel front-ends and mobile — concrete thresholds (contrast, target size, focus), Livewire / Inertia focus-management specifics, screen-reader semantics, reduced motion, mobile a11y (VoiceOver / TalkBack, dynamic type). Use when designing screens, auditing UI for accessibility, or reviewing frontend / mobile work for the accessibility part of done.
• delivery-templates: Artifact templates for the planning + coordination roles — requirements doc, user story + acceptance criteria, RICE / WSJF scoring, sprint plan, retro, team-health report, stakeholder update, delivery log. Use when producing any docs/requirements, docs/backlog, docs/roadmap, or docs/sprints artifact, so every document lands in the same shape at the expected path.
• docs-authoring: Documentation templates + style rules — changelog (Keep a Changelog), release notes, runbook (Symptoms → Triage → Resolve), API endpoint reference block, onboarding guide. Use when writing or restructuring any docs surface so every page lands in a proven shape with tested examples and cited sources.
• eloquent-performance: The query-performance cookbook — reading EXPLAIN plans, diagnosing + fixing N+1 without overfetching, pagination and chunking choices, the caching decision tree (remember vs flexible vs lock), measurement discipline. Use when an endpoint or query is slow, before adding an index or cache, or when reviewing query-shape changes. Diagnosis recipes — the fix lands with the owning builder (backend / database developer).
• laravel-conventions: The idiomatic-Laravel convention reference — which primitive to reach for and which antipattern to refuse, across HTTP, Eloquent, validation, authorization, config, queues, and testing. Use when writing or reviewing Laravel/PHP code and you need the canonical "right way," when choosing between two approaches, or when something feels like it's fighting the framework. Pairs with laravel/agent-skills' laravel-simplifier (which refines after the fact); this guides the choice up front.
• laravel-deploy: The Laravel deployment cookbook — platform detection, zero-downtime release checklist, queue-worker + scheduler topology, rollback drill, post-deploy smoke. Use when building or reviewing a deploy pipeline, changing worker / scheduler topology, preparing a release, or writing an incident runbook's technical steps.
• laravel-security: The Laravel security-review cookbook — STRIDE applied to Laravel primitives, the authn / authz / mass-assignment / upload / injection checklist, advisory lookup procedure, and the finding format. Use when threat-modeling a feature, reviewing a PR that touches auth / PII / billing / uploads / middleware, or triaging a suspected vulnerability. Findings only — fixes land with the owning builder after human awareness.
• laravel-testing: The Laravel test-authoring cookbook — fakes with exact assertion syntax, Pest v4 browser testing vs Dusk, factory states + sequences, time control, DB strategies. Use when writing or reviewing Pest / PHPUnit tests, reproducing a bug as a regression test, choosing between fakes and mocks, or setting up browser tests. Recipes only — test strategy and Ship / Hold verdicts stay with qa-engineer.