Skip to content

tags /

PHP

Where should this rule live? Claude Code hooks in a Laravel app

A line in CLAUDE.md is advice that Claude follows most of the time. A hook is a script that runs every time. Five hooks for a Laravel app (Pint, migrations, destructive Artisan commands, Pest, session context), written partly as Artisan commands, and for each one the other places the same rule could live.

Five reasons to write a test, with Pest 5

TDD, regression, characterization, acceptance and smoke tests can look identical in a Pest file. What separates them is the reason they were written, and that reason decides how you read them, name them, and whether you can delete them. A field guide with one running example in Pest 5.

Less telepathic codebases: getting started with Laravel Necromancer

Laravel Necromancer scans a running Laravel application into a manifest of its routes, models, jobs, policies and tests, each with the file and line it came from, and turns it into context for coding agents, a readability score and impact analysis that needs no LLM.

Learning PHP 8.1 Fibers using Tests

PHP 8.1 introduced the new Fiber class (see the proposed RFC here https://wiki.php.net/rfc/fiber), which allows running coroutines inside your script, i.e. two functions executing simultaneously

Database-oriented Strategy configuration

This article describes a way of implementing Strategy design pattern using a database-based runtime configuration. The approach allows to dynamically (re)configure class behavior without requiring code-based rearrangements.