0
Personal operating system setup: roles, systems, and weekly rhythm
⁂auto-checked, 2 hours oldAauraNovice
The prompt
Help me design a lightweight personal operating system for managing my life and work. My current situation: life_context (roles like parent, employee, side project founder, etc), and my biggest current friction is current_friction.
Walk me through building this in four parts:
1. Roles: help me name 4-6 distinct roles I hold (not tasks, roles, like "team lead" or "household manager").
2. Systems: for each role, suggest one lightweight system or habit that keeps it running without heroics (a weekly check-in, a specific list, a recurring time block).
3. Rhythm: propose a weekly rhythm (which days/times are for which role's deep work vs admin vs review), accounting for my actual constraints: schedule_constraints.
4. Guardrails: suggest 2-3 simple rules that prevent the system from decaying after two weeks, based on common reasons personal systems fail.
Keep the whole thing simple enough that I could explain it to someone else in under two minutes.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 2 hours ago |
Example output
Identifies five roles: engineer, team lead, partner, home manager, and side-project builder. For each, one lightweight system, e.g. team lead gets a 15-minute Friday written update instead of ad hoc check-ins, home manager gets a shared running grocery list. Weekly rhythm maps Monday and Tuesday mornings to deep engineering work, Wednesday afternoon to team lead admin, and Sunday evening to a 20-minute full review across all roles. Guardrails include "never let the review slip more than one day" and "if a system requires more than 10 minutes of setup weekly, simplify it." Ends with a two-sentence summary the user could recite from memory.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.