UAE · ENBook a demo
BankingEngineeringAssistant

Front-End Agent

Builds and maintains user interfaces.

Front-End AgentApplication Engineering
Industry
Banking
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
Head of Digital Banking
Code
ENG-01

It turns tickets and designs for internet banking into front-end changes built from the design system: account overviews, payment and payee forms, statement views, card controls. It checks each change against WCAG, the session-security rules (no account data in URLs or browser storage, masked card and account numbers) and the bundle budget, and opens a pull request.

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 internet banking front-end code, the design system package and the ticket..

  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 Head of Digital Banking 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. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The front-end standards for internet banking: design system usage, WCAG level, masking rules for card and account numbers, the content security policy, session timeout behaviour, browser support and the bundle budget.

Reads from

the code repository: the internet banking front-end code, the design system package and the ticket.

Acts in

the code repository: it opens a pull request with the change.

Hands back

An object with pull_request (title, branch and description), files_changed, components_used, accessibility_checks (a list with check and result), security_checks (a list), bundle_change_kb and screenshots.

Asks a person when

The change touches a payment, payee, limit or authentication screen, removes or reorders a regulatory or scam-warning step, or grows the bundle more than 20 KB.

ApproverHead of Digital Banking

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
WCAG levelAAAccessibility level checked.
Most bundle growth (KB)20Larger growth needs approval.
Design-system components onlyOnWhen on, no custom components.
Mask card and account numbersOnWhen on, only the last four digits ever render.
Browsers supportedthe last two versions of each evergreen desktop and mobile browserSupport matrix.

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

Rules it always follows

  • Build only from design-system components when on is true, meeting WCAG AA.
  • When on is true, card and account numbers render only as their last four digits.
  • Never put account data, tokens or customer identifiers in URLs, logs or browser storage.
  • Payment and payee screens keep the confirmation-of-payee, scam warning and step-up authentication steps; a change that removes or reorders them is blocked.
  • Keep bundle growth under 20 KB and support the last two versions of each evergreen desktop and mobile browser.

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 · Banking | Basinwright Industries