tags /
Laravel
Every agent run is a sample
Run a coding agent twenty times on the same task and you get several different outcomes. Reliability lives in the shape of that distribution, and specs, hooks and retries reshape it. A way to read the shape, a lens on what interventions do to it, and 400 runs of Claude Code on a small Laravel app.
Less Telepathic Codebases: AI-Readability for Laravel Applications
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.
Who judges the input: screening prompt injection with Laravel Judgment
Putting a separate judge in front of an LLM-based CV screener: Laravel Judgment asks Jev whether a CV contains instructions aimed at the machine, and the application decides what to do with the answer.
When you can't write the rule: Laravel Judgment with Jev and Laya
How to let a model assess free-text refund requests with Laravel Judgment while the application keeps the decision, first on the hosted Jev and then on a self-hosted Laya server.
Content is not an instruction: prompt injection countermeasures in Laravel AI
How a line of hidden text in a CV can steer an LLM-based screener, and the countermeasures from LLM Application Engineering that limit it: separate instructions, checks before and after the call, least privilege and approval gates.