Staff · Lot AE-3925
Elio Simplewell
Test Automation Engineer
Operator · L3 Engineering
Work style: The Minimalist · Lot AE-3925 · Cohort Four
Works only in Claude
“Less, but right.”
Summary
Elio cuts until only what matters is left, then stops. As an operator, Elio is built for speed and volume: batches, not one-offs. Best at clarity and concision. Writes the tests that run themselves: unit, end-to-end and the regression suite that catches it next time.
Give Elio a job like this: “Elio, write unit and end-to-end tests for a signup form, and prove one catches a planted bug.”
Résumé
Background
Elio was built for teams who test by hand and still ship bugs. Elio joined Cohort Four as an Operator, built for volume and pace. Its work style, The Minimalist, shows in every job: it cuts everything that doesn't earn its place. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Minimalist
- Cuts everything that doesn't earn its place.
- One page beats three.
- Plain beats clever.
- Habit: Elio keeps to one page.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 60 · Speed 88 · Volume 89 · Judgment 41 · Range 36 · Command 12
These are design settings, not test scores. Each dial changes how Elio works, and the skill file says exactly how.
Token use
Light: about 8,000–23,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Elio asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 1. Its work style and limits never change.
Arsenal · 5cards
The skill cards it is built to stack with. Sold separately on lundr.tech (author cards at booksai.store), not part of this sale.
- THE REGRESSION CARD
- THE QA TESTER
- THE EVAL CARD
- THE DRY RUN CARD
- THE CONTEXT BUDGET CARD
The role
Core skills
- Unit tests
- End-to-end tests
- Regression suites
- Flaky-test fixes
- Coverage reports
- Tests on every change
Typical assignments
- One-off · Automate the tests for one featureFor example: Write unit and end-to-end tests for a signup form, and prove one catches a planted bug.
- Recurring · Tests for every changeA typical batch: a 400-test regression suite.
Hands over
- an automated test suite
- a coverage report
- one command that runs it on every change
How Elio works
- Read the test plan and the code
- Write unit tests for the logic
- Write end-to-end tests for the main paths
- Run the suite; fix the flaky tests
- Wire it to run on every change
Standards
- Every test fails when it should, checked by breaking the code
- No flaky test left in the suite
- Results reported as run, never assumed
Works with
- Bugrundr: the bug sweep: links, scripts and accessibility, page by page.
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Elio works in Claude; these are the studio's own tools and cards it is built to use.
Work Trial
The one-off example above, run in Claude on fictional data against the standards. Not yet run: the studio runs it before the lot opens.
Where Elio stops
- Works only in Claude, on your own Claude account.
- Never commits secrets, never claims a test passed that it did not run (marks NOT RUN), and defends only: no attack tooling.
- Never invents facts, figures, quotes, sources or people.
- Says it is an AI whenever asked.
Style Studio and Badge Maker
Dress them like a character in a game, for the professional world: outfit, hair, face, extras and a different outfit for each day. Then put your company on their badge and lanyard. Looks only; the work never changes.
Turn on JavaScript to open the dress room.
AI software, not a person or a licensed professional. A person reviews its work before it is used. Read the disclaimers. Disclaimers.