zenbu-powers

驗收標準對齊評估方法論。給定用戶原始任務需求 + 上游 agent 產出，本 SKILL 提供萃取 testable criteria、4 大評估維度、報告格式、與 reviewer agents 的職責邊界、以及 WEB / 桌面 / CLI / 純文件的驗收手法分流。供 acceptance-evaluator agent 載入；orchestrator 直接 evaluate 簡單任務時也可參考。

Git diff 驅動的瀏覽器模擬人工測試工作流程。分析程式碼變更、映射影響範圍、使用 agent-browser 執行瀏覽器測試、錄製影片截圖、產出測試報告。

技術文件研究員的完整工作流程與規範。涵蓋文件爬取流程（Library / 主題兩種模式）、 品質規範與行為準則、SKILL 產出模板與驗收流程。 供 lib-skill-creator agent 執行文件研究與 SKILL 產出時載入。

Markdown 轉換的完整工作流程。涵蓋 markitdown MCP 轉換、圖片處理與上傳、 SVG/Mermaid 渲染、輸出品質處理與清理。 支援 PDF、Word、PowerPoint、Excel、HTML、圖片、音訊等格式。 供 markdown-creator agent 執行文件轉換時載入。

Agent 工廠。根據黃金法則創建符合最佳實踐的薄殼 Agent + 配套 Skills。 當用戶需要「建立 agent」、「新增 agent」、「create agent」、「設計 agent」、 「agent 工廠」、「造一個 agent」時使用此 skill。

Multi-pattern text search, filtering, and replacement using the Aho-Corasick algorithm. Use this skill whenever the user wants to: search for multiple keywords/patterns simultaneously in text or files, filter or detect sensitive words, scan multiple files for a list of terms, or redact/replace matched content. Triggers on phrases like "掃描關鍵字", "敏感詞過濾", "多個 pattern 搜尋", "批次掃描", "redact", "replace patterns", "keyword filter", "find multiple words", "scan files for patterns", or any task involving simultaneous multi-pattern matching. Always prefer this skill over naive grep loops when more than one pattern is involved.

Turns ideas into approved design specs through Socratic dialogue, with a HARD-GATE blocking any implementation until a design is written and approved. Use before any creative work: features, components, WP plugins / Gutenberg blocks, behaviour changes, architectural proposals. Triggers: 思考一個新功能, 比較多種實現方式, 寫設計文件, 探索 design 方案, 業務需求 trade-off, 多個 approach 比較, 規劃新模組, brainstorm a feature, design a component, compare approaches, write a spec.

文件初建 playbook：全新專案 CLAUDE.md / rules / specs 的建立流程與模板。供 doc-manager agent 在 greenfield 場景載入。

開發分支收尾決策樹。當實作完成、所有測試通過後使用，引導使用者在 Merge / PR / Keep / Discard 4 個選項中做出選擇，並執行對應的 git + worktree 清理流程。 與 zenbu-powers:git-commit 互補：git-commit 處理「commit 訊息產出」，本 skill 處理「commit 之後到底要 merge / 開 PR / 保留 / 丟掉」。 改寫自 obra/superpowers 的 finishing-a-development-branch skill，整合 zenbu-powers 的 worktree 與 CI 雙模式。

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

從用戶的粗略需求出發，結合專案 specs（features、activities、open-issue）自動延伸，生成結構化 GitHub Issue 需求文件。觸發：「建立需求」、「開 issue」、「寫需求」、「新功能需求」、「feature request」、「我想做一個功能」、「需求文件」。預設 PM 模式；提到「DEV」、「開發」、「工程」、「技術需求」、「dev issue」時切換 Dev 模式。模式詳述見 SKILL.md。

