Cookbook
Choose a problem. Follow a small set of steps. Know what a correct result looks like.
Create a focused landing page
Check mobile and desktop layouts, keyboard navigation, text contrast, and the primary action.
Fix a bug without widening scope
Show the failing case before the fix, the passing case after it, and a neighboring regression check.
Audit technical SEO
Cite inspected URLs and actual rendered markup. Test fixes on staging before publication.
Improve speed with measurements
Compare before and after under the same device and network conditions; report variability.
Build a useful operations dashboard
Recalculate totals independently and test empty, zero, and invalid records.
Connect an API with failure handling
Use mocked responses for success and failure. Confirm retries are bounded and do not duplicate writes.
Plan an additive database migration
Rehearse on disposable data, compare counts and constraints, and verify restoration.
Clean a CSV without losing evidence
Reconcile row counts, explain removed records, and test malformed values using a small fixture.
Document how the project really works
Follow the documented setup in a clean environment where possible; mark unverified steps.
Understand an existing project
Confirm cited files exist; separate verified findings from unknowns.
Upgrade one dependency deliberately
Run relevant checks and affected user flows; document breaking changes and rollback.
Add a Laravel authorization policy
Test owner, non-owner, guest, and privileged roles against actual routes.
Build a transparent product page
Compare every claim to the source data; test mobile layout and prototype controls without real payments.