production-ready

Production-ready verification involves analyzing your codebase structure, running comprehensive Pest unit and feature tests, executing Playwright UI tests, checking dependencies, and documenting the entire workflow. This Skill automates that end-to-end audit, identifies gaps, and guides you through commits and verification steps until your app meets production standards.

Yes. Pest handles unit and feature testing for your backend logic, while Playwright runs UI tests on your frontend. This Skill orchestrates both testing frameworks to verify your full-stack Laravel app comprehensively, ensuring backend functionality and user-facing behavior work correctly before production.

A production-readiness audit inventories your codebase structure, dependencies, and existing tests; flags missing test coverage; checks for documentation and version-control discipline; and verifies end-to-end workflows. This Skill generates a task plan documenting each gap and the steps needed to resolve them.

This Skill runs an automated workflow that executes Pest tests, Playwright UI tests, and codebase analysis in sequence, then generates a task manager plan. You follow step-by-step commit guidance to address gaps identified in the audit, with continuous verification until your app reaches production-ready status.

This Skill applies to full-stack Laravel/PHP applications and frontend stacks. For frontend-only projects, Playwright UI tests and frontend-specific analysis run; for full-stack apps, both backend Pest testing and frontend Playwright tests execute together to verify the entire application.