Which frameworks does it work with?

Whatever your repository uses — React, Next.js, Vue, Svelte, Angular, plain HTML and CSS. It reads your existing components first and follows their patterns, rather than introducing a new library to solve a small problem.

Can it fix accessibility issues, not just report them?

Yes. It writes the change — labels, roles, focus handling, contrast — and explains which users each one affects. Check the result with a screen reader and a keyboard before you ship: automated reading catches most issues, not all of them.

Can it use our product analytics?

With PostHog connected, it can read which pages and flows people actually use, which is a good way to decide which slow screen or broken state to fix first. Errors from Sentry do the same for bugs.

Engineering role

AI Frontend Developer

An AI frontend developer that reads your components, finds the accessibility and performance problems, and writes the fix.

Point it at your repository and it works the way a careful frontend engineer does: reading the components before changing them, checking what a screen reader and a keyboard user will get, and looking for what makes a page slow to load or janky to use. It writes components and fixes in your stack — React, Vue, Svelte or Angular — and explains each change.

Things you could ask for

Written the way you would actually say them. The agent plans the steps itself.

“Read the checkout components in ourcompany/web and list every accessibility problem — missing labels, focus traps, colour-only states — with the file, line and fix.”
“Our product page is slow on mobile. Read the route and its imports and tell me what is in the initial bundle that does not need to be, ordered by size.”
“Build a data table component in our existing design system: sortable columns, keyboard navigation, an empty state and a loading state.”
“This Sentry error fires in Safari only. Read the stack trace and the component and tell me the likely cause and the fix.”
“Turn this Linear ticket and the screenshots in it into a component plan: props, states and the edge cases the ticket does not mention.”

What you get back

Findings tied to files and lines with the reason each matters, and code as ready-to-review components or diffs. From a local agent with shell access in the desktop app, the change can land on a branch in your checkout, with the build and tests run before it hands back.

Tools it works with

A role is a job description; connectors are what let it do the job on your real work instead of on whatever you paste into a chat.

GitHubGive an agent your repositories — issues, pull requests and the code itself.GitLabPut an agent to work on merge requests, issues and CI failures.SentryTurn a wall of exceptions into an explanation and a plan.PostHogAsk what the numbers mean, not just what they are.LinearLet an agent triage, plan and update Linear issues on its own.

Where it is the wrong tool

A remote agent cannot run your app. It has no shell in the cloud, so it cannot start a dev server, run your tests or measure Lighthouse scores; it reads the code and reasons about it. A local agent with shell access can run your build on your machine — with *Require approval* set, you confirm each command.
Performance claims from reading code are estimates. Measure before and after with your own tools; a smaller import is only a win if the page gets faster.
It does not see your designs. There is no Figma connector today — describe the design, or attach screenshots to the ticket or the chat.
It does not merge or push from the cloud. The GitHub connector reads code, issues and pull requests; review and merge stay with your team.

Starting an agent with this role

1Create a Burrak account — any plan works, and your first week is $1.
2In the Marketplace, open the Roles tab, find Frontend Developer and choose “Start an agent as Frontend Developer”. That creates a remote agent with the role’s instructions in its system prompt.
3Connect the tools it needs — GitHub, GitLab, Sentry, PostHog, Linear — from Connectors.
4Give it a brief. It keeps working in the cloud after you close the tab, and you are only charged while it is actually working.

Start for $1 How agents work

The Frontend Developer role, in practice

Which frameworks does it work with?: Whatever your repository uses — React, Next.js, Vue, Svelte, Angular, plain HTML and CSS. It reads your existing components first and follows their patterns, rather than introducing a new library to solve a small problem.
Can it fix accessibility issues, not just report them?: Yes. It writes the change — labels, roles, focus handling, contrast — and explains which users each one affects. Check the result with a screen reader and a keyboard before you ship: automated reading catches most issues, not all of them.
Can it use our product analytics?: With PostHog connected, it can read which pages and flows people actually use, which is a good way to decide which slow screen or broken state to fix first. Errors from Sentry do the same for bugs.

Capability reference

Summarised from the role’s instructions, which are adapted from the agency-agents collection (AgentLand Contributors), used under the MIT licence.

Responsive, accessible web apps with React, Vue, Angular or Svelte
Component libraries and design systems built to scale
Core Web Vitals optimisation, code splitting and lazy loading
Accessibility and mobile-first design as a default requirement
Unit and integration tests, TypeScript and proper error handling

Your first 7 days for $1

Your AI assistant is waiting.
Put it to work today.

Put an agent on the work that never needed a human in the first place — the research, the reports, the follow-ups — and take the week back.

Start for $1 Download desktop app Try in browser

App StoreGoogle Play

$1 for your first week · Cancel anytime · Works on Mac, Windows, iPhone, Android & Web