think 是做什麼的？
將粗略的想法轉變為經過批准的、決策完整的計劃，並在編碼前驗證其結構。當用戶以任何語言詢問規劃、架構、設計方向、可行性、價值判斷，或某功能是否值得實現時使用。不適用於除錯或小幅修改。
將粗略的想法轉變為經過批准的、決策完整的計劃，並在編碼前驗證其結構。當用戶以任何語言詢問規劃、架構、設計方向、可行性、價值判斷，或某功能是否值得實現時使用。不適用於除錯或小幅修改。
這個技能專為需要在編碼前進行系統性規劃的開發者或 AI 助手而設計。它的核心目標是將模糊、粗略的想法轉化為結構完整、經過驗證的計劃，確保每一項決策都已經被批准，從而大幅降低後續開發的風險與返工成本。支援的平台包括 Claude Code、Cursor、Codex 等常見的 AI 編程助手。該技能透過引導使用者 (或 AI) 以結構化方式思考問題，從定義目標、分析可行性、評估風險，到最終形成一份「決策完成」(decision-complete) 的計畫書來運作。它特別擅長處理涉及規劃、架構、設計方向、可行性分析、價值判斷，以及「這件事值不值得做」這類策略性問題。請注意，它不適合處理單純的除錯(Bug fix)或微小的編輯任務，這些任務更適合直接使用其他工具或技能。
npx skills add https://github.com/tw93/waza/tree/main/skills/think將粗略的想法轉變為經過批准的、決策完整的計劃，並在編碼前驗證其結構。當用戶以任何語言詢問規劃、架構、設計方向、可行性、價值判斷，或某功能是否值得實現時使用。不適用於除錯或小幅修改。
This repo contains 7 individual skills — each has its own dedicated page.
Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask review/看看代码/合并前/看看issue/PR/release/push or to implement an approved plan, with safety gates for dirty and untracked worktrees. Not for exploring ideas, debugging root causes, or prose review.
Produces distinctive, production-grade UI for pages, components, visual interfaces, typography, and screenshot-driven polish. Use when users ask in any language for UI, page, component, frontend, typography, screenshot-grounded visual polish, or complaints that a screen looks unclear, ugly, inconsistent, or visually wrong. Not for backend logic or data pipelines.
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask 检查claude/检查codex/检查pi/配置检查/健康度 or report agents ignoring instructions, missing validation, or code becoming hard to maintain. Not for debugging code or reviewing PRs.
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.
Runs a six-phase research workflow that turns unfamiliar domains, source bundles, or collected material into publish-ready output. Use when users ask in any language to research, study, deep-dive, compile sources, synthesize unfamiliar material, or turn a source bundle into a coherent reference. Not for quick lookups or single-file reads.
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask 看这个链接/读一下/read this/check this URL. Not for local text files already in the repo.
Rewrites and polishes prose in Chinese or English, removes AI-like wording, and reviews product localization copy while preserving intent for drafts, docs, release notes, launch copy, and social posts. Use when users ask in any language to draft, rewrite, proofread, localize, polish release notes, remove AI-like wording, or prepare launch and social copy. Not for code comments, commit messages, or inline docs.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".