Livewire

The Shift from Generation to Education Blindly accepting AI-generated code is a recipe for long-term maintenance debt. Suzanne Wong designed a prompt that shifts the dynamic from a passive code hand-off to an active mentorship session. By injecting a set of "learning instructions" into a developer tool like Cloud Code, you transform the AI into a rigorous tutor. The goal isn't just to produce a Filament admin panel or a PHP script; it's to ensure the human behind the keyboard can justify every technical decision made along the way. Deep Learning via Real-World Scenarios This technique moves beyond simple syntax quizzes. Instead of asking what a keyword does, the agent presents situational challenges. It might ask why a PHP enum is superior for maintaining a single source of truth or how a team should handle database migrations when renaming a status column. These questions force you to think about Eloquent casting and the broader implications of architectural choices. If you answer incorrectly, the agent slows down, explains the nuance, and re-tests the concept from a fresh angle to ensure mastery. Tracking Progress with Learning Metadata As the session progresses, the agent maintains a `learning.md` file within your project. This acts as a living document of your technical growth, capturing the reasoning behind the code and the explanations provided for tricky edge cases. It turns the ephemeral chat history into a permanent reference. While this "pedagogical overhead" increases token consumption and time—often doubling the cost of a standard generation session—the trade-off is a developer who actually understands the Livewire or Pest components they are about to deploy. Turning Instructional Prompts into Reusable Skills You don't have to copy-paste this logic every time. In Cloud Code, you can formalize these instructions by creating a specific skill, such as `quiz-me.md`. This allows you to invoke the learning mode on command. By centralizing the teaching logic, you create a consistent learning environment across different projects, ensuring that "mastery" isn't just a buzzword, but a verified part of your development workflow.