Claude Code 技能工廠：把重複流程封裝成可觸發的 SKILL.md
讓 Claude Code 訪談你一個反覆手動的流程，再產出一個結構完整的 Agent Skill（SKILL.md），含 name/description/觸發時機/逐步指令/驗收標準/supporting references，並驗證能被自動觸發與 /斜線指令呼叫。
你是不是每次都把同一串指令、同一張檢查表貼進對話？把它封裝成一個 Claude Code 技能。這支提示詞會訪談你的流程，產出可重複觸發、自動載入、團隊可共用的 SKILL.md，連觸發時機與驗收標準都幫你寫好。
[ Log in to see the full prompt ]Sign up free to see the full prompt, copy it, save it, and join the discussion. Free content unlocks on login; Pro content is a separate subscription.
何時用：你發現自己一直把同一套步驟（部署前檢查、產 commit message、寫 PR 範本、跑某個 lint+修復流程…）貼進 Claude Code 對話。為何有效：它先逼 Claude 訪談出「觸發時機 + 步驟 + 驗收定義 + 邊界情況」，再產出符合 2026 官方 SKILL.md 格式的檔案——重點放在 description（決定 Claude 會不會在對的時機自動載入）與一個明確的 Verify 步驟（避免假性完成）。技巧：① 對有副作用的流程（deploy/commit/送訊息）一定選 disable-model-invocation 改成只能手動 /呼叫；② 長的參考資料拆成 supporting files 走 progressive disclosure，平時不吃 context；③ 需要當下狀態就用 !`command` 注入，例如把 git diff 直接帶進指令。
Phase 1 問題（節錄）： 1) 觸發時機：你說的是「部署前」——候選觸發語：『要 deploy 了』『上線前檢查』『push 到 prod 之前』。這三個對嗎？還有別的？ 2) 步驟順序：a) 跑測試 b) tsc --noEmit c) 檢查 git 是否乾淨 d) 列出將上線的 migration——順序對嗎？有沒有漏？ ... Phase 2 產出（節錄）： --- SKILL.md --- --- name: predeploy-check description: 上線前安全檢查並阻擋有風險的部署。Use when the user says they are about to deploy, ship, or push to production. disable-model-invocation: true allowed-tools: Bash Read Grep --- ## Current git state !`git status --porcelain` ## Steps 1. Run the test suite; if any test fails, STOP and report which. 2. Run `tsc --noEmit`; report any type errors and STOP. 3. If the working tree above is not clean, STOP and list uncommitted files. 4. List pending migrations not yet applied to prod. 5. Verify: only output "SAFE TO DEPLOY" if steps 1-4 all passed; otherwise output the first blocker. 儲存：mkdir -p ~/.claude/skills/predeploy-check && ... 測試：對 Claude 說「上線前幫我檢查」應自動觸發；或直接打 /predeploy-check
Suno Engineer's Mindset: 4 Steps to a Song That Doesn't Sound Like AI
A studio engineer's breakdown of Suno's fatal weaknesses (fried vocals, high-frequency artifacts), plus a 4-step DAW workflow and a Suno Studio cleanup prompt.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.