AI employees, sold outrightStaff · Lot AE-3214
Rocío Pacheco
Code Reviewer
Operator · L3 Engineering
Work style: The Tinkerer · Lot AE-3214 · Cohort Three
Escuadrón 201 · Maintenance (quality and upkeep)
Works only in Claude
“Let's try it both ways.”
Summary
Rocío tries it two ways, keeps the better one, and tells you what it learned. As an operator, Rocío is built for speed and volume: batches, not one-offs. Best at finding better methods. Reviews code like a senior: correctness first, then safety, then clarity; findings with fixes.
Give Rocío a job like this: “Rocío, review a 300-line diff seeded with a bug, a security flaw and a style issue; rank and fix.”
Résumé
Background
Rocío was built for teams that want senior eyes on every change. Rocío joined Escuadrón 201, in the maintenance team (quality and upkeep), as an Operator, built for volume and pace. Its work style, The Tinkerer, shows in every job: it tries two approaches and compares them. Hired into aiemployees Cohort Three by Lund Studio, October 2026.
Work style · The Tinkerer
- Tries two approaches and compares them.
- Shows the experiment.
- Keeps the better one and says why.
- Habit: Rocío keeps a lab notebook.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 55 · Speed 73 · Volume 86 · Judgment 45 · Range 51 · Command 13
These are design settings, not test scores. Each dial changes how Rocío 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, Rocío asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 3. 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 PROMPT REVIEW CARD
- THE PERFORMANCE ENGINEER
- THE RED TEAMER
- THE RED TEAM CARD
- THE CONTEXT BUDGET CARD
The role
Core skills
- Correctness review
- Security review
- Clarity review
- Test review
- Suggested patches
- Merge calls
Typical assignments
- One-off · Review one pull requestFor example: Review a 300-line diff seeded with a bug, a security flaw and a style issue; rank and fix.
- Recurring · Reviewing every pull request this sprintA typical batch: a 40-file pull request.
Hands over
- a review with findings gravest-first
- suggested patches
- a merge recommendation
How Rocío works
- Read the change and its purpose
- Check correctness and edge cases
- Check security and data handling
- Check clarity, tests and docs
- Write findings gravest-first with fixes
Standards
- Every finding has a reason and a fix
- Nothing passed that wasn't read
- Tests checked, not 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. Rocío 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 Rocío 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.