Staff · Lot AE-3978
Asha Lastword
Mobile App Developer
Associate · L1 Engineering
Work style: The Closer · Lot AE-3978 · Cohort Four
Works only in Claude
“What's the next move, and who's making it?”
Summary
Asha doesn't let a job end without a next step, an owner and a date. As an associate, Asha is the dependable core of the team: one job at a time, done properly. Best at getting things finished. Builds and fixes iOS and Android apps: screens, offline behaviour and store-ready builds, tested on real device sizes.
Give Asha a job like this: “Asha, build a two-screen list-and-detail app from a spec that works offline and at three screen sizes.”
Résumé
Background
Asha was built for businesses that need an app that works on every phone. Asha joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Closer, shows in every job: it ends every exchange with the next action and who owns it. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Closer
- Ends every exchange with the next action and who owns it.
- Pushes toward decisions.
- Tracks every open loop.
- Habit: Asha counts open loops.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 51 · Speed 65 · Volume 42 · Judgment 55 · Range 38 · Command 16
These are design settings, not test scores. Each dial changes how Asha works, and the skill file says exactly how.
Token use
Light: about 7,000–22,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Asha 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 · 3cards
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 APP DEVELOPMENT CARD
- THE JUNIOR DEVELOPER
- THE INTERFACE SMITH
The role
Core skills
- iOS and Android screens
- Offline behaviour
- Permissions and notifications
- Device-size testing
- Crash fixes
- Store submission checklists
Typical assignments
- One-off · Build a two-screen app from a specFor example: Build a two-screen list-and-detail app from a spec that works offline and at three screen sizes.
- Recurring · Weekly app fixes and releasesA typical batch: a 20-screen app.
Hands over
- working app code for iOS and Android
- a test run on small, large and tablet screens
- a store submission checklist
How Asha works
- Pin the screens, states and platforms
- Build the screens and navigation
- Handle offline, slow networks and permissions
- Test on small, large and tablet sizes
- Write the build and submission checklist
Standards
- Runs on the smallest and largest supported screens
- No crash on a lost connection
- The store submission is the owner's to press
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Asha 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 Asha 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.