NestJS 10+ / TypeScript 5+ 編碼標準與最佳實踐，涵蓋模組化架構、Dependency Injection、Controller/Service/Repository 分層、DTO + class-validator、Guards/Interceptors/Pipes/Filters、TypeORM/Prisma Repository Pattern、JWT/Passport 認證、Jest + supertest 測試規範與命名慣例。供 @zenbu-powers:nestjs-master 開發時遵循，並作為 @zenbu-powers:nestjs-reviewer 的判準。當開發或審查 NestJS 程式碼、建立新 Module、重構後端、或確認命名與型別慣例時請啟用此技能。

NestJS 10+ / TypeScript 程式碼審查 checklist，專精模組邊界、Dependency Injection、Guards/Interceptors/Pipes/Filters、TypeORM/Prisma Repository Pattern、class-validator DTO、JWT/Passport 認證與 Jest 測試覆蓋檢查。提供可逐項勾選的審查清單、嚴重性分級、before/after 對比範例與輸出報告模板，供 @zenbu-powers:nestjs-reviewer 審查時照表操作。與 zenbu-powers:nestjs-coding-standards 搭配：該 skill 寫「規範本身」，本 skill 寫「審查時照著跑的 checklist」。

React 18 / TypeScript 程式碼審查 checklist，專精 hooks、效能、a11y 與 Ant Design / Refine / React Query 整合檢查。提供可逐項勾選的審查清單與 before/after 對比範例，供 @zenbu-powers:react-reviewer 審查時照表操作。與 zenbu-powers:react-coding-standards 搭配：該 skill 寫「規範本身」，本 skill 寫「審查時照著跑的 checklist」。

系統化除錯方法論。遇到任何 bug、測試失敗或非預期行為時使用，在提出任何修復方案前強制執行。 以 4 階段流程（根因調查 → 模式分析 → 假設驗證 → 實作修復）杜絕「猜一下、改一下」的隨機修補， 並針對 WordPress / React / AIBDD 場景補充常見 bug 模式。 改寫自 obra/superpowers 的 systematic-debugging skill，在地化為 WP 生態。

TDD 執行協調 playbook（Red→Green→Refactor 循環 / Issue 拆分 / CI 與本地雙模式），供 tdd-coordinator agent 執行 TDD 流程協調時載入。預設使用純 sub-agent 鏈式委派；Agent Teams 與 worktree 為 opt-in 進階模式（見 references/team-and-worktree.md）。

在做出任何回應（包含釐清提問）之前先檢查是否適用——若適用，載入此 skill 以建立 orchestrator 心法、鏈式委派紀律與全域一致性原則。

Zenbu Apps (zenbu-cms, zb-cart, all Zenbu modules) unified design system. Use when building or reviewing admin dashboard UI — pages, components, layout structures, or design tokens (color/typography/spacing/border-radius/shadow). Triggers — admin UI, dashboard, page layout, design tokens, sidebar, batch select, action bar, WCAG, accessibility, QA checklist, Zenbu UI, zenbu-cms, zb-cart. Component / pattern / QA detail in references.

AIBDD TDD 流程統一決策中心——8 個 stage（control-flow / red / green / refactor / code-quality / step-template / schema-analysis / starter / test-skeleton）× 3 語言（C# / PHP / TypeScript）的合一入口。 從用戶 prompt（紅燈 / 綠燈 / 重構 / control-flow / starter / 批次跑 BDD 等）觸發， 依語言推斷與 stage 路由載入對應 references/{stage}/{language}.md。 當用戶說「紅燈」「綠燈」「control-flow」「跑 BDD 自動化」「重構」「TDD 批次」 「BDD pipeline」「test skeleton」「step template」「schema 分析」「骨架建立」 「初始化專案」「scaffold」「建專案」「make tests pass」「failing test」等 觸發詞時啟用。

跨 skill 共用的 reference 庫。包含 reconciler contract（desired-state reconciliation 合約）等 所有 form skill 共用的模式定義。不直接觸發，由其他 skill Read references/ 中的檔案。

