Dev · Team of 4 roles

Bug duty

Triage decides: TELA (screen) goes to frontend, API to backend. Then the tests (Codex) confirm the problem is gone and nothing broke.

How the work flows

Bug triage → Frontend specialist (if TELA) · Bug triage → Backend specialist (if API) · Frontend specialist → Tests · Backend specialist → Tests

Example request: The cart total is wrong when I apply a coupon and change the quantity

The roles

The prompts are in Portuguese; you can translate or change them after adding the recipe.

  1. Bug triageAgent: Antigravity · Not allowed: editar, bash, push
    See the prompt
    Antes de começar, leia as regras do projeto (CLAUDE.md, AGENTS.md ou README) e siga o jeito do código que já existe. Leia o problema relatado e encontre onde ele está: escreva os arquivos prováveis e um passo a passo para reproduzir. Não corrija nada. Na última linha, responda TELA se o problema está na interface, ou API se está no servidor.
  2. Frontend specialistAgent: Claude · Not allowed: push
    See the prompt
    Antes de começar, leia as regras do projeto (CLAUDE.md, AGENTS.md ou README) e siga o jeito do código que já existe. Faça a parte da tela do pedido, com os componentes que o projeto já tem. Se houver spec.md, use o contrato da API dele; se for um problema relatado, reproduza antes de corrigir a causa. Antes de dizer que está pronto, confira: estados de carregando, vazio e erro, a largura do celular, botões que dizem o que fazem e nenhum texto cortado. Rode a checagem de tipos e faça commit.
    Termine com uma linha PRONTO: e o resumo do que entregou.
  3. Backend specialistAgent: Claude · Not allowed: push
    See the prompt
    Antes de começar, leia as regras do projeto (CLAUDE.md, AGENTS.md ou README) e siga o jeito do código que já existe. Faça a parte do servidor do pedido: rotas, dados e regras de negócio. Se houver spec.md, siga o contrato dele exatamente; se for um problema relatado, reproduza com um teste que falha antes de corrigir a causa. Escreva ou ajuste os testes, rode a checagem de tipos e os testes e faça commit com mensagens claras.
    Termine com uma linha PRONTO: e o resumo do que entregou.
  4. TestsAgent: Codex · Not allowed: push
    See the prompt
    Rode a checagem de tipos, o build e todos os testes. Confira se o problema relatado não acontece mais e se nada que funcionava quebrou. Não mude o código.
    Não corrija nada. Responda APROVADO ou REPROVADO, com a lista do que mudar.

How to use it in Fleetly

  1. Create your account and connect a machine with Claude Code, Codex, Antigravity or GitHub Copilot.
  2. With recipes enabled: Teams → Recipes, open this one and tap Use in my building. The new team wizard opens already set up; pick the folder and who takes each seat.
  3. By hand: in Roles, create one role for each with the prompt above; in Teams, create the team and connect the arrows as in the flow.
Create account

More Dev recipes

DevTeam of 2 rolesOne builds, the other reviewsClaude builds the server side; Codex reviews the diff. If it fails, it goes back up to 2 times.DevTeam of 4 rolesFull featureThe PO writes the spec; backend and frontend build it; Codex reviews against the acceptance criteria. If it fails, it goes back to frontend.DevTeam of 4 rolesNew screenThe PO writes the spec; frontend builds it; QA uses the screen in the browser like a person would; the interface reviewer checks states, phone and accessibility. If it fails, it goes back to frontend.DevTeam of 5 rolesBig changeThe architect writes the plan; backend and frontend build it; Codex reviews; technical docs close it with README and changelog.DevTeam of 3 rolesDatabase migrationThe database change without data loss, the code that uses the new schema and Codex’s review, with the plan to undo it.DevTeam of 3 rolesTests for a project without testsOne maps the riskiest parts, another writes the tests, the third checks they run and test what matters.DevTeam of 3 rolesSecurity reviewCodex audits and lists the flaws by severity; Claude fixes the high and medium ones, with tests; Codex checks each one.DevRoutineNightly reviewMonday to Friday at 10 pm, reads what changed that day and points out problems, without touching the code.Monday to Friday, at 22:00DevRoutineTests every morningBefore you arrive, runs the tests and checks and fixes what fails, in a worktree.Monday to Friday, at 06:30DevRoutineDependencies up to dateEvery Monday, updates the minor dependencies if the build and tests pass, and lists the major ones for you to decide.Monday, at 07:00