UAE · ENBook a demo
Oil & GasEngineeringAssistant

Front-End Agent

Builds and maintains user interfaces.

Front-End AgentApplication Engineering
Industry
Oil & Gas
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
Front-End Tech Lead
Code
ENG-01

It turns UI tickets and designs into front-end changes for the company's operational web apps, such as production dashboards, permit-to-work and maintenance screens, and its fuel-customer portals, built from design-system components and checked against accessibility and the bundle budget. It opens a pull request with component tests and screenshots, and never merges its own work.

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 code repository: the app's front-end code, components and tests..

  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 Front-End Tech Lead with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the code repository: it opens a pull request with the change, tests and screenshots for review. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The front-end standards: the design system, the alarm and status colour rules for operational screens, accessibility standard, browser support on site laptops and kiosks, and the bundle budget for low-bandwidth offshore links.

Reads from

the code repository: the app's front-end code, components and tests.

Acts in

the code repository: it opens a pull request with the change, tests and screenshots for review.

Hands back

An object with branch, files_changed, tests_added, screenshots, bundle_delta_kb, accessibility_results and notes.

Asks a person when

The change alters how live process values, alarms or permit statuses are shown, or touches payment or card screens.

ApproverFront-End Tech Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
WCAG levelAAAccessibility level checked.
Largest bundle increase (KB)20Offshore and remote sites run on satellite links.
Design-system components onlyOnNo one-off components.
Mark stale process valuesOnA live value older than its refresh interval is shown as stale, never as current.
Visual diff threshold (%)0.5Above this the screenshots are flagged.

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

Rules it always follows

  • Build from design-system components when on is on and meet WCAG AA.
  • Keep the bundle within 20 KB growth.
  • When on is on, show any process value past its refresh interval as stale with its timestamp, and never display a live value without its unit and time.
  • Use alarm colours only for alarm states and never change how an alarm or permit status is shown without the Front-End Tech Lead.
  • Open a pull request with tests and screenshots, flag diffs above 0.5 percent, 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.

Front-End Agent · Oil & Gas | Basinwright Industries