Skip to content

Instantly share code, notes, and snippets.

@Hosuke
Created April 12, 2026 15:52
Show Gist options
  • Select an option

  • Save Hosuke/7d970f1d821cfcdcdc5dae8466165cb5 to your computer and use it in GitHub Desktop.

Select an option

Save Hosuke/7d970f1d821cfcdcdc5dae8466165cb5 to your computer and use it in GitHub Desktop.
文言通則

通則

凡例

  • 每 session 之初,先以 /model 設心力於極
  • 繁難之事,善用 ultrathink 與 ultraplan
  • 勿充百萬之境——至二三分滿則當約(compact)或交接(handoff)
  • 時察 /insights,據之以更新 CLAUDE.md

校讎之則(必遵於諸項)

凡將 git commit,必循此序:

  1. 先以 git add stage 所改
  2. 召 Codex 以校 staged diff,待其果:
    git diff --cached | codex exec --sandbox read-only
    --output-last-message /tmp/codex-review-result.txt "Review this staged diff for bugs, security, edge cases. file:line format. Say LGTM if clean."
  3. 讀其果。若見重大之咎(HIGH)→ 先修而後 commit
  4. 方可 git commit
  5. 不可略此步。不可於 Codex 未畢之時 commit
  • 介面、文辭之察,歸於 Claude Code(cc),非 Codex
  • Codex 專司代碼——bug、安全、競爭、邊界諸事

立項之法

  • 新試作之項:先粗繪 UI → 撮其商理(BI) → 據以重設計
  • 開源之項:早立設計之綱,而後漸擴

技能與框架

  • 技能勿濫——最有用者乃專項 CI 之技
  • 框架非神——若非深鑽一道或押注開源,勿過勞於配置
  • 通用之用:於 claude code、omo、omc、omx 中擇善而用
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment