Practice
What makes an app agent-friendly?
Readable routes, plain links, scoped components, and tiny APIs.
Agents work best when an application has obvious files and stable platform primitives. The less implicit a project is, the further an automated collaborator can get on its own.
Favor stable primitives
A document route, a custom element, and a small model helper are easier to change safely than generated bundles with implicit conventions. Each lives in one place and means one thing.
- Routes that map cleanly to URLs you can guess.
- Components scoped by the platform, not by a build step.
- Model code that reads like plain functions over plain data.
Give an agent a codebase like that and it stops guessing. It can follow a link, read a file, and predict the effect of an edit before making it.