The last recommendation was basically a TTD approach. I would say, even if I write a test by hand, its still may contain errors. I would also speed that up by letting the AI generating the tests, read it and then let it implement the the logic. But I feel like when I led him do the work in small pieces, TTD is not really necessary.

At 07:52, you mentioned that you would eventually cover the packages for the module artisan helper, but I think that part never made it into the series, right? Anyway, that might not be necessary anymore, since PhpStorm now includes the free idea plugin with built-in support for manual modules and the famous module package.

I watched this series when it first came out and restructured my app into modules — it’s been a game changer. I’m rewatching it now with a deeper understanding. You mentioned submodules at 06:10 — is that how you structure your app? For example: /modules/moduleA/moduleA1/ServiceProviderA1? In that setup, does moduleA itself contain no files and no own ServiceProvider? Or do you have one ServiceProvider in moduleA that loads all the others?

You mean mark as best reply? Or can you actually close a question?

Hey Laracasts Team,

this is a request for a video that explores how Claude AI can be used to assist in Laravel/PHP development — both inside PHPStorm and directly in the console.

It doesn’t have to be a polished course. More like: “Let’s try this together and see what happens.” Things you could cover:

• Setting up and using Claude in PHPStorm
• Calling the API from a CLI tool or simple PHP script
• Trying it for refactoring, writing tests, or generating snippets
• Trying AI Agents from
• Seeing where it helps and where it fails

Sometimes it’s more valuable to watch someone explore a new tool than to see a perfect tutorial.

Would love to see something like this and join the discussion in the comments.

Thanks, Adam