From the source
They can copy your product's style, match its patterns, and try to follow its conventions.
What they cannot do is understand why those patterns exist.
Code shows agents what shipped, not why one component, phrase, or interaction became your standard.
That reasoning lives in design reviews, PR comments, Slack threads, and with the people who were in the room.
For an agent, context that isn't in the codebase doesn't exist.
Vercel is an agent-native team.
We treat accepted product decisions like code, keeping them in the repository, reviewing changes against them, and making them available to every agent working there.
The way we do this is through product-design .
It's a system with three parts: An agent skill that gives coding agents the context behind decisions that require product or codebase judgment.
Linters that enforce clear rules automatically.
A review loop that gathers evidence from Slack, Figma, and GitHub, then prepares guideline updates for review.
Any team can build the same structure around their own standards.
Copy link to heading Inside the product-design skill …
