Loading...
Loading...
Found 2,010 Skills
Human Made engineering principles and code quality standards. Apply when writing code, reviewing code, planning implementations, or discussing architecture. Covers code quality priorities, simplicity over complexity, and avoiding over-engineering.
Generates a full comprehensive status update of the project. Use when the user asks for a status update, progress report, "STATUS UPDATE", "WHAT'S THE STATUS", or wants to know what's done, what's broken, and what's next. Writes to docs/status/.
Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note. Writes explicit "None" style sections whenever the user does not provide details.
Patterns and conventions for creating a good PR
Add a linked resource (external file reference) to a ***plain spec. Use when the user wants to reference a JSON schema, API spec, data file, or other external file from within a functional spec, definition, or implementation requirement.
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.
bklit-ui monorepo contributors only — ship a chart or component from playground prototype to production in packages/ui with docs and registry.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.
Use when investigating and documenting a production incident, outage, data corruption event, or post-mortem — guides evidence collection during the investigation AND produces a rich, reproducible Root Cause Analysis report. Trigger on phrases like "write an RCA", "post-mortem for X", "document this incident", "what went wrong with...", "the pipeline broke yesterday, help me investigate", or any time the user is debugging a recently-resolved incident and wants a writeup. Also use proactively when the user finishes resolving an incident in-session and the resolution context is fresh — offer to capture it as an RCA before details fade.
Use when writing a new agent skill for the dogfooded-skills library — covers frontmatter spec, section structure, quality criteria, and antipatterns.