Agents,
minus the hype
This runs my studio
A handful of agents on schedules.

It touches everything

What it keeps current
My expense agent tracks subscriptions and posts a monthly summary.
It’s simpler than you’re picturing
What an agent actually is
Who it is
what it cares about
Instructions
how to do its job
A schedule
when it runs
Boring on purpose
It’s just plain text
What an agent reads
CLAUDE.mdthe context
project-status.mdhow to do one job
Same pattern, every agent
| Agent | Role | Runs |
|---|---|---|
| master | Orchestrator, weekly maintenance | Weekdays |
| admin | Runway, invoicing, pipeline triage | Friday |
| project | Per-project status + backlog | Monday |
| content | Scouts content ideas | Monday |
| comms | Drafts client comms | On demand |
My master agent
Just a markdown file, a role and a to-do list.
Rules, not autonomy
I make the calls, the agent just follows the rules
Most of the hype sells
complexity you don’t need
It started as three files
who-i-am.mdmy-company.mdvalues.md

Where it’s going

Alto
my internal cockpit

Aloft
a live window for clients
Agents are simpler than the hype
Automate one job, then build yours
Thank you
aline.noin/linehjartarson