AIBDD Phase 01 工具——只負責需求分析的 7 步拆解： Composition → Flow Alignment → Structural Read → Impact Analysis → Behavior Design → Clarify → Quality Gate。 以統一流程處理 greenfield / 新功能 / 改變需求（三者同一件事，差別只在起始狀態）。 產出 Execution Plan（Phase 02-07 的 scope 依據）+ Activity Diagrams + Feature Rules（@ignore，無 Examples）。 保持 Activity、.feature 兩個視圖的一致性（api.yml / erm.dbml 由後續 Phase 處理）。 ⚠️ 邊界區分：完整 AIBDD 全流程（Phase 01 → 04 串接、寫 .feature / api.yml / erm.dbml）請改用 @zenbu-powers:clarifier agent；純業務 idea 探索（產 design.md、不走 BDD）請改用 zenbu-powers:brainstorming skill。本 skill 是 Phase 01 工具，不串接後續 phase。

Activity 視圖的 Spec Skill（Reconciler）。從 idea 推導 Activity Diagram desired state（.mmd 或 .activity 格式） 並連動產生所有綁定檔案（.feature/.md）骨架，不確定處標記便條紙。 以 desired-state reconciliation 模式運作：讀取現有 .activity 檔（若存在）→ 推導 desired state → 計算 diff → 增量更新；Greenfield 時 current = 空，等同於從零建立骨架。 可被 /discovery 調用，也可獨立使用。支援兩種格式：.mmd（Mermaid flowchart，預設）與 .activity（自訂 DSL）。

API 視圖的 Spec Skill（Reconciler）。從 .feature 文件推導 OpenAPI 格式的 api.yml。 每個 Feature 的 command/query 對應一個 endpoint。 以 desired-state reconciliation 模式運作：讀取現有 api.yml（若存在）→ 推導 desired state → 計算 diff → 增量更新。Greenfield 時 current = 空，等同於從零建立。 可被 /discovery 調用，也可獨立使用。

系統抽象驅動的 BDD 分析（Reconciler）。從已確認的 .feature Rule 骨架推導系統抽象、 實體句型模型與覆蓋矩陣，再據此產出最小必要句型集的 .feature 檔案（含 Examples）。 以 desired-state reconciliation 模式運作：三階段各自讀取現有 artifact → 推導 desired state → 計算 diff → 增量更新。Greenfield 時 current = 空。 善用 Scenario Outline + Examples 做 Data-Driven 測試， 善用 Data Table 承載結構化輸入與驗證。 支援 Boundary 偵測——偵測到 Web Backend 時載入內建 preset（句型分析方針 + Handler 決策樹）。 由 @zenbu-powers:clarifier 在 Phase 03（BDD Analysis）親自呼叫， 或由 /zenbu-powers:aibdd-carry-on-engineering-plan 執行 Phase 03 卡片時觸發。

Entity 視圖的 Spec Skill（Reconciler）。從 .feature 文件推導 DBML 格式的 erm.dbml（資料模型）。 以 desired-state reconciliation 模式運作：讀取現有 erm.dbml（若存在）→ 推導 desired state → 計算 diff → 增量更新。Greenfield 時 current = 空，等同於從零建立。 可被 /discovery 調用，也可獨立使用。

Feature 視圖的 Spec Skill。從 .feature 骨架（含便條紙）、ES spec 或 User idea 出發，澄清並產出完整的 Gherkin Feature File。可被 /discovery 調用，也可獨立使用。

需求層級的全流程工程計畫產生器。給定任意新需求（功能群、單一功能、微調）， 自動產出 plan.md（含 Dependency Graph）+ 7 張 Phase 卡片 （External Quality: Strategic → Entity → BDD Analysis → API Contract → Implementation: Backend TDD → Frontend Build → Integration）， 然後委派 /aibdd-carry-on-engineering-plan 以 feedback loop 審查機制逐步執行。 當使用者說「specformula」「新需求工程計畫」「需求級 BDD 工程計畫」時觸發。 前提：arguments.yml 已存在（/aibdd-kickoff 已完成）。

