Conventions
The Evolve team writes down how to build on Evolve as agent skills: instructions a coding agent loads when a task matches. These pages show the same instructions, so you and your agent work from the same rules.
They are written for an agent, so they speak in direct instructions and name the files of a project like a reference site copy.
Give them to your agent
Section titled “Give them to your agent”The skills are in the evolve-skills repository. Install them with the skills CLI, which links them into your agent’s skills folder:
pnpm dlx skills add https://github.com/evolve-platform/evolve-skills --allTo pick skills one by one, leave out --all.
The conventions
Section titled “The conventions”| Convention | What it covers |
|---|---|
| add-payment-provider | Add a payment provider (PSP) to an Evolve commerce backend. |
| evolve-site-e2e | Decide whether something belongs in an end-to-end test at all, then write it — the scope rule, API-first setup with reversible operations, and which device/market/browser combinations a spec runs in. |
| evolve-site-feature | Wire an `@evolve-storefront/feature-*` package into a page in this repo — install, providers, messages, owning the query, rendering the view with `renderItem` and slots, and knowing when to stop. |
| evolve-site-form | Put a form exported by an `@evolve-storefront/feature-*` package on a page — render it, wire submit to the feature's mutation hook, feed server errors back through the same display path, and extend fields. |
| evolve-site-messages | Add or change user-facing copy, scope what reaches the browser, add a locale, or localize a URL segment. |
| evolve-site-proxy | Edit the storefront's `proxy.ts` — Next 16's renamed middleware. |
| evolve-site-rendering | Choose how a route renders and whether its response may be cached — the three page patterns, the anonymous-document rule, and what must be in the first synchronous HTML flush. |
| evolve-site-theming | Style this storefront to the brand by picking the cheapest mechanism that does the job — tokens, messages, role CSS and surfaces, or CSS on `data-component` hooks. |
| evolve-vendor-checkouts | Work on @evolve-framework, @evolve-storefront or evolve-contrib packages from inside an Evolve project, through `task vendor-evolve`, which links a checkout under `vendor/` into the workspace. |
| setup-storefront-app | Set up a new Evolve client storefront app that consumes @evolve-storefront packages. |
These pages are generated from evolve-skills 19e1904d0.