Loading...
Loading...
Found 1,951 Skills
Set a tracking document as the source of truth for the current feature or task. Use when starting work on a feature, bug fix, or multi-step task that benefits from a persistent record of decisions, discoveries, and progress. Keeps the document updated as work proceeds.
Answer ZenMux questions by reading the latest official docs. Use for product features, APIs, integration, pricing, models/providers, routing, fallback, streaming, multimodal, structured output, tool calling, reasoning, prompt caching, image/video generation, web search, long context, observability, logs, cost tracking, subscriptions, PAYG, invoices, FAQ, privacy, terms, compliance, and tool guides for Claude Code, Cursor, Cline, Codex, Gemini CLI, opencode, Cherry Studio, Obsidian, Sider, Open-WebUI, Dify, and GitHub Copilot. Trigger on "ZenMux docs", "ZenMux API", "how to use ZenMux", "models", "pricing", "ZenMux 怎么用", "文档", "快速开始", "API 参考", "模型路由", "供应商路由", "订阅", "按量计费", "接入", "配置". Also use when ZenMux is the project context and the user asks about LLM API aggregation, model routing, or provider fallback.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Use when the user requests Chinese or Traditional Chinese output for responses, comments, docs, or localization, following Taiwan terminology (zh-Hant-TW/zh-TW/zh_TW).
Maintain comprehensive changelogs and release notes following Keep a Changelog format. Use when documenting version history, release notes, or tracking changes across versions.
Expert in requirements definition and system design. Converts abstract requirements into concrete specification documents (SPEC.md) and design documents (DESIGN.md), and visualizes system structures using Mermaid diagrams.
Create factual working journal entries in Notes/WorkingJournal/ after completing analysis work. Use when user asks to "summarize work", "document results", or "create working journal entry". Ensures code is committed, copies figures to attachments, and creates objective summaries with citations.
Creates comprehensive Technical Design Documents (TDD) following industry standards with mandatory sections, optional sections, and interactive gathering of missing information.
Use when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.
This skill should be activated when the user requests to "create PRD", "write product requirements document", "generate PRD", "new PRD" (either in Chinese or English), or mentions "product requirements document" or "PRD template". It automatically generates comprehensive Chinese PRD documents in accordance with 2026 best practices.
Technical writing skills specialized in drafting, structuring, and visualizing technical notes. Understand the essence from source code and official documents, and create explanatory articles in an engineer-friendly format.
Template for documenting co-built solutions, integrations, and GTM motions with partners.