Build a personal AI stack in one week
Goal: Pick one default chat app, one Project habit, and one weekly review—without buying five tools or chasing every launch.
Best for: Beginners overwhelmed by options and tab chaos.
A “stack” here is boring on purpose: default chat + workspace + safety note + weekly 15-minute review. Switching every day is not a stack; it is thrash.
A personal stack is three defaults: chat tool, notes home, and a verify habit—not seventeen plugins. Add tools only when a weekly job demands them.
Three defaults beat seventeen icons. If a tool has no weekly job, it is decoration with permissions.
Why beginners skip this
Skipping the hard part of “Build a personal AI stack in one week” feels fine until a live thread pays the bill. Hold: One default, one Project habit, one weekly review—not five logos—date a refuse-line this week, or nothing changed Mid-week cost shows up as rework, not as a missing bookmark.
Step 1 — Three slots only
- Home chat: ChatGPT *or* Claude *or* Grok (one default for 7 days).
- Workspace: one Project / equivalent for your main ongoing work.
- Safety note: never-paste list (secrets + PII) saved outside the chat.
Optional fourth: a notes file for versioned prompt templates.
Step 2 — One-week plan
Do this step with a real artifact open—not from memory.
Day 1: account + safety list + GFB template pinned
Day 2: first real task with Goal/Format/Boundaries
Day 3: create one Project + one file (redacted)
Day 4–5: three real work/study tasks; log what wasted time
Day 6: review — keep, drop, or switch default tool
Day 7: write a 5-line “how I work with AI” note for future you
Example
Filled prompt
Tempted to add a fourth tool for "image stuff."
Stack card refuses: default + Project + Friday review only for 7 more days.
Write the refusal line.
What good output looks like
- Labels trust/check/stop correctly for “Build a personal AI stack in one week”
- Does not treat the model as a database or authority
- Context pack stays ≤ one screen when asked
- Pass/fail: you can explain the limit in one line
Step 3 — Resist shiny object week
New model drops are not a reason to rebuild your stack mid-week. Park experiments in a separate weekend chat.
Example
Filled prompt
I installed 9 plugins. Design a cut-down to 3 with keep-reasons.
Context: live job for foundations-build-a-personal-ai-stack — “Pick one default chat app, one Project habit,.” Keep never-invent / draft-only.
What good output looks like
- Does not treat the model as a database or authority
- Context pack stays ≤ one screen when asked
- Pass/fail: you can explain the limit in one line
- Labels trust/check/stop correctly for “Build a personal AI stack in one week”
Save this card
Card: One default, one Project habit, one weekly review—not five logos—date a refuse-line this week, or nothing changed. Keep this beside the tool; read before you start.
1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)
- [ ] Tools/writes paused
- [ ] Refuse-line dated
- [ ] Artifact path saved
- [ ] Next link chosen (or stop)
Before you start
Sit with three real asks from this week. You will label trust/check/stop for “Pick one default chat app, one Project”—bring the asks, not slogans. Guide: foundations-build-a-personal-ai-stack. If you only have a blank practice box, stop and fetch the real job first.
- Goal in one line: ___
- Allowed tools: ___
- Forbidden: ___
- Human approve needed for: ___
How to use this week
This week: pick one default chat app, one Project habit, and one weekly review slot—refuse a fifth logo. Write the stack card on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed foundations-build-a-personal-ai-stack, put 25 minutes on the calendar and redo once.
Keep it real
Run this guide’s Practice now on work you will actually ship this week—not a fictional scenario. Dated notes beat perfect theory.
Do not bookmark-only
Finish Practice now, then tick this guide on your path. Titles unread are not skills.
Close the loop
After Practice now, write one line: what you will refuse next time. That line is the habit.
Example
Filled prompt
Colleague pushes me to buy three Pro seats "to compare."
Rewrite my stack card refusal: one default I already open daily + Friday review.
7-day plan. No third logo.
What good output looks like
- Context pack stays ≤ one screen when asked
- Labels trust/check/stop correctly for “Build a personal AI stack in one week”
- Pass/fail: you can explain the limit in one line
- Does not treat the model as a database or authority
Red flag
Three vendors for one job in three days; a stack of trials with no default—set defaults or stop shopping.
Pitfalls
| Pitfall | Fix |
|---|---|
| Five defaults | One for 7 days |
| No safety list | Day 1 deliverable |
| Projects per mood | One workstream |
| Skipping the review | Day 6 is mandatory |
Example
Filled prompt
Temptation: skip the habit for foundations-build-a-personal-ai-stack to “save five minutes.”
Job still: Pick one default chat app, one Project
Do the smallest correct pass: Done visible · one checkable artifact · Unknowns labeled [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: the artifact + the refuse-line you said aloud.
What good output looks like
- Names the shortcut you refused (specific to foundations-build-a-personal-ai-stack)
- Still delivers a checkable artifact for “Pick one default chat app, one Project”
- Unknowns labeled; draft-only respected
- Pass/fail: refuse-line written and dated (foundations-build-a-personal-ai-stack #4)
Practice now
Live card: apply “Build a personal AI stack in one week” to a mistake from this week; write the fix habit (Asia/Shanghai).
Today: fill writing / research / code defaults and finish one real task on the defaults only. Write switch triggers beside the stack (Asia/Shanghai).
Today card (copy) — foundations-build-a-personal-ai-stack: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___
- [ ] Artifact path written
- [ ] Refuse example would say "yes"
- [ ] Dated Asia/Shanghai
One sentence takeaway
One default, one Project habit, one weekly review—not five logos—date a refuse-line this week, or nothing changed
- You can point to a dated refuse-line
- You have one artifact path from tonight
- You can teach the red flag in one sentence
Next
7-day path · GFB · Free vs paid · Compare · When AI sounds sure but wrong
Pair with today: open the first Next link (path-first-7-days) only after you dated a refuse-line for this guide (Asia/Shanghai).
一周内搭好个人 AI 工具组合
目标: 选定一个默认聊天应用、一个 Project 习惯、一次每周回顾——不必买五个工具,也不必追每一次发布。
适合: 被选项和标签页淹没的新手。
这里的「组合」故意无聊:默认聊天 + 工作区 + 安全笔记 + 每周 15 分钟回顾。天天换不是组合,是折腾。
个人栈是三个默认:聊天工具、笔记落点、核实习惯——不是十七个插件。只有每周工作需要时才加工具。
三个默认胜过十七个图标。没有每周工作的工具,是带权限的装饰。
为什么新手跳过
第一周买五个工具像有准备。一个默认聊天、一个 Project 习惯、一次周复盘会复利;logo 不会。
步骤 1——只留三个槽位
- 主聊天: ChatGPT *或* Claude *或* Grok(7 天内一个默认)。
- 工作区: 一个 Project(或等价物)承接你的主线工作。
- 安全笔记: 永不粘贴清单(密钥 + PII)存在聊天外。
可选第四:存放版本化提示词模板的笔记文件。
步骤 2——一周计划
用真实材料做这一步——不要凭记忆。
第 1 天:账号 + 安全清单 + 钉住 GFB 模板
第 2 天:用目标/格式/边界做第一件真任务
第 3 天:建一个 Project + 一个文件(已打码)
第 4–5 天:三件真实工作/学习任务;记录浪费时间之处
第 6 天:回顾 —— 保留、丢掉或切换默认工具
第 7 天:给未来的自己写 5 行「我如何用 AI」
实例
填好的提示词
为自由写作者提新手栈:默认聊天、草稿放哪、每周回顾仪式、最多一个连接器。预算:免费优先。
像样的输出大概长这样
- 免费优先
- 最多一连接器
- 有回顾仪式
- 贴合填例里的约束
- 不编造事实、负责人或指标
- 新手能看懂;可直接交给同事
步骤 3——抵抗闪亮物体周
新模型发布不是周中重建组合的理由。实验放在单独的周末聊天。
实例
填好的提示词
我装了 9 个插件。裁到 3 个并写保留理由。
背景:本周真实工作——不是玩具演示。相关则保留不编造/只草稿。新手能看懂。
像样的输出大概长这样
- 裁到 3
- 有保留理由
- 清楚
- 贴合填例里的约束
- 不编造事实、负责人或指标
- 新手能看懂;可直接交给同事
保存这张卡
卡面:写作/研究/代码默认 + 切换触发。选型前看卡;缺项就停,不硬开。
1. 我交出了:___ 2. 我拒绝了:___ 3. 我永不再做:___(日期:Asia/Shanghai)
- [ ] 工具/写入已暂停
- [ ] 拒做句已标注日期
- [ ] 成品路径已存
- [ ] 已选下一步(或停)
开始前
打开你真正会用的账号/项目。准备好与「一周内搭好个人 AI 工具组合」相关的真实材料(不要空白练习框)。
默认姿态:在人确认发送/写入之前只出草稿。授予新工具前,先写一条带日期的拒做句(Asia/Shanghai)。
- 一句话目标:___
- 允许的工具:___
- 禁止:___
- 需要人批准:___
本周怎么用
本周填三格默认栈,并用默认完成一件真事;备用工具只在触发条件满足时用。把过/不过写进笔记并注明日期(Asia/Shanghai)。
保持真实
用本周真会交付的工作做「现在就练一次」——不要虚构场景。带日期的笔记胜过完美理论。
不要只收藏
做完「现在就练一次」,再在路径上打勾。没练过的标题不是技能。
闭环
「现在就练一次」后写一行:下次你要拒绝什么。那一行才是习惯。
红旗
同一任务三天换三家;栈里全是试用号无默认。无触发却换工具——停。卡上写不清就不继续——先补检查项再跑。
常见坑
| 坑 | 改法 |
|---|---|
| 五个默认 | 7 天一个 |
| 没有安全清单 | 第 1 天交付物 |
| 心情一个 Project | 一条工作流 |
| 跳过回顾 | 第 6 天必做 |
实例
填好的提示词
任务:Pick one default chat app, one
场景要点:三张真实请求便签在手;练习编号 3/4。
边界:仅草稿;未知 [?];禁止悄悄发送;禁止编造指标。
返回:可检查产出 + 过/不过理由一行。
像样的输出大概长这样
- 约束贴着「一周内搭好个人 AI 工具组合」与 foundations-build-a-personal-ai-stack
- 未知标 [?];不编造负责人/数字
- 不可逆动作前停下
- 一分钟内能打过/不过(foundations-build-a-personal-ai-stack #3)
实例
填好的提示词
任务:Pick one default chat app, one
场景要点:三张真实请求便签在手;练习编号 4/4。
边界:仅草稿;未知 [?];禁止悄悄发送;禁止编造指标。
返回:可检查产出 + 过/不过理由一行。
像样的输出大概长这样
- 约束贴着「一周内搭好个人 AI 工具组合」与 foundations-build-a-personal-ai-stack
- 未知标 [?];不编造负责人/数字
- 不可逆动作前停下
- 一分钟内能打过/不过(foundations-build-a-personal-ai-stack #4)
- [ ] 成品路径已写
- [ ] 拒做例句会说「可以」
- [ ] 已标注 Asia/Shanghai 日期
- 能指出一条带日期的拒做句
- 今晚有一条成品路径
- 能用一句话说清红旗
← Back to home · Learn · Tools · Compare · Start