wayne930242

Detects project languages and monorepo state, runs language-appropriate static analysis (dependency graph, complexity, duplication, semantic patterns), and produces a refactor map ranking hotspots. Use when user invokes /aref or explicitly asks to analyze a codebase for refactoring.

Executes a refactor plan phase-by-phase on a dedicated branch with per-phase commits and mandatory reviewer checkpoints. Use when characterization-tests scaffold is complete and plan has phases ready to execute.

Writes AGENTS.md per subproject, archives run artifacts, and suggests rcc handoff conditionally. Use when verifying-refactors passes (PASS or PASS-WITH-WEAK-TESTS).

Converts a refactor map into a phased plan using parallel-change, branch-by-abstraction, or strangler fig patterns. Use when user has approved the refactor map from analyzing-codebases.

Adds golden/snapshot tests to untested hotspot modules before refactoring. Use when refactor plan marks any phase with characterization_test.status=must-scaffold.

Validates hard structural rules (no cycles, file/fn line caps, cognitive/cyclomatic complexity) and runs mutation testing on touched modules. Use when applying-refactors has completed all phases on the refactor branch.

Validates component-type choices for agent system work, classifying knowledge as CLAUDE.md vs rule vs skill vs agent vs hook and checking for conflicts. Use when starting any skill/agent/rule workflow to validate approach. Use when classifying knowledge type. Use when checking for component conflicts.

Scans project structure and agent system components, runs 11-category weakness analysis, and produces actionable restructuring recommendations. Use when analyzing an existing agent system for weaknesses. Use when user says "analyze agent system", "check agent setup", "audit agent config". Use when called by migrating-agent-systems or refactoring-skills.

Use when translating game content that requires cost-optimized model routing, linear workflow efficiency, and immediate formatting to avoid multi-loop review cycles

Use when high-quality translation is needed with multi-agent review and quality gates before overwriting source files.

Use when a markdown draft or docs page must be checked for structural validity and documentation style compliance before writeback or publishing.

Use when high-quality translation is needed with multi-agent review and quality gates before overwriting source files.

Use when extracted rulebook markdown needs to be split into semantic documentation files and navigation. Trigger this skill from `init-doc`, future append/add-document flows, or whenever regenerated `_pages.md` source invalidates the existing chapter map. Do not use this skill for temporary translation chunking; that belongs to a separate draft-only translation workflow.

Use when performing final quality checks before publishing the documentation site. Use when all translation is complete and you need to verify titles/descriptions are translated, check for misplaced or erroneous content, and run page-reference link checks.

Use when translating in bilingual mode — produces Chinese primary + English blockquote markdown. Single-pass, no multi-round review. Requires translation_mode=bilingual in style-decisions.json.

Use when translating one file, one section, or all docs with glossary and style constraints.

Use when starting project code-improvement work — refactoring, architecture improvement, cleanup of an existing codebase — or when a grilling session should leave docs behind. Runs the interview and records decisions as ADRs and domain terms in CONTEXT.md as they crystallise.

Use when the user requests development work — implementing a feature, debugging an error, designing an approach, or deploying a release. MUST be invoked as the entry point before any implementation, debugging, or design sub-skill.

Use when the user names final QA as the goal — pre-release verification, "上線前驗證 / 最終品質保證".

A relentless interview to sharpen a plan or design.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Use when the user asks to check, audit, or review something thoroughly. Builds a check plan, then verifies each item with the investigating skill.

Use when the user asks to research or investigate a question, claim, or topic in depth. Comprehensive investigation with current information, every claim traceable to a source.

Use when the user asks an explanatory question — what is, how does, why, compare. Builds the user's mental model rather than dumping facts.

缺漏校對 - 檢查規則完整性

一致性校對 - 檢查術語使用是否一致

Initial summary - initialize the document translation project, build glossary and chapter structure

Create a new project from template and set up a GitHub repo (public or private)

PDF 遊戲規則轉換與翻譯流程。Use when processing PDF files, extracting content, splitting chapters, or translating game documentation.

用語權衡 - 術語選擇與全文替換

術語互動管理與一致性檢查。Use when creating/editing glossary terms, reading terms with site-wide validation, or making terminology decisions.

Start translation - translate a specified section or file

Use when performing final quality checks before publishing the documentation site. Use when all translation is complete and you need to verify titles/descriptions are translated, check for misplaced or erroneous content, and run page-reference link checks.

Use when high-quality translation is needed with multi-agent review and quality gates before overwriting source files.

Use when extracted rulebook markdown needs to be split into semantic documentation files and navigation. Trigger this skill from `init-doc`, future append/add-document flows, or whenever regenerated `_pages.md` source invalidates the existing chapter map. Do not use this skill for temporary translation chunking; that belongs to a separate draft-only translation workflow.

Use when initializing a translation project from extraction through glossary, chapter mapping, and progress tracking.

Use when high-quality translation is needed with multi-agent review and quality gates before overwriting source files.

Use when translating one file, one section, or all docs with glossary and style constraints.

第一次使用時建立健康基本檔案。透過友善問答收集使用者的基本資料、身體數據、飲食習慣、病史與傷史，儲存後由運動科學家進行初始分析。

建立或更新今日健康日誌。支援記錄心情、健身、飲食、睡眠感受等。每天只有一份日誌，會自動合併到同一天的檔案中。

健康計劃週度審查。從三位後台專家的角度（營養、訓練、科學數據）綜合分析近期健康狀況，給出平衡的建議與下週重點。使用獨立 context 執行，避免干擾主對話。

生成個人化訓練飲食菜單。支援單日（1d）、週計劃（1w）、月計劃（1m）。根據健康檔案、Garmin 數據，由健身教練和營養師合作規劃，並用腳本輸出格式化 Markdown 菜單。

UI/UX design intelligence. 67 styles, 96 palettes, 56 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

Use when the user mentions Linear or Trello issues, references issue IDs like MP-123, or asks to sync, show, start, complete, create, assign, edit, cancel, comment on, or check status of tasks.

Use when the user asks to prepare, cut, ship, or tag a cc-dispatch release. Trigger phrases include "prepare release", "cut release", "tag v0.X", "new version", "ship a release", "/releasing". Argument is the target version (e.g. `v0.2.0`).