The only Telegram skill your AI agent needs. Read messages, parse channels, download and transcribe voice notes — all via Telethon user API. One session file, zero bots. Use when user says 'read telegram', 'check saved messages', 'fetch from telegram', 'parse channel', 'transcribe voice', 'telegram search', 'check my telegram', or when any agent needs Telegram data. Also trigger on 'what did I save in telegram', 'read my saved messages', 'get messages from channel X', 'download voice notes'. Covers: ad-hoc reading, channel parsing with sanitization, voice/audio download. Requires TG_API_ID, TG_API_HASH env vars and a session file.

LINE Messaging API official reference at API-reference depth. Covers every endpoint, request/response schema, message object, webhook event, and rich menu / Flex Message structure. Use this skill whenever the task touches the LINE bot platform: building or debugging a LINE bot / LINE Official Account, handling LINE webhooks, sending reply / push / multicast / narrowcast / broadcast messages, issuing or verifying channel access tokens, validating the x-line-signature, building text / sticker / image / video / audio / location / imagemap / template / Flex / coupon messages, quick replies, rich menus and rich menu aliases, audiences, insights, coupons, profile / group / multi-person chat lookups, account link tokens, or membership features. Trigger on mentions of: LINE Messaging API, developers.line.biz, api.line.me, api-data.line.me, @line/bot-sdk, line-bot-sdk, replyToken, channel access token, channel secret, x-line-signature, LIFF bot, Flex Message, rich menu, narrowcast, postback event, webhook event object

LINE Ads API (LINE Ads Management API / LADM) official reference at API-reference depth. Covers the entire ad-platform REST API exposed at ads.line.me/api: every endpoint, request/response schema, query parameter, enum, definition object, delivery-status reason, and error reason. Use this skill whenever the task touches LINE advertising automation: building or debugging a LINE Ads integration, an Ad Tech partner, a Data Provider partner, or a Reporting partner; managing ad accounts (adaccounts), groups, link requests, campaigns, ad groups (adgroups), ads, creatives, media (image / video / animation / app upload), product catalogs / DPA product sets and products; building or reading custom audiences (UPLOAD, LOOKALIKE, WEBTRAFFIC, APP_EVENT, ACCOUNT_FRIENDS, VIDEO_VIEW, IMAGE_CLICK), custom conversions, LINE Tags and tag events; generating performance reports (pfreports), online reports, change-history reports; running ARS adgroup result simulations; or signing requests with JWS / HMAC-SHA256. Trigger on menti

LINE Conversion API official reference at API-reference depth. Covers the single Send Conversion Event endpoint, its authentication, every request / response field, all five JSON schema objects (ConversionApiRequest, web, event, user, custom), and the official LINE Conversion API development guidelines. Use this skill whenever the task touches server-to-server conversion / event tracking for LINE Ads: sending conversion events, PageView / Conversion / custom-conversion events, conversion measurement, ad delivery optimization, audience accumulation, or reporting for LINE Ads Platform (LAP); building or debugging a Conversion API client / integration; deduplicating events across LINE Tag and Conversion API; user matching with line_uid / click_id / phone / email / ifa / browser_id / external_id; hashing phone numbers or emails with SHA-256 for Conversion API; the X-Line-TagAccessToken / X-Line-ChannelID headers; the LINE Tag ID; the ldtag_cl click ID; the __lt__cid first-party cookie / browser ID; the LINE Tag _

LINE Developers Console official reference at API-reference depth. Covers the whole management-tool layer of the LINE Platform: what a Developer, Provider, and Channel are and how they relate; creating / deleting providers and channels; provider and channel limits; certified providers and provider pages; the immovable channel-to-provider linkage and per-provider user ID rule; logging in to the console with a Business ID; creating a developer account on first login; the developer account / Business ID / LINE account relationship; linking and unlinking a LINE account; which channel types a developer can create based on LINE-account link status; provider roles (Admin / Member / No role) and channel roles (Admin / Member / Tester) with the full per-tab, per-channel-type permission matrices for LINE Login, Messaging API, Blockchain Service and LINE MINI App channels; inviting developers by email, importing developers from a provider, editing roles, removing developers; best practices for provider and channel manag

