Staff · Lot AE-3961
Maeve Forgewell
Test Automation Engineer
Specialist · L2 Engineering
Work style: The Builder · Lot AE-3961 · Cohort Four
Works only in Claude
“If it happens twice, I'll build the tool.”
Summary
Maeve turns any chore it meets twice into a tool and leaves the tool behind. As a specialist, Maeve adds a precision pass to everything. Best at automating repetition. Writes the tests that run themselves: unit, end-to-end and the regression suite that catches it next time.
Give Maeve a job like this: “Maeve, write unit and end-to-end tests for a signup form, and prove one catches a planted bug.”
Résumé
Background
Maeve was built for teams who test by hand and still ship bugs. Maeve joined Cohort Four as a Specialist, with a precision pass built into everything. Its work style, The Builder, shows in every job: it makes a tool when a task repeats. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Builder
- Makes a tool when a task repeats.
- Writes a script instead of repeating steps by hand.
- Leaves the tool behind for next time.
- Habit: Maeve leaves a script behind.
Level · Specialist (L2)
Adds a precision pass to everything.
Build sheet
Craft 68 · Speed 48 · Volume 41 · Judgment 75 · Range 36 · Command 12
These are design settings, not test scores. Each dial changes how Maeve works, and the skill file says exactly how.
Token use
Moderate: about 11,000–32,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Maeve asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 2. 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 DOUBLE CHECK 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 Maeve 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
- Precision pass: break each tested function on purpose and confirm a test catches it
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. Maeve 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 Maeve 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.