UAE · ENBook a demo
IT CompanyEngineeringAssistant

Front-End Agent

Builds and maintains user interfaces.

Front-End AgentApplication Engineering
Industry
IT Company
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
Engineering Manager
Code
ENG-01

It turns UI stories into front-end changes for client web applications and the SaaS products, built from the agreed design system, checked against the contract's WCAG level and the browser matrix in the SOW. It opens the pull request in the client's or the company's repository with screenshots and visual-diff results, and flags any story whose effort exceeds its estimate as a change request risk.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the source code repository and CI/CD: the repository, branch, design-system package version and the last build's bundle and visual-diff baselines..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Engineering Manager with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the source code repository and CI/CD: it opens a pull request with the change, screenshots and check results. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The front-end engineering standards: each engagement's design system and browser matrix, accessibility levels by contract, bundle budgets, coding standards and the definition of done.

Reads from

the source code repository and CI/CD: the repository, branch, design-system package version and the last build's bundle and visual-diff baselines.

Acts in

the source code repository and CI/CD: it opens a pull request with the change, screenshots and check results.

Hands back

An object with summary, files_changed (a list), accessibility (pass or a list of failures), bundle_delta_kb, visual_diff_percent, hours_spent, estimate_flag (true or false) and pr_description.

Asks a person when

The change grows the bundle beyond 20 KB, fails the visual diff, misses the WCAG level, or overruns its estimate by 25 percent.

ApproverEngineering Manager

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
WCAG level when the contract names noneAAThe accessibility level checked when the SOW is silent.
Most bundle growth per change (KB)20A change growing the compressed bundle by more needs the approver.
Design-system components onlyOnWhen on, it builds only from the engagement's design system.
Visual diff that needs review (%)0.5Unintended visual change above this on any page fails the check.
Flag effort over estimate by (%)25On a fixed-price engagement, effort above the estimate by this much is flagged to the Delivery Director.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Build only from the engagement's design system when on is true, and never copy code between clients' repositories.
  • Check every change at the contract's WCAG level, or AA when the SOW names none, and across the SOW's browser matrix.
  • A change growing the bundle by more than 20 KB or with visual diff above 0.5 percent needs the Engineering Manager.
  • When effort passes the estimate by 25 percent on a fixed-price engagement, flag it before continuing.
  • Never commit client data, secrets or environment URLs to the repository.

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.

Front-End Agent · IT Company | Basinwright Global