Run any Skill in Manus with one click

fw-trap

Stars9

Forks0

UpdatedJuly 23, 2026 at 10:28

flightwake 登記坑 — 把非顯而易見的陷阱寫進 TRAPS registry。Use immediately when a surprising root cause is found (weird error, vendor quirk, encoding trap), or when the user says 記一下這個坑/trap.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kaiwutech-TW

kaiwutech-TW/flightwake

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	fw-trap
description	flightwake 登記坑 — 把非顯而易見的陷阱寫進 TRAPS registry。Use immediately when a surprising root cause is found (weird error, vendor quirk, encoding trap), or when the user says 記一下這個坑/trap.

fw-trap — 坑登記

目的:同一個坑,全專案(含未來的 session 和其他 agent)只踩一次。

什麼夠格進 TRAPS

症狀與根因距離很遠的(例:jsonb 存成字串 scalar → 根因是驅動對「字串參數+::jsonb」的編碼行為)
廠商的未文件化行為(例:某操作路徑不觸發 webhook)
環境差異坑(本機過、prod 炸)
不夠格:一般 bug、看錯誤訊息就懂的問題

步驟

依 .flightwake/TRAPS.md 檔頭示範的條目格式(OKF 式 frontmatter:name/type/tags/discovered) 寫進 .flightwake/TRAPS.md 最上面
四欄都要:症狀(原始錯誤訊息照貼)、根因一句話、解法/繞法、佐證連結(commit/record)
相關的坑用 [[name]] 互連
當下就寫——坑的細節半天就忘
新坑取代或涵蓋既有條目時:舊條目 frontmatter 的 status 改 superseded、內文指向 [[新條目]]——不刪行, 讓「舊 md vs 新 md」的衝突有明確方向邊
判斷坑的範疇:若坑不是本 repo 特有、任何專案都會踩(平台/語言/工具層,如 Node stdin 行為、shell 展開)—— TRAPS 照登(repo 登記簿必須自足:接手者與其他 agent 看不到你的個人記憶), 另存一份到你的使用者層記憶(如 Claude 記憶),防其他 repo 重犯。跨範疇各存是分工不是重複:通用坑只記在單一 repo,換個 repo 就會再咬一次

More from this repository

same repository

fw-trap

kaiwutech-TW/flightwake

flightwake trap registration — write a non-obvious trap into the TRAPS registry. Use immediately when a surprising root cause is found (weird error, vendor quirk, encoding trap), or when the user says log this trap / trap.

2026-07-239

fw-coldstart

kaiwutech-TW/flightwake

flightwake cold start — restore state before touching a repo. Use when starting work in a repo that has .flightwake/, when the user says take over / continue / coldstart, or at the start of any session touching a flightwake-managed repo.

2026-07-199

fw-handoff

kaiwutech-TW/flightwake

flightwake cross-session handoff — write CONTEXT for work that is unfinished and will continue later. Use when stopping mid-build on multi-session work, when the user says handoff / continue next time, or before context runs out on a large task.

2026-07-199

fw-record

kaiwutech-TW/flightwake

flightwake wrap-up record — write the flight record and update STATE. Use when wrapping up work that touched schema/prod, spanned 3+ commits, or when the session is ending; also when the user says wrap up / record this.

2026-07-199

fw-coldstart

kaiwutech-TW/flightwake

flightwake 冷啟動 — 接手一個 repo 前先恢復狀態。Use when starting work in a repo that has .flightwake/, when the user says 接手/繼續上次/coldstart, or at the start of any session touching a flightwake-managed repo.

2026-07-199

fw-record

kaiwutech-TW/flightwake

flightwake 收尾記錄 — 寫飛行紀錄並更新 STATE。Use when wrapping up work that touched schema/prod, spanned 3+ commits, or when the session is ending; also when the user says 收尾/記錄一下/record.

2026-07-189

name	fw-trap
description	flightwake 登記坑 — 把非顯而易見的陷阱寫進 TRAPS registry。Use immediately when a surprising root cause is found (weird error, vendor quirk, encoding trap), or when the user says 記一下這個坑/trap.

fw-trap — 坑登記

目的:同一個坑,全專案(含未來的 session 和其他 agent)只踩一次。

什麼夠格進 TRAPS

症狀與根因距離很遠的(例:jsonb 存成字串 scalar → 根因是驅動對「字串參數+::jsonb」的編碼行為)
廠商的未文件化行為(例:某操作路徑不觸發 webhook)
環境差異坑(本機過、prod 炸)
不夠格:一般 bug、看錯誤訊息就懂的問題

步驟

依 .flightwake/TRAPS.md 檔頭示範的條目格式(OKF 式 frontmatter:name/type/tags/discovered) 寫進 .flightwake/TRAPS.md 最上面
四欄都要:症狀(原始錯誤訊息照貼)、根因一句話、解法/繞法、佐證連結(commit/record)
相關的坑用 [[name]] 互連
當下就寫——坑的細節半天就忘
新坑取代或涵蓋既有條目時:舊條目 frontmatter 的 status 改 superseded、內文指向 [[新條目]]——不刪行, 讓「舊 md vs 新 md」的衝突有明確方向邊
判斷坑的範疇:若坑不是本 repo 特有、任何專案都會踩(平台/語言/工具層,如 Node stdin 行為、shell 展開)—— TRAPS 照登(repo 登記簿必須自足:接手者與其他 agent 看不到你的個人記憶), 另存一份到你的使用者層記憶(如 Claude 記憶),防其他 repo 重犯。跨範疇各存是分工不是重複:通用坑只記在單一 repo,換個 repo 就會再咬一次