Zenobia000

Architecture-level code review using a three-phase smells → principles → fixes flow. Use when reviewing existing system architecture, identifying design debt, evaluating refactor candidates, or auditing module boundaries and dependencies. Complements sunnydata-code-review (line-level) and architect agent (greenfield design).

Find and fix WCAG 2.2 accessibility issues. Two modes — report (sweep a codebase or page, produce a prioritized written report, no edits) and fix (audit→edit→verify loop on a target). Prefers direct-CDP live-DOM auditing; falls back to a browser-MCP composition or HTML-string audits.

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.

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.

Expert UI/UX design guidance for unique, accessible interfaces. Use for visual decisions, colors, typography, layouts. Always ask before making design decisions. Use this skill when the user asks to build web components, pages, or applications.

解析使用者訊息中的自然語言日期時間，查詢 Google Calendar 空檔， 建立日曆事件並傳送預約確認。 適用時機：使用者想預約或安排時間，提及關鍵字如 預約、約時間、排時間、訂時間、安排、約一下、book、schedule、appointment、reserve， 或意圖明確為安排會面／服務時間。 不適用：查詢既有行事曆事件、修改／取消預約、週期性排程、 或無預約意圖的一般日期問題。 前置需求：已設定 Google Calendar API 認證。

根據 email-triage 分類結果草擬專業的電子郵件回覆，透過 Resend 發送（建議）或儲存為 Gmail 草稿（備用）。 在發送任何電子郵件之前需經由使用者確認 — 絕不自動發送。 使用時機：使用者想要回覆電子郵件，或提到如「幫我回這封信」、「回覆」、「幫我回」、「草擬回覆」、「reply to this email」、「draft a reply」、「reply」、「回覆第N封」、「幫我回所有詢價信」、「reply to all inquiries」等關鍵字，或是意圖明確為撰寫收到的電子郵件的回覆時。 不適用於：閱讀/分類電子郵件（請使用 email-triage）、發送新電子郵件（非回覆）、轉寄電子郵件、管理電子郵件設定，或修改現有草稿。 需求：草稿模式需要 Gmail API 憑證（gmail.readonly + gmail.compose）；Resend 模式需要設定 Resend MCP Server。

讀取 Gmail 收件匣中的未讀電子郵件，產生 AI 摘要，將其分類（詢價/支援/預約/垃圾郵件/其他），分配優先等級（高/中/低），並輸出結構化的分類清單。 使用時機：使用者想要檢查電子郵件，或提到如「看信」、「收信」、「信箱」、「有沒有新信」、「整理信箱」、「信件摘要」、「check email」、「inbox」、「email summary」、「triage」等關鍵字，或是意圖明確為檢視收到的電子郵件時。 不適用於：回覆電子郵件（請使用 email-reply-draft）、發送新電子郵件、修改/刪除電子郵件、管理電子郵件設定，或閱讀特定已知主旨的電子郵件。 需求：需要設定 Gmail API 憑證（gmail.modify + gmail.labels）。

從對話、表單、Email 中擷取客戶資訊，計算 Lead Score，寫入 CRM（Notion 或 Google Sheets），自動指派 follow-up 任務。 Use when: 使用者提及潛在客戶詢問、收到 lead、關鍵字如 客戶, 詢問, 潛在客戶, lead, 有人問, 新客, 有人來信, 客戶資料, CRM, 建立客戶, 記錄客戶。 NOT for: 查詢現有 CRM 資料（無新 lead 脈絡）、修改已進行的交易階段、產生報表、管理既有客戶關係。 Requires: Notion MCP 連線或 Google Sheets API 認證。

Telegram DM 客服的 fallback 處理器：比對 FAQ 知識庫自動回覆常見問題， 偵測升級觸發條件轉人工，透過 Telegram 通知負責人，並將對話記錄寫入 CRM。 Use when: 客戶透過 Telegram DM 提問，且未被其他 Skill 匹配時進入。 關鍵字：客服, FAQ, 常見問題, 自動回覆, 升級, 轉人工, customer service, support。 NOT for: 主動行銷推播、多群組廣播、語音/圖片處理、既有客戶關係管理。 Requires: TELEGRAM_BOT_TOKEN 與 NOTIFY_CHAT_ID 環境變數。

TRIZ Step 2+3 TC/PC/SF 解題管線。參數映射、矩陣查表、原理具體化、OZ-OT-Px 提取、分離策略、SF 標準解匹配。Use when technical contradictions need resolution through the full TC-to-PC-to-SF pipeline or SF-only fast channel.

TRIZ Step 1 功能建模。引導建立組件交互圖、SF 診斷、改善/惡化描述。Use when a system needs functional analysis and substance-field modeling before contradiction resolution.

TRIZ 工作流入口路由。自動偵測問題類型並路由到適當步驟（Step 0/1/2 或 SF-only），管理 session 狀態。Use as the main entry point for any TRIZ problem-solving session.

TRIZ Step 0 問題定向。使用 5Why、KT Is/IsNot、CECA 從症狀挖掘到可操作的因果節點，確定子系統和 TC 假設。Use when a problem symptom needs root cause analysis before TRIZ contradiction resolution.

TRIZ Step 4 驗證與複雜度檢查。判定解法為進化或補丁，產出工程規格書或技術債記錄。Use when TRIZ solution proposals need verification, complexity assessment, or downstream deliverable generation.

📄 VibeCoding Document Generator - 根據七問答案自動填充 VibeCoding 範本產出專案文檔

🎯 TaskMaster Context Writer - 自動將 Agent 報告強制寫入 .claude/context/ 目錄

Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.

Initialize a new project from the VibeCoding starter template. Sets up directory structure, CLAUDE.md, git, and optional GitHub remote.

Automatically detect and prevent dangerous operations, secret exposure, and main branch modifications.