Tag: claude-code
All the articles with the tag "claude-code".
-
Cutting Rules to Save Tokens: One Week of AI Harness Ablation
Most people keep piling instructions onto their AI, but removing rules is what actually saves tokens. Here are the one-week results of my ablation experiment and how Anthropic recommended the exact same thing.
-
規矩適度拿掉，額度才能越省：寫給 AI 的規則消融實驗滿一週
大家都習慣幫 AI 助手狂加規則，但我發現規矩適度拿掉額度才能越來越省。本文記錄我的消融實驗滿一週數據，以及 Anthropic 官方剛好倡導的極致減法。
-
My AI's Memory Files Kept Growing, So I Deleted 101 and Added a Gate
After a few months with Claude Code, the memory files it wrote for itself had piled up past four hundred, mostly running logs and client status. Here is how I sorted them, cut them to just over three hundred, and put a write gate in front to stop the regrowth.
-
AI 的記憶檔越寫越多，我一次砍掉 101 份，再裝一道閘門
用 Claude Code 幾個月後，它自己寫下的記憶檔累積到四百多份，多半是流水帳和客戶狀態。這篇寫我怎麼把它們分到該去的地方、砍到三百份以下，並用一道寫入閘門擋住它再長回來。
- Updated:
Letting Claude Dig Through a Month of My AI Chats: Habits, Mods, and Auto Mode Rules
I had Claude Code read 300-plus of my conversations from the past month. It surfaced four habits worth copying, turned three of my catchphrases into switchable auto/out/wrap modes, and the same logs can rewrite your auto mode rules.
- Updated:
讓 Claude 翻我自己一個月的 AI 對話：挖出的習慣、Mod 和自動模式規則
請 Claude Code 讀我過去一個月三百多場對話紀錄，挖出四個值得照抄的習慣、三句口頭禪做成可切換的 auto／out／wrap 模式，也能拿來改寫 auto mode 的規則。
-
Switching Your AI's Working Mode with One Command: Building work-mode and a Week of Testing
I built work-mode, a Claude Code plugin with autonomous, delegate and wrap-up modes plus desktop/phone reply formats. The pain points, how it evolved, numbers from 136 sessions, and prompts you can copy.
-
用一個指令切換 AI 的工作模式：work-mode 開發與一週實測
我做了 work-mode 外掛，讓 Claude Code 切換自主、外派、收斂三種模式，並依電腦或手機調整回覆。這篇講痛點、開發過程、136 場對話的實測數字，以及可以照抄的提示詞。
-
Measuring Again Three Months Later: From AI Adoption L2.5 to L3
In July I rated myself L2.5 on Boris's AI adoption table. Three months later I measured again: Claude can reach my knowledge base and old chats, code goes through Codex review first, schedules run everything, and 430 sessions in two weeks were started by code.
-
三個月後重量一次：我從 AI 導入 L2.5 站上 L3
七月照 Boris 的 AI 導入分級表自評 L2.5，三個月後重新量一次：知識庫和舊對話 Claude 自己拿得到、程式先過 Codex 審查、排程全面上線，兩週 430 場 Claude 是程式叫起來的。
-
Burning Quota and Saving Quota: How I Inventoried, Allocated, and Spent My AI Credits in Two Weeks
I found seven separate AI quota pools. I burned the ones about to expire on work that can check itself, and spent the surplus on things that will save quota later. Includes the inventory, my allocation rules, results, and prompts you can copy.
-
燒額度跟省額度：我這兩週怎麼盤點、分配、用掉 AI 額度
我盤點出七個 AI 額度池，一邊把快作廢的額度燒在能自己驗對錯的工作上，一邊用多出來的額度做以後能省額度的事。附盤點表、分配判準、實際成效，跟可以直接照抄的提示詞。
-
I Asked My AI "Now What?" 41 Times in Two Weeks
Letting an AI run long jobs in the background is easy. Knowing where it got to when you come back is not. I counted two weeks of my own messages and found I was missing a status board, not more monitoring.
-
我兩週問了 AI 41 次「現在呢」
讓 AI 在背景跑長任務很簡單，難的是回來時一眼看懂它跑到哪。翻完自己兩週 1,053 則訊息，我發現缺的不是監控，是一張自己能看的狀態表。
-
Which Claude Code Plan to Buy: Pro, Max 5x or Max 20x
Who should buy Pro, who should buy Max 5x, whether Max 20x is worth it, and when to just use the API. Prices come from Anthropic's official pages; the usage judgment comes from running Claude Code every day.
-
Claude Code 訂閱怎麼選：Pro、Max 5x、Max 20x 該買哪個
誰該買 Pro、誰該買 Max 5x、Max 20x 要不要買，什麼時候直接用 API。價格以官方頁面為準，用量判斷來自我每天開 Claude Code 的經驗。
-
Two Claude Mods I Built: a Recording Mask and a Warm-Cache Plugin
I built two Claude Mods: one that masks sensitive info while I record courses, and one that keeps the Claude Code prompt cache warm. Then I found Claude Code already has idle compact built in.
-
自己做了兩個 Claude Mod：錄課遮罩與暖快取
我做了兩個 Claude Mod：錄課用的敏感資訊遮罩，和 Claude Code 暖快取外掛。後來才發現 Claude Code 原生就有閒置壓縮。
-
How I use herdr: three workspaces for standing, today and long-term
After Opus 5.5 analyzed 30 days of my session logs, I split herdr into standing, today and long-term workspaces. Four status lights keep the standing agent aware, and Opus can jump into the next pane to rescue a task.
-
我怎麼用 herdr：常駐、今日、長期三個工作區
請 Opus 5.5 分析 30 天 session log 後，我把 herdr 工作區分成常駐、今日、長期；四種燈號讓常駐 agent 掌握全場，還能叫 Opus 跳到隔壁窗格救場。
- Updated:
My Pre-Trip Remote Checklist: Leaving the Mac Mini as Home Base
Eight things I checked before flying out, to keep a home Mac Mini reachable as the base for Claude and Codex: Tailscale, Herdr, caffeinate, auto-reboot, and remote file access.
- Updated:
出國前的遠端連線檢查表：把 Mac Mini 留在家當本體
出國前一次寫下的八條遠端配置檢查表：Tailscale、Herdr、咖啡因防休眠、自動重開機、遠端存取，把留在家中的 Mac Mini 當成 Claude/Codex 的 harness 本體。
-
159 Confirmation Prompts in 14 Days, and About 70% Were False Alarms
I audited 14 days of PreToolUse hook ask prompts: 159 of them, roughly 70% false positives. A guard hook should match the command position, not the whole string, and you can measure the fix from hook events in the transcript without replaying anything.
-
14 天 159 次確認，七成是誤判
盤點 PreToolUse hook 14 天跳出的 159 次 ask，約七成是誤判。攔截要比對指令位置而不是整段字串，成效從 transcript 的 hook 事件統計，不重播。
-
Keys Leak Where You Feel Safe
Three near-leaks of API keys in one week, and none came from pasting one somewhere public: skill packaging, a masking command that failed, and a build config. Plus the rule I use to decide whether to rotate.
-
金鑰漏在你以為安全的地方
一週內三次金鑰差點外洩，入口都不是貼錯：skill 打包、遮蔽指令失手、build 設定。最後附上我判斷要不要輪換的準則。
-
Running 5+ Claude Code/Codex at Once: My Five Fixes for the Attention Bottleneck
Once I have more than 5 Claude Code/Codex windows going, I hit an attention bottleneck — constant context switching is genuinely exhausting. Five things that get me past it: a good multi-window manager, voice input, an overnight schedule, a reviewable skill, and regular pruning.
- Updated:
Three Moves Between Claude and Codex
Moving the whole harness to Codex in May, switching my daily driver in July, a honeymoon where the quota would not run out, a subsidy-war July that ledgered 57.5x, to August quota cuts, and moving back to Claude in September. One chronological log.
- Updated:
When to Call In Fable: Three Moments, and Don't Turn On ultracode
The most expensive model is not meant to run the whole way. Three moments where calling in Fable feels right to me, plus why I cap Opus 5 at med, and the weekly cycle I fell into: efficiency king Monday to Thursday, Fable mode Friday to Sunday.
-
同時開 5 個以上 Claude Code／Codex，我的五個注意力瓶頸解法
同時開超過 5 個 Claude Code／Codex 視窗時會遇到注意力瓶頸，一直 context switching 真的很累。分享目前跳脫這個瓶頸的五個做法：多窗口管理器、語音輸入、夜間排程、reviewable skill、定期做減法。
- Updated:
我在 Claude 和 Codex 之間搬了三次家
五月把整套 harness 搬到 Codex、七月換掉主力、蜜月期額度花不完、七月補貼大戰打出 57.5x 帳面價值，到八月偷縮額度、九月又搬回 Claude。一條照時間排的編年紀錄。
- Updated:
何時派工 Fable？三個時機，還有別開 ultracode
最貴的模型不是拿來全程跑的。三個我體感最好的 Fable 派工時機、為什麼 Opus 5 我最多開到 med，以及我後來變成週一到週四效率王、週五到週日 Fable 模式的那個循環。
- Updated:
Your Own Machine Is the Attack Surface: Leftover Credentials, Permission Flags, Untrusted Input
Everyone talks about AI security as whether the model will say the wrong thing. What actually bites you is the plaintext keys left on your disk, the permission flag you waved through, and the untrusted input you fed it.
- Updated:
你的電腦才是攻擊面：殘留憑證、權限旗標、不可信輸入
大家談 AI 資安都在談模型會不會說錯話，但真正會咬你的是本機殘留的明文金鑰、隨手開的權限旗標，還有你讓模型讀進來的不可信輸入。
-
Claude Code for Tutors: Letting an Agent Teach Teachers How to Use Agents
A free project for teachers that brings a teacher's own scenarios into Claude Code and Codex, so an Agent walks you through every feature one lesson at a time.
-
Claude Code for Tutors：讓 Agent 直接教老師怎麼用 Agent
我做了一個給老師的免費專案，把老師會遇到的情境帶進 Claude Code 與 Codex，讓 Agent 一堂一堂帶你走過每個功能。
- Updated:
More Subagents Won't Make You Faster
From wanting 13 subagents to chat for me, to one person running 1000, to agents arguing across a table — the real bottleneck is the human main agent, and the fix is deduping before you dispatch.
- Updated:
No Error Doesn't Mean Success: Silent Failures, Opus Fabricating Tool Output, and the Hook That Finally Stops It
Exit 0, HTTP 200, and a model saying "done" are all unreliable success signals. Cases from my own code, CLIs, and APIs through to a model inventing commit hashes out of thin air, ending with the one thing that actually holds.
- Updated:
派更多 subagent 不會讓你更快
從想派 13 個 subagent 代聊、一個人操控 1000 個，到面對面互審代碼的荒謬幻想——真正的瓶頸是人類這個 main agent，解法是先去重去衝突再派工。
- Updated:
沒拋錯不代表成功：靜默失敗、Opus 捏造工具輸出，以及一個擋得住的 hook
exit 0、HTTP 200、模型說「已完成」——這三種訊號都不能當成事情做完了。從自己的程式碼、CLI、API 一路到模型憑空生成 commit hash 的實錄，最後用一個 hook 收尾。
-
I Built a Skill That Semantically Searches My Old Claude Code / Codex Sessions
I keep forgetting which session a demo came from, only remembering roughly how many days ago and roughly what I did. So I built a skill that can search all my past Claude Code / Codex sessions by meaning, not just keywords.
-
我做了一個能語意搜尋 Claude Code / Codex 舊對話的 SKILL
備課時常常忘記某個示範是哪場對話做的，只記得大概幾天前、做過什麼。我做了一個 SKILL，能語意模糊搜尋過去所有 Claude Code / Codex 對話，不只靠關鍵字比對。
- Updated:
7 Practical Tips for Talking to Claude 5: Less Drift, Less Chatter, Less Slacking, Less Nagging
Some practical tips I have been sharing with friends lately on talking to the Claude 5 generation of models: a home-made explain skill for alien-speak, answering everything in one pass instead of letting the conversation drift, voice-input setups, first-principles pruning, a hook that treats slacking, a minimal CLAUDE.md, and a fix for the phantom pushback habit.
- Updated:
Where the Quota Actually Goes: Claude Code Cache Bugs, Opus 4.7's 2x Burn, and Runaway Subagents
Four quota incidents in full: two official cache bugs, an 80x jump in API requests pulled from JSONL, Opus 4.7 measured at 2x consumption, and one session of mine that burned 90% in half an hour.
- Updated:
Two Worlds of Web-Based Claude Code Setup
Web Claude Code has two completely different runtimes — cloud VM and remote-control. Here is what I learned setting up both, the small bugs I hit, and why some user-level configs simply cannot be lifted to the cloud as-is.
- Updated:
A Year In, My Answer to "Terminal or Desktop App?" Has Changed Three Times
From March's Cowork token burn, to April's "still the terminal," to May's "beginners should just start with the desktop app," to August's "the CLI is the firstborn." One question, three different answers across five posts, laid out in the order I gave them.
- Updated:
Fable 5's One-Week Return: Turning the Most Expensive Model into a Skill Distillation Engine
Fable 5 came back for one week only. I did not spend it on daily busywork — I spent it on high-leverage judgment, distilled into skills that cheap models can follow.
- Updated:
The More Rules You Add, the Less Claude Listens — I Sent a Team of Agents to Trim My Setup and Cut 36% of Always-On Context
Late at night I got Opus 4.8, and my weekly quota happened to reset. The first thing I did was put my harness on a diet. A COO student who had burned through 88% of his 1M context made me face one thing squarely: the more rules you add, the less the model listens.
- Updated:
Leveling Up the iPad Workflow — Surviving Internet and Power Outages, and Why I Ditched the Magic Keyboard
A follow-up to the full iPad-runs-Claude-Code guide. This one is not about setup, it is about robustness: home internet in Bangkok drops, the rainy season kills the power, so how does the host machine survive? Plus why I gave up the Magic Keyboard for my mouth and some gestures.
- Updated:
跟 Claude 5 對話的 7 個實用技巧：不發散、不話癆、不偷懶、不雞婆
一些最近跟朋友分享的，跟 Claude 5 代系列模型對話的實用小技巧：自製 explain skill 抓外星話、一次回完別讓對話發散、語音輸入配置、first-principles 剪枝、用 hook 治偷懶、CLAUDE.md 極簡化，以及治雞婆的幻影反駁。
- Updated:
額度是怎麼被燒掉的：Claude Code 快取 bug、Opus 4.7 的 2x 消耗、subagent 遞迴繁殖
四起額度事故的完整紀錄：兩個官方快取 bug、JSONL 扒出來的 80 倍 API 請求、Opus 4.7 實測 2x 消耗，以及我自己一個 session 半小時燒掉 90% 的 subagent 遞迴。
- Updated:
網頁版 Claude Code 環境設定的兩個世界
網頁版 Claude Code 有兩種環境——雲端 VM 跟 Remote-control。這篇整理我實測下來的設定訣竅、會踩到的小 bug，以及為什麼有些設定不能無腦丟到雲端。
- Updated:
一年下來，我對「該用終端機還是桌面版」的答案變了三次
從三月的 Cowork 燒 token、四月的「答案還是終端機」、五月的「初學者直接從桌面版開始就好」，到八月的「CLI 是親生的」。同一個問題，我在五篇文章裡給過三種不同的答案，這裡照時間順序排出來。
- Updated:
Fable 5 回歸一週：把最貴的模型變成 Skill Distillation 引擎
Fable 5 限時回歸一週，我沒拿去做日常小事，而是拿去做高槓桿判斷、蒸餾成便宜模型可照做的 skills。
- Updated:
規則越加，Claude 越不聽話——派一隊 AI 重整設定，常態上下文省 36%
半夜拿到 Opus 4.8、額度剛好重置，我做的第一件事是減肥我的 harness。一個 COO 學員把 1M 上下文用到 88% 的案例，讓我認真面對一件事：規則加越多，模型反而越不聽話。
- Updated:
iPad 工作流進階——斷網斷電的備案，與我為什麼放棄妙控鍵盤
iPad 跑 Claude Code 全攻略的續篇：談的不是安裝，是穩健性——曼谷家用網路會斷、雨季會停電，主機端怎麼撐住；以及我為什麼放棄妙控鍵盤、改用一張嘴加手勢。
-
My CLAUDE.md Boiled Down to Eight Lines of "Take Pride In…, Take Shame In…"
My CLAUDE.md cut down to eight paired maxims, plus a human-machine collaboration circular written deliberately in Party-document style, plus a sixteen-character guideline.
-
我的 CLAUDE.md 精煉到只剩八句「以…為榮，以…為恥」
把 CLAUDE.md 一路砍到只剩八組對句，外加一篇刻意寫成公文體的人機協同宣導文，還有十六字方針。
-
Two Skills That Make AI Talk Like a Human: ASD-STE100 for Grammar, ISO 24495 for Structure
A skill I threw together three weeks ago got passed around by people overseas and picked up three PRs, so I shipped a second one I use every single day.
-
讓 AI 對你說人話的兩個 skill：ASD-STE100 管文法，ISO 24495 管結構
三個禮拜前隨手做的 asd-ste100-skill 被老外瘋狂轉載還留了三個 PR，順手再開一個天天在用的 iso-24495-skill。
-
Information Diet: I Pulled My Own Chrome History and Audited Where My Attention Goes
People obsess over whether every bite of food is clean, then swallow piles of dirty info online without a second thought. So I pulled my own Chrome history db and had it analyze my browsing habits. A few sections came out uglier than I expected.
-
Information Diet：我抓自己的 Chrome 瀏覽紀錄，做了一次注意力盤點
現代人極度在意吃進口裡的每一塊食物乾不乾淨，卻毫不在乎上網吃到的一大堆 Dirty Info。所以我抓了自己的 Chrome 瀏覽紀錄 db，讓工具分析我的上網習慣，結果有幾段比我預期的難看。
-
The CLI Is the Firstborn
New features and fresh bug fixes land in the CLI first. Remote control waits forever. Same company, wildly different update cadence.
-
CLI 是親生的，其他都是後媽養的
新功能和剛修好的 bug 都優先落在 CLI，remote control 要等猴年馬月。同一家公司的產品，更新頻率差很多。
-
Six New Context Engineering Rules for Claude 5, and the 1,473 Lines I Cut
After reading Anthropic's context engineering guidance for Claude 5, I turned the key points into nine cards, then cut 1,473 lines from a harness I had built up over four model generations.
-
Supposedly the Smartest Model, and Opus 5 Spent My Whole Day Spinning in Place
Wrong languages, sudden Simplified Chinese, then whole turns with no visible output — and a session log that matched an issue open since June 15.
-
Claude 5 時代的情境工程六條新規則，與我砍掉的 1473 行 harness
讀完 Anthropic 對 Claude 5 的情境工程指南後，我把重點做成九張圖卡，然後照著把累積四個世代的 harness 削掉 1473 行。
-
號稱最聰明的 Opus 5，一整天在我對話裡空轉
從回錯語言、突然寫簡體，到整輪沒有可見輸出，查 session log 之後對上一個 6/15 就開著沒修的 issue。
-
I'm Stuck at Stage 2.5 of AI Adoption
After watching Boris Cherny break down the stages of AI adoption, it hit home: I'm stuck at stage 2.5, where limited attention plus low trust becomes a vicious cycle. This week I used late-night schedules, a morning dashboard, and herdr auto-spawning sessions to cut a 4-5 hour workflow down to 1-2 hours.
-
Some of My Subagents Were Already Grandpas
A CCX quota incident with no guardrails set: subagents bred recursively, one session burned 90% in half an hour, and here is the full forensics and fix.
-
Two Traps Running Claude Code on Local Ollama: Truncated Context, and A3B Buckling Under Heavy Verification
Two things I logged: cco (Claude Code driven by local Ollama) had long been giving off-topic answers, and the root cause was not a weak model but a full harness whose system prompt had ballooned to 30-50k tokens and was being silently truncated; then I put A3B on the Mac mini for two days as a night worker.
-
Instead of Begging the Model Not to Lie, I Wrote a Hook That Stops It
The sequel to the Opus 4.8 confabulation post: I moved "don't make up numbers" from a plea in CLAUDE.md to a pending-guard hook that blocks git commit at PreToolUse.
-
Second Harness Diet: Global Skills From 58 Down to 40
A follow-up to the harness diet series: six months later, a bigger cleanup that cut my global skills from 58 down to 40, start to finish.
-
我卡在 AI 導入的 2.5 階段
看了 Boris Cherny 分享的 AI 導入階段框架後有感而發：我卡在 2.5 階段，注意力有限加信任不足變成惡性循環，這週靠深夜排程、晨間儀表板、herdr 自動開 session 把 4-5 小時的協作壓到 1-2 小時。
-
有些 subagent 都當阿公了
一次 CCX 沒設好護欄的額度事故：subagent 遞迴繁殖，一個 session 半小時燒掉 90%，事後鑑識與修法全記錄。
-
本機 Ollama 跑 Claude Code 的兩個坑：context 被截斷、A3B 撐不住重驗證
記錄兩件事：cco（本機 Ollama 驅動 Claude Code）長期答非所問，根因不是模型不夠聰明，是完整 harness 的 system prompt 早就膨脹到 3-5 萬 token 被靜默截斷；順手把 Mac mini 換上 A3B 當夜間工人測了兩天。
-
與其拜託模型不要騙我，不如寫一個擋得住的 hook
接續 Opus 4.8 捏造工具輸出那篇：我把「別亂編數字」從 CLAUDE.md 的拜託，升級成一個掛在 PreToolUse 擋 git commit 的 pending-guard hook。
-
第二次 harness 減肥：全域 skills 58 砍到 40
接續 harness 減肥系列，半年後做了第二輪更大規模的整理，把全域 skills 從 58 個砍到 40 個的完整過程。
-
I Finally Switched My Daily Driver from Claude Code to Codex
I try new tools easily, but I am slow to leave the ones already built into my routine. This time, quotas, pricing, and product direction all crossed the line together.
-
我終於把主力從 Claude Code 換成 Codex 了
我很愛試新工具，卻很難離開已經用習慣的工具。這次真正讓我換主力的，不是一次 benchmark，而是額度、價格與可預見的產品方向一起越過了臨界點。
-
I Let My /adhd Skill Go Dig Up a 3C-Scene Price-Hike Rumor on Its Own
I toss a vague rumor topic at my /adhd skill and watch it search, admit it searched wrong, stop to ask a disambiguating question, and finally piece the whole thing together with sources.
-
我讓 /adhd skill 自己去查一件 3C 圈的漲價八卦
含糊丟一個八卦題目給 /adhd skill，看它自己一路搜、承認搜錯、停下來反問消歧義，最後拼出全貌附來源。
-
Claude Seeing Ghosts Four Nights Straight: A Log of Opus 4.8 Fabricating Tool Output
A four-day log of Opus 4.8 tool-result confabulation: from the technical symptoms to the GitHub issue to JSONL forensics.
-
Claude 半夜見鬼連續四天：Opus 4.8 捏造工具輸出實錄
Opus 4.8 連續四天的 tool-result confabulation 實錄：從技術現象、GitHub issue 到 JSONL 鑑識。
-
Opus 4.8 Cries 'Prompt Injection,' Codex GPT-5.5 Tracks Down the Real Cause: a Worktree Race
With multiple sessions open in one repo and no worktree, Opus 4.8 raised a false prompt injection alarm, told me to check for supply-chain attacks and rotate API keys, until Codex GPT-5.5 read the session log and pinned the real cause: just a worktree race.
-
Opus 4.8 搞烏龍報『提示注入攻擊』，Codex GPT-5.5 揪出 worktree race 真因
Opus 4.8 在我忘開 worktree 的情況下誤報「提示注入攻擊」，叫我去查供應鏈、rotate API key，最後 Codex GPT-5.5 查 session log 才揪出真因只是 worktree race。
-
Running Taiwan Sports-Lottery Odds With Mobile Claude Code, Standing in the Lottery Shop: the Odds Are Garbage, You'll Lose
Walked past a lottery shop, felt like placing a sports bet, and on a whim wired up a betting-odds skill on mobile Claude Code right there. The verdict: the correct-score market carries a 191% overround, every expected value is negative, you lose.
-
在彩券行用手機 Claude Code 算運彩賠率：台運賠率爛透了，誰下誰賠
路過彩券行起念想下運彩，順手用手機 Claude Code 接賭率分析 skill 現場開算，結論：台運波膽盤水錢高達 191%，期望值全負，誰下誰賠。
-
Two Mindsets for Getting Unstuck: Logical Thinking, and the AI Pedagogy of Never Making the Same Mistake Twice
Teaching a student today, I said that breaking through when you are stuck is not hard. What matters are two mindsets: logical thinking, and an AI pedagogy like raising a child, where the goal is not for the AI to never err, but to never make the same mistake twice.
-
卡關時的兩個心態：用邏輯思考，與『不貳過』的 AI 教育學
今天跟一個學員教學時談到，卡關時破除障礙並不難，重點是兩個心態：用邏輯思考，以及像帶孩子一樣的 AI 教育學，追求的不是讓 AI 無過，而是不貳過。
-
Teaching a Talent Agency to Use Claude Code, and the Soft Landing of the DK Confidence Curve
A short trip back to Taiwan packed with private training sessions: walking a talent agency through contract review, receipt reconciliation, and closeout reports with Claude Code, plus a note on the DK confidence curve and its soft landing.
-
帶藝人經紀公司用 Claude Code，與 DK 信心曲線的軟著陸
短暫回台跑私人場培訓，帶藝人經紀公司的企劃、製片、財務用 Claude Code 做合約審閱、單據核對、結案報告，順便聊聊 DK 信心曲線的快速上坡與軟著陸。
-
The Perpetual Token-Burning Machine: Anthropic Really Is Trying
A few scattered gripes about Anthropic's relentless push to get users burning tokens: 103 auto-triggered agents, five-layer Russian-doll subagents, and Formosa-Plastics-tier flexing.
-
燒 token 永動機：Anthropic 真的很努力
幾則關於 Anthropic 在鼓勵用戶燒 token 這條路上的零碎吐槽：自動觸發 103 個 agent、五層俄羅斯娃娃 subagent、台塑等級的炫富。
-
The Five-Step SOP for Sneaking Claude Code Runs From the Hotel Over Dinner
Back in Taipei at a hotel, the five-step backup SOP I run before heading out to dinner with friends: pull power, keep it charged and online, caffeinate against sleep, tailscale, test remote desktop. Then sneak in some Claude Code over dinner.
-
出門吃飯前，讓 Claude Code 在旅館背景偷跑的五步 SOP
回台北入住旅館，出門跟朋友吃飯前的五步備援 SOP：取電、充電連網、防休眠、tailscale、遠端桌面試通。然後就能邊吃飯邊偷用 Claude Code。
-
From Miasma to Hades: How One Group Turned AI Tools Into a Supply-Chain Attack Vector
Two June 2026 npm/Python supply-chain attacks: Miasma backdoored Red Hat packages, then TeamPCP/UNC6780 upgraded to Hades, turning Claude Code, Cursor and 14 other AI tools into an attack vector. Includes self-check steps.
-
從 Miasma 到 Hades：同一個攻擊組織如何把 AI 工具當成供應鏈攻擊媒介
2026 年 6 月兩波 npm/Python 供應鏈攻擊：Miasma 入侵紅帽套件後門，TeamPCP/UNC6780 升級成 Hades，把 Claude Code、Cursor 等 14 款 AI 工具當成攻擊媒介。附自我檢查步驟。
-
A Few Takeaways from the Claude Code Anniversary Talk
Claude Code just turned one. Boldy (CC's father) and Cat Wu (CC+Cowork product lead) released an anniversary talk. Here are the core takeaways: agent armies, auto mode and routines, role convergence and mobile work, and context minimalism.
-
Don't Dump the Last Session's JSON — Check Your Harness First
No need to feed the whole context JSON from your last conversation: the harness has several layers — AGENTS.md, rules, skills, hooks — and raw session history is full of useless tool calls.