An agent does better when it works from your framework version and your application's own conventions rather than from what it saw most often in training. These articles cover adding features to an existing Laravel application, stopping outdated Next.js suggestions, and whether to move a working Vue project because a tool seems better at another framework.
5 articles
Which parts of a database migration to hand an AI coding agent, which to keep, how to give it a database it is allowed to lose, and a rehearsal in which a migration passed every usual check while deleting 198…
Which Flutter work to hand to an AI agent, what to decide first, the widget tests that catch faults the analyzer missed in a small demonstration, and how to time the whole task, debugging included.
One older benchmark found models did better in React than Vue, and documentation in context moves agent results a lot. Diagnose failures, run a representative ticket in your Vue app with better context and checks, then weigh what still fails…
Read the installed Next.js version and router from the repository, give the agent the documentation bundled with that version, back it with a build, lint and a search for retired APIs, and change the rules in the same pull request…
Give the agent the application's own account of its routes, models, policies and conventions, brief the feature around the existing permission and data rules, write the forbidden-user test first and review the diff where Laravel hides behaviour.
