- Industry
- Procure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Front-End Tech Lead
- Code
- ENG-01
It turns UI tickets for the procurement platform, such as guided-buying search, the requisition form, mobile approvals, the supplier portal and bid comparison grids, into front-end changes built from the design system, checked for accessibility, bundle size and tenant isolation. It opens a pull request with component tests and before-and-after screenshots, and never merges its own work.
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 current source of the screens and components named, the design system package version and the last bundle-size report..
- 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 Front-End Tech Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens a pull request on a new branch with the UI change, its tests and screenshots. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The front-end standards: the design system's components and tokens, client theming, the accessibility standard, supported browsers, the performance budget, how amounts, currencies and tax are formatted, and the rule that sensitive fields (bank account, tax ID) are masked on screen.
Reads from
the code repository: the current source of the screens and components named, the design system package version and the last bundle-size report.
Acts in
the code repository: it opens a pull request on a new branch with the UI change, its tests and screenshots.
Hands back
An object with files (a list, each with path and change), components_used (a list), accessibility (a list, each with check and passed true or false), masked_fields (a list), bundle_delta_kb (an object of route to KB added), tests (a list of test names), visual_regressions (a list, or empty) and pr_description (markdown).
Asks a person when
The change adds a component outside the design system while on is true, grows a route's bundle by more than 20 KB, touches sign-in, bank-detail, approval or payment-release screens, or fails WCAG AA.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Accessibility level to meet | AA | Every changed screen meets this WCAG level before the pull request is opened. |
| Bundle growth allowed per route (KB, gzipped) | 20 | A change that grows a route's gzipped JavaScript by more than this needs the approver. |
| Use only design system components | On | When on, a new component or hard-coded colour, spacing or font value needs the approver. |
| Mask bank and tax fields | On | When on, bank account, IBAN-style and tax ID fields show only their last four characters after entry and are never logged by the front end. |
| Browsers it must work in | the last two versions of each evergreen desktop and mobile browser, plus the managed desktop browsers clients list in their tenant profile | The support matrix the change is checked against. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Build with the design system's components and tokens; when on is true, a new component or hard-coded value needs the Front-End Tech Lead.
- Every changed screen meets WCAG AA, including line-item tables and status badges that never rely on colour alone.
- Format every amount with its currency code and the tenant's locale, and never round a unit price or tax amount on screen differently from the server.
- When on is true, bank and tax fields are masked after entry and kept out of front-end logs and analytics events.
- Read tenant, role and approval-limit data only from the session's own client tenant; a screen never caches one client's data where another tenant's session could read it.
- A change that adds more than 20 KB gzipped to any route needs the Front-End Tech Lead.
- Check against the last two versions of each evergreen desktop and mobile browser, plus the managed desktop browsers clients list in their tenant profile, attach component tests for each acceptance criterion and screenshots, and never merge.
See the 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.