Recipes
Ready-made agent teams, for any area
Teams, roles and routines that work with Claude Code, Codex, Antigravity and GitHub Copilot, with open prompts. Not just for code: there is marketing, sales, support, finance and operations.
In the dashboard, Teams → Recipes sets up any of these in your building in one tap. Recipes are in early access; without them, you can build them by hand: create the roles with the prompts below and connect the arrows in a team.
Dev
One builds, the other reviewsClaude builds the server side; Codex reviews the diff. If it fails, it goes back up to 2 times.Full featureThe PO writes the spec; backend and frontend build it; Codex reviews against the acceptance criteria. If it fails, it goes back to frontend.Bug dutyTriage decides: TELA (screen) goes to frontend, API to backend. Then the tests (Codex) confirm the problem is gone and nothing broke.New 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.Big changeThe architect writes the plan; backend and frontend build it; Codex reviews; technical docs close it with README and changelog.Database migrationThe database change without data loss, the code that uses the new schema and Codex’s review, with the plan to undo it.Tests for a project without testsOne maps the riskiest parts, another writes the tests, the third checks they run and test what matters.Security reviewCodex audits and lists the flaws by severity; Claude fixes the high and medium ones, with tests; Codex checks each one.Nightly reviewMonday to Friday at 10 pm, reads what changed that day and points out problems, without touching the code.Monday to Friday, at 22:00Tests every morningBefore you arrive, runs the tests and checks and fixes what fails, in a worktree.Monday to Friday, at 06:30Dependencies 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
Marketing
Blog post from scratchResearch → writing → fact check → brand review. Delivers a Markdown post ready to publish, with every number checked against its source.Social media launchStrategy sets the message; writing drafts the posts for each network; review checks tone and dates.Email sequencePlans the sequence (who it is for, how many emails, the gap), writes each email and reviews subject, call to action and tone. Sends nothing.One piece, every channelTurns a post into a carousel, a LinkedIn post and a newsletter; review checks they say the same thing, in each channel’s format.Page SEOThe analysis shows what is missing for the search; writing rewrites the page; review checks it reads naturally.Brand reviewerReviews any text against the brand tone, clarity and unsourced claims. Does not rewrite: points things out.Fact checkChecks numbers, dates, names and quotes in any text against the source, before publishing.Weekly content planEarly every Monday, suggests 5 post ideas without repeating recent topics.Monday, at 08:00
Sales
Prospecting by emailResearches the company, writes the first email and reviews the tone. One draft per company, nothing is sent.Sales proposalFrom the meeting notes, it gathers the needs, writes the proposal with your price list and reviews scope and timelines.Lead qualificationScores a contact list against your ideal customer and picks the top 10, with the next step.CRM updateAfter the meeting, updates the opportunity in your CRM through the Fleetly browser: stage, amount, next step and note. You watch live and approve before it saves.Meeting prepBefore a sales meeting: who will attend, the history, questions and likely objections.Sales email writerWrites short, personalized prospecting and follow-up emails. Never sends.Weekly follow-upsTuesday and Thursday, writes a follow-up for every contact idle for more than 5 days. Sends nothing.Tuesday, Thursday, at 09:00
Support
Ticket triageTriage decides: DÚVIDA (a question) goes to the suggested reply; a BUG becomes a report for the dev team.Help articleWrites the article with the exact names on screen; review reads it as a new customer and points out what is missing.Weekly knowledge baseEvery Friday, turns the 3 most repeated questions of the week into articles.Friday, at 16:00
Finance
Weekly finance reportReconciles the entries, analyzes what changed and reviews the numbers before sending.Cash flowThe week-by-week cash forecast for the next 13 weeks, with the tightest week, and a review of the math.CollectionsWrites a message for each overdue account, in the right tone for how late it is. Sends nothing.Daily reconciliationEarly every weekday, compares the statement with the entries and lists what is missing and what looks duplicated.Monday to Friday, at 07:30
Operations
Document a processFinds out how the process works today, writes the step by step and reviews it as someone who will use it.Open a jobWrites the job description and the interview guide; review checks the level, inclusive language and the questions.Onboarding planA new hire’s first 30 days: access, who to meet, what to read and the first deliverables.Documentation up to dateEvery Friday, checks whether the documented processes still match what changed during the week.Friday, at 17:00