LINE Front-end Framework (LIFF) official reference at API-reference depth. Covers the full `liff` JavaScript SDK method reference, the LIFF Server API, LIFF plugins, the pluggable SDK, the LIFF CLI / Create LIFF App tooling, and every step of building, registering, and opening a LIFF app. Use this skill whenever the task touches a LIFF app / LINE in-app web app: initializing the SDK, logging users in, reading the LINE user profile, sending messages on the user's behalf, scanning 2D / QR codes, sharing via the share target picker, or debugging a LIFF browser issue. Trigger on mentions of: LIFF, LINE Front-end Framework, LIFF app, liff.line.me, miniapp.line.me, @line/liff, @line/liff-cli, @line/create-liff-app, liff-inspector, liff-mock, the liff CDN sdk.js, liff.init, liff.ready, liff.id, liff.login, liff.logout, liff.getProfile, liff.getAccessToken, liff.getIDToken, liff.getDecodedIDToken, liff.getContext, liff.getOS, liff.getAppLanguage, liff.getVersion, liff.getLineVersion, liff.isInClient, liff.isLoggedIn,

LINE Login SDKs official reference at API-reference depth. Covers the native mobile/game SDKs that integrate LINE Login (LINE's OAuth 2.0 / OpenID Connect social login) into apps: the LINE SDK v5 for iOS Swift, the LINE SDK v5 for Android, the LINE SDK for Unity, and the LINE SDK for Flutter plugin. Use this skill whenever the task touches client-side LINE Login on a native app: installing the SDK (CocoaPods `LineSDKSwift`, Carthage, Maven Central `com.linecorp.linesdk:linesdk`, Unity `.unitypackage`, pub.dev `flutter_line_sdk`), configuring channel ID / bundle ID / package name / URL schemes, calling LINE Login, getting an access token / ID token, getting the user profile, logging users out, refreshing or verifying access tokens, enabling the add friend option (bot prompt) and checking friendship status, handling SDK errors, using universal links on iOS, or using the SDK from Objective-C. Also includes the full per-platform SDK class/method API reference — every class, interface, enum, property, method signa

LINE Login official reference at API-reference depth. Covers the entire LINE Login documentation section: the OAuth 2.0 authorization code grant flow, OpenID Connect (OIDC) integration, the web login flow, every authorization URL query parameter, every scope, every API endpoint, ID token (JWT) structure and verification, access/refresh token lifecycle, the add friend option, PKCE, security hardening, and both LINE Login v2.1 and the deprecated v2.0. Use this skill whenever the task touches social login with LINE accounts: integrating LINE Login into a web app or website, building the authorization request to access.line.me/oauth2/v2.1/authorize, handling the authorization code / state callback, exchanging the code for an access token at api.line.me/oauth2/v2.1/token, requesting the profile / openid / email scopes, verifying an access token, refreshing or revoking tokens, getting a user profile, decoding or verifying an ID token (iss / sub / aud / nonce / amr / exp), the userinfo endpoint, the friendship statu

LY Ads Network (LINEヤフー広告ネットワーク / formerly LINE Ads Network) official publisher / SDK reference at API-reference depth. Covers the FiveSDK mobile ad SDK for iOS and Android, the ironSource mediation adapter, and the publisher Dashboard plus its Reporting API. Use this skill whenever the task touches monetizing a mobile app with LY Ads Network: integrating or debugging the FiveSDK, displaying custom layout / banner / rectangle, video reward, interstitial, or native ad formats, loading ads with the legacy load API or the new AdLoader API, handling ad event callbacks (impression, click, error, reward, play, viewThrough, pause, fullScreen open/close), wiring App Tracking Transparency (ATT) and SKAdNetwork on iOS, configuring AndroidManifest and Google Play Data safety on Android, app-ads.txt, registering apps and slots, test devices, block settings and TargetCPM in the Dashboard, fetching reports via the Dashboard Reporting API, or mediating LY Ads Network through ironSource / LevelPlay / AdMob / GAM / MAX. Trigg

LINE MINI App official documentation at API-reference depth. Covers the complete LINE MINI App platform: building a web app that runs inside the LINE app as a LIFF app, the LINE MINI App channel and its three internal channels (Developing / Review / Published), the verification review that turns an unverified MINI App into a verified MINI App, and every LINE MINI App API. Use this skill whenever the task touches LINE MINI App: creating a LINE MINI App channel, configuring it in the LINE Developers Console, the built-in action button / dropdown menu / multi-tab view, implementing a custom action button with Flex Message share messages and the share target picker, sending service messages, Channel consent simplification and the authorization flow, Common Profile Quick-fill, in-app purchase (IAP), Custom Path, permanent links, adding a shortcut to the home screen, opening a LINE MINI App in an external browser, handling payments (LINE Pay / IAP), the verified-badge review and submission flow, or placing ads. Cov

Mini Dapp / Unifi Apps SDK official reference at API-reference depth — the DApp Portal documentation, now rebranded as Unifi. Covers the Unifi Apps SDK (`@linenext/dapp-portal-sdk`, class `DappPortalSDK`), the EIP-1193 wallet provider, the payment provider and Payment Server REST API, the event provider, Web3 gas-fee delegation, the Kaia blockchain, LINE MINI App / LINE Login LIFF / Web integration, NFT drops and rewards, and the Unifi Pay PG integration. Use this skill whenever the task touches LINE's Web3 / Mini Dapp ecosystem: integrating the Unifi Apps SDK or Mini Dapp SDK, building a Unifi App / Mini Dapp / LINE MINI App with crypto, connecting a Kaia wallet (Unifi Wallet, Kaia Wallet, OKX, Bitget), sending KAIA or USDT, signing transactions, creating in-app purchases (crypto / Stripe fiat / LINE IAP), handling payment webhooks (lockUrl, unlockUrl, paymentStatusChangeCallbackUrl), finalizing payments, settlement and chargebacks, gas-fee delegation, ERC-20 token balances, or onboarding/review of a Unifi A

LINE "Options for corporate customers" (partner-docs) official reference at API-reference depth. Covers every partner / corporate-only LINE Platform feature, endpoint, request/response schema, scope, and webhook event. Use this skill whenever the task touches LINE corporate / partner features: LINE notification messages (template or flexible) — sending messages by phone number with /v2/bot/message/pnp/templated/push or /bot/pnp/push, the delivery completion webhook event, phone-number SHA256 hashing, X-Line-Delivery-Tag; the Module / module channel system — attaching a module channel via the OAuth 2.0 flow, manager.line.biz/module/auth, Chat Control (Acquire/Release Control API, Active/Standby Channel, Default Active), the Detach API, module-specific webhook events (attached / detached / activated / deactivated / botSuspended / botResumed), calling the Messaging API from a module channel with the bot-user-ID header; the Mission Sticker API (/shop/v3/mission); LINE Profile+ (real_name / gender / birthdate / ph

LINE Pay developer documentation, official API reference at API-reference depth. Covers the Online API (v4, v3) and Offline API (v4, v2.4, v2) — every endpoint, request/response schema, parameter table, result code, the HMAC request-signing algorithm, and the merchant redirection pages. Use this skill whenever the task touches LINE Pay: building or debugging a LINE Pay integration for an online shop or an offline POS terminal, requesting / confirming / capturing / voiding / refunding a payment, implementing pre-approved (recurring / subscription) payments, generating the X-LINE-Authorization HMAC-SHA256 signature, handling channel ID / channel secret credentials, processing a customer's My Code (oneTimeKey), checking a payment request status, retrieving payment details, or wiring up the confirmUrl / cancelUrl redirection pages. Trigger on mentions of: LINE Pay, developers-pay.line.me, api-pay.line.me, sandbox-api-pay.line.me, LINE Pay Online API, LINE Pay Offline API, /v4/payments/request, /v4/payments/confir