13.6K skills · sorted by relevance
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
The English summary is being prepared. Showing the original description.
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.
The English summary is being prepared. Showing the original description.
Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.
The English summary is being prepared. Showing the original description.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
The English summary is being prepared. Showing the original description.
Rebase the current branch with flexible target options. Use when you need to rebase on main, a specific branch, or a remote branch, with intelligent conflict handling.
The English summary is being prepared. Showing the original description.
Bun runtime and modern JavaScript backend practices, including Bun-native tooling (bun run/test/build) and PostgreSQL usage guidance. Use when building or reviewing Bun-based services, APIs, scripts, or when Bun-specific workflow questions arise.
The English summary is being prepared. Showing the original description.
Read-only file search and codebase exploration specialist. Use when you need to find files by pattern, search code with regex, navigate unfamiliar codebases, or understand code architecture without making changes.
The English summary is being prepared. Showing the original description.
Multi-agent exploration and task delegation for complex areas of interest. Use when you need to deeply explore a codebase area, gather information from multiple perspectives, or delegate parallel research tasks for comprehensive analysis.
The English summary is being prepared. Showing the original description.
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.
The English summary is being prepared. Showing the original description.
UI runtime 驗證 SKILL — 刷新 Cocos asset-db、執行 validate-ui-specs.js、headless-snapshot-test.js、capture-ui-screens.js，並依環境選用 cocos-screenshot 或 cocos-preview-qa 檢查實際畫面殘差，回寫 generated-review / runtime-verdict。USE FOR: 修改 layout / skin / screen / content / Panel / UI 資產後的驗證收尾。DO NOT USE FOR: 純資產生成、無 target 的整專案大範圍探索。
The English summary is being prepared. Showing the original description.
UI 自動化生產總控 SKILL — 從 UI 示意圖、參考圖、Figma snapshot 或既有頁面經驗啟動，串接 proof draft、family-map、MCQ、normalized recipe、task shard、ui-spec 與 CompositePanel / ChildPanel scaffold、靜態驗證、Browser QA 自動調整，直到交付人類驗收。USE FOR: 想把一張新 UI 從「給圖」一路推進到可驗證的 screen package 與 QA 閉環。DO NOT USE FOR: 單純修一個 runtime bug、單一 prefab 微調、純美術資產委託。
The English summary is being prepared. Showing the original description.
UI brief 生成 SKILL — 從 docs/keep.summary.md、正式規格書、task shard、cross-reference-index 與參考圖整理成可執行的 UI brief 或 task-ready brief。USE FOR: 新 UI 畫面開工前、既有畫面補 task shard 欄位、需要收斂 family / proof / normalized recipe / content_contract / smoke_route。DO NOT USE FOR: 直接修改 ui-spec JSON、直接做視覺 QA。
The English summary is being prepared. Showing the original description.
UI 資產品質驗證 SKILL — 執行 validate-visual-assets.js、validate-ui-specs.js 與必要的 snapshot regression，對 skin family 資產、screen package、proof draft / family-map 進行全面驗證，並回寫 generated-review。USE FOR: 任何 UI 資產生成後、在 ui-preview-judge 前必須先通過的 QA 關卡。DO NOT USE FOR: debug runtime 崩潰（用 cocos-log-reader）、Layout 佈局調整（用 ui-vibe-pipeline）。
The English summary is being prepared. Showing the original description.
Strict routing mode for prompts prefixed with `(best)`. USE FOR: any turn where the user explicitly wants the safest, smallest-context, highest-discipline execution path. This skill must route into context-budget-guard first, then continue into the task-specific workflow.
The English summary is being prepared. Showing the original description.
EDITOR PREVIEW SCREENSHOT SKILL — Capture the current Cocos Creator Editor window to a PNG file and inspect exactly what is already visible inside the Editor. USE FOR: visual symptoms when the user already has the target screen open in Cocos Editor / Editor Preview. DO NOT USE FOR: browser-driven QA, automatic browser target switching, reference-image comparison pipelines, compile errors, or pure log analysis. If the user wants browser screenshots, remind them to prepare the Browser Review environment and use cocos-preview-qa instead.
The English summary is being prepared. Showing the original description.
Inspect a repository and emit a guidance orientation report.
The English summary is being prepared. Showing the original description.
DEBUGGING SKILL — Read and analyze Cocos Creator project.log for runtime errors, warnings, and stack traces. USE FOR: any bug report, crash, UI glitch, TypeError, null reference, missing asset, CompositePanel mount fail, ChildPanel route fail, or screen spec wiring error. Load this skill FIRST before any runtime debugging session. DO NOT USE FOR: compile errors (use get_errors tool instead).
The English summary is being prepared. Showing the original description.
通用任務開單器 SKILL — 統一建立或回寫 Markdown task card、docs/tasks/tasks-*.json 分片、UI quality shard，並強制遵守 docs/agent-briefs/Readme.md (doc_ai_0023) 與 docs/遊戲規格文件/系統規格書/名詞定義文件.md (doc_spec_0008) 的硬規則。USE FOR: 開任務卡、開單、task card、task shard、tasks-ui.json、tasks-prog.json、tasks-dc.json、tasks-data.json、agent-briefs/tasks、docs/tasks/*_task.md、UI pipeline 開卡。DO NOT USE FOR: 純 runtime 除錯、單純修改既有功能碼但不需要新卡、只做極小 typo 修補。
The English summary is being prepared. Showing the original description.
Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline. Use when writing, reviewing, or refactoring any Go code, especially code drifting toward Java/Spring shapes (deep layer trees, generic repositories, heavy frameworks) - even if the user never says "idiomatic". Distilled from spf13/go-skills and adapted to this repo.
The English summary is being prepared. Showing the original description.
Generate 5–10 business idea candidates from a blank page or a founder's domain context — using pain mining, jobs-to-be-done, trend × capability mapping, constraint relaxation, adjacency search, and founder-market-fit prompts. Each candidate is a structured idea card (segment, JTBD, current alternative, why-now, distribution wedge, monetisation, "feels like"). Load when the user asks to generate business ideas, brainstorm startup ideas, find ideas to work on, says "what business should I start", "give me startup ideas", "I don't know what to build", "ideate ventures", "blank-page idea generation", "find me a startup idea", "explore business opportunities". Sub-skill of `venture-exploration`. Hard-bans "Uber for X" / "AI for X" with no specific JTBD, "everyone" segments, and idea cards missing any of the 7 required fields. Does NOT design or evaluate ideas generated — for that use `idea-evaluation`.
The English summary is being prepared. Showing the original description.
Critically audit agent skills and remove content that is outdated, disproven, model-specific, or based on poorly cited sources. Load when improve-skills runs its per-skill cycle, when the user asks to prune skills, remove outdated techniques, check if skills are still valid, verify citations in skills, audit skill sources, or update skills for a new model release. Also triggers on "are these skills still valid", "check for obsolete techniques", "verify skill citations", or "update skills for GPT-5/Claude 4/Gemini 2". Runs before split-skill and compress-skill — removing bad content first means the remaining content is worth preserving.
The English summary is being prepared. Showing the original description.
Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.
The English summary is being prepared. Showing the original description.
Run a pre-mortem — imagine the project has already failed one year from now and work backward to find the root causes before they happen. Load when the user asks for a pre-mortem, wants to imagine failure before committing, asks "what could go wrong before we start", "assume this fails — why", "risk analysis before launch", "what kills this project", "what could go wrong", or when deep-thinking diagnoses a pre-mortem frame. Based on Gary Klein's prospective hindsight method, which surfaces failure causes more effectively than forward risk analysis. Most useful right before a major commitment.
The English summary is being prepared. Showing the original description.
Decompose tasks into structured, outcome-defined process entries with complexity triage. Load when user says "decompose this", "break this down", "what steps do I need", "plan this out", "what's the process for", "how do I approach this", or when any complex task needs structured execution planning. Includes a problem-understanding pass before complexity triage. Routes to `problem-to-plan` when the user needs planning deliverables (spec + plan + TODO). Does NOT replace brainstorming — brainstorming is design approval (upstream), this is execution planning (downstream).
The English summary is being prepared. Showing the original description.