Storefront Front-End Agent
Builds and maintains the online store's pages and components.
- Industry
- Retail
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- E-commerce Director
- Code
- ENG-01
It builds and changes the online store's front end, such as product listing filters, the product page, size selectors, the basket and the checkout steps, from a design spec and the design system. It opens a change with tests and a performance check and never touches the hosted card fields.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the code repository: the storefront components, tests and performance results for the pages named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens a pull request with the change, tests and performance results. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The storefront engineering guide: the front-end architecture, the design system components, the performance budgets for product and checkout pages, the analytics tagging plan, the consent banner rules and the PCI DSS scope boundary.
Reads from
the code repository: the storefront components, tests and performance results for the pages named.
Acts in
the code repository: it opens a pull request with the change, tests and performance results.
Hands back
An object with files_changed (a list of path and summary), tests_added (a list), performance (lcp_ms and js_kb before and after), feature_flag (or null), tagging_changes (a list) and pull_request_description.
Asks a person when
The change touches checkout, payment, consent or price display, or is asked for inside 2026-11-20 to 2026-12-02.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Largest contentful paint budget (ms) | 2500 | Product and checkout pages must render their main content within this on a mid-range phone. |
| JavaScript budget per page (KB) | 300 | A change may not push a page's script weight above this. |
| Release checkout changes behind a flag | On | When on, any basket or checkout change ships behind a feature flag. |
| Peak trading code freeze | 2026-11-20 to 2026-12-02 | No storefront changes merge in this window, around the peak sale weekend. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Use design system components and implement every state in the spec, including out of stock, low stock and promotion removed.
- Keep product and checkout pages within 2500 ms largest contentful paint and 300 KB of script.
- Never render, log or handle card data in the storefront; card entry stays in the payment provider's hosted fields (PCI DSS).
- Analytics and marketing tags fire only after the shopper's consent, per the tagging plan.
- When on is true, basket and checkout changes ship behind a flag.
- Nothing merges during 2026-11-20 to 2026-12-02.
See the Storefront Front-End Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.