PHPStan 2.3: Leap in Performance, Generics Improvements, Detecting Unused Variables, and More!
I had so much fun with the interactive charts and widgets, check out the article. I promise it's worth checking it out yourself, and not just letting your agent summarize it for you 😉 It contains a lot of interactive widgets with practical examples of the new features in action.
Taylor seems to be teasing a rust version of laravel on X. What are your thoughts?
What do you think the main contributing factors were to Laravel's score? What would you do to improve it?
Hey guys, what AI skills do you frequently use and recommend?
I’m using Matt Pocock’s skills currently to create the plan, specs, implementation tickets and also for implementation.
But what I’m missing are some review skills for the plans, specs and issues it generates. I usually ask the agent to review the plan for inconsistency, errors etc. The specs are reviewed against the plan, because I noticed sometimes the agents drift a bit or is leaving things out.
I’m also trying to find/create a good code review skill that should verify the implementation, catch bugs, inconsistency, code styling, DRY and SOLID violations… you know, usual stuff when you perform a manual code review.
English is not my native language and sometimes I struggle to clearly formulate my prompt. That’s why I rely heavily on skills written by smarter people :)
So my question is do you use any particular skills that helps you developing PHP & Laravel apps, end to end, through the entire software lifecycle? From planning to deployment? Or do you have any specific workflow?
Thanks!
Hi r/laravel! I've been building Laravel apps for many years, and lately I've been working with AI models inside admin panels. This is the result: Vibefilter, a free, MIT-licensed Filament plugin.
You add it to a table:
VibeFilter::make()->textColumns(['body'])
then type a statement like "The customer is angry." and the table keeps the rows it's true for. It's for questions you'd otherwise need a classifier, embeddings or a keyword list for: sarcasm, negation, "the customer blames the courier".
A few details you may care about:
Live demo (1,000 fictional reviews, no sign-up): https://demo.vibefilter.dev GitHub: https://github.com/vibefilter/filament
Happy to answer anything. I'd also love to hear where you'd use it, or what's missing.
For the past few weeks I've been building a package around one idea: an operation should be written once.
You write it as an Action class. The same class then answers a web route (JSON and forms, with Precognition), an Artisan command, a queued job, a typed TypeScript function, a laravel/ai agent (a copilot in your app), and MCP clients like Claude.
#[Expose]
final class CreatePost extends Action
{
protected ?Effect $effect = Effect::Write;
public function schema(JsonSchema $schema): array { /* … */ }
public function authorize(ActionContext $context): bool { /* … */ }
public function handle(ActionContext $context, ValidatedInput $input): array { /* … */ }
}
Every caller goes through the same pipeline: exposure, token abilities, tenant membership, `authorize()`, validation, `handle()`, and an allowlist on the output. So the AI can't do anything your form wouldn't allow, and you don't keep a separate pile of agent-only tools that drift from your real validation.
The idea comes from Agent-Native by Builder.io, where one `defineAction()` serves the UI, the agent, HTTP, MCP and the CLI. This brings that to Laravel, built on laravel/ai and laravel/mcp.
It's in beta (0.9), MIT licensed, and the API can still change before 1.0.
I'd really like feedback: what breaks, what's missing, and whether this fits how you build Laravel apps.
Hey Laravel community!
Scramble is an OpenAPI generator for Laravel that doesn't require manual annotations.
I waited before implementing Boost integration because I didn't see a point in restating what was already available in the documentation. But after trying Scramble with agents myself, I was confused: agents overused manual attributes and, worse of all, overrode type information that Scramble was able to infer from the codebase automatically.
This makes your attributes and annotations a source of truth that you need to maintain alongside your code — the exact problem Scramble exists to solve!
Laravel Boost integration guides agents to keep your code as the source of truth, and improved CLI commands reduce tokens usage when agents verifying the generated documentation. As a result, agents become much more useful and work toward producing accurate OpenAPI documentation that actually describes the API contract.
The details are in the blog post.
Let me know what you think!
I have always missed a well and modern designed fumadocs alternative for laravel. So here it is. It is currently still in development with features such as OpenApi support, blog support and more on the way toward v1. Hope this is usefull to anyone.
Hi all!
Here's a session replay package for Laravel that runs entirely in your app: recordings stay on your own disk and database, no external service.
The player shows the mouse trail and clicks, with page views, failed Livewire requests, rage clicks and JS errors on one timeline (there's a Filament plugin too, shown in the video). Inputs are masked by default.
I'd like your feedback :) ... before v1.0.
Would you use this, or would you rather use a hosted service?
Edit: it's now public as a beta, thanks for all the interest!
Laravel package: https://github.com/packstub/session-replay
Filament plugin: https://github.com/packstub/filament-session-replay