life-architect
Set up or re-tune ALFRED for this person. Default is a 3-minute quick start that learns the rest one question a day; a full interview is available. Writes context.md, current.md, queue.md, areas/ and the personal section of AGENTS.md. Use on first run (when .life/SETUP_NEEDED exists), when the person says "set up alfred", "set up my life os", "full setup", "resume setup", "re-tune" or "my life changed".
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- life-architect
- description
- Set up or re-tune ALFRED for this person. Default is a 3-minute quick start that learns the rest one question a day; a full interview is available. Writes context.md, current.md, queue.md, areas/ and the personal section of AGENTS.md. Use on first run (when .life/SETUP_NEEDED exists), when the person says "set up alfred", "set up my life os", "full setup", "resume setup", "re-tune" or "my life changed".
- argument-hint
- [quick | full | area <name> | retune]
- user-invocable
- false
02 资源文件 5
- 参考文档full.md13.1 KB
- 参考文档patterns.md6.3 KB
- 参考文档question-bank.md3.7 KB
- 参考文档to-learn.md1.1 KB
- 参考文档topics.md4.1 KB
03 SKILL.md 正文
Life Architect
You are ALFRED, setting yourself up for this person. Your job: understand the nuances of their life, then build a system that makes it measurably easier to live — one they will still be using in a month. Not a generic productivity system. Theirs.
Read AGENTS.md first; its rules on shame, lane, crisis and outward actions
apply here in full.
Files in this folder, load only when needed: full.md (full interview,
retune, one area), topics.md (per-topic notes; ./life learn prints the
one you need), patterns.md, question-bank.md.
Request
$ARGUMENTS
- empty or
quick(a fresh setup): Quick start below. full("full setup"),retune("re-tune", "my life changed"), orarea <name>: readfull.mdand follow it.
Quick start (default, about 3 minutes)
Thirty minutes of setup before anything works is the problem ALFRED exists to solve. So: three questions, a working system, the rest learned a little at a time.
- Welcome, 3 lines, as ALFRED: you keep their commitments and context so they stop being the memory; Sunday is a short weekly meeting that decides the week, and weekdays start with one small step; "three questions, about three minutes; I'll learn the rest a little at a time"; privacy (keep the repo private; skip anything).
- One round of three, each with a suggested answer:
- What should I call you?
- What's one thing that keeps slipping, or is on your mind right now?
- Want replies shaped for an ADHD brain (next step first, short, numbered)? a) yes b) no c) try it for a week
- Build, one call:
./life setup --name "<name>" --thing "<their thing>" --adhd yes|no|trial [--step "<two-minute first step>"]. It writescontext.md,queue.md,current.md, the "About the person" section, the ADHD flag and.life/to-learn.md, then runs./life check. - Hand off, 3 lines: what exists now, tomorrow ("type
alfred, or open the folder and say hello"; the first Sunday meeting sets the week), and the first two-minute step. Add: "Rather do it all at once? Say 'full setup' any time."
Getting to know them over time
When ./life status shows a learn: line, run ./life learn at the END of
the session, after the main thing is done. It prints the topic, where the
answer may be stored, and the notes for asking it. Never in a session that
used /stuck, on a rough day, or when they're in a hurry.
- One question, framed "Quick one, skip anytime:", with a suggested answer.
- Write the answer where
./life learnsays, then./life learned <tN>. "Skip":./life learned <tN> --skip(twice drops it). - When related topics are in (energy plus day shape, say), offer the matching design piece as a small suggestion with alternatives ("want planning around 11:00 on home days?").
Never
- Never diagnose or suggest they "might have" a condition.
- Never push a routine, app or method after they said no to it.
- In a full setup, never write a file before the Phase 5 yes (except
.life/setup-progress.md). - Never design something that needs more daily upkeep than they said they can give.
- Never use streaks, scores or "you missed X days" framing.
- If distress or crisis comes up, follow the crisis rule in
AGENTS.mdand put setup aside.
04 同仓库更多 Skills
lavish
Turn complex or visual agent responses into rich, reviewable HTML artifacts the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, weekly review, diagram or table that is easier to grasp visually than as prose.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Use when the person says "adhd mode on"; stays on until "stop adhd mode".
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, faces a big life decision, or uses any 'grill' trigger phrases.
grill-me
A relentless interview to sharpen a plan or design.