菜单
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Applies TDD methodology to skill documentation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Turn a prompt or an existing image into a polished multi-scene cinematic short video using Seedance for clip generation, uguu.se for file hosting, and FFmpeg for last-frame extraction and crossfade stitching. Supports two modes — PARALLEL (multiple scenes from the same reference image, concurrent, ~3 min total) and CHAIN (each scene starts on the last frame of the previous scene, sequential, ~3 min per scene, produces one continuous long take). Use this skill whenever the user wants to "make a video from an image", "animate this picture", "generate video scenes", "create a cinematic short", "stitch AI videos together", "make a long continuous video", "chain AI clips", or any workflow that goes from one reference image to a multi-clip stitched video. Also trigger when the user mentions Seedance, image-to-video, video stitching, crossfades between clips, frame chaining, last-frame continuity, or wants to turn a generated image into motion. Covers the full pipeline end-to-end — generate image with the chat-level
Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric/mathematical content.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
| name | skill-authoring |
| description | Use when creating new skills, editing existing skills, or verifying skills work before deployment. Applies TDD methodology to skill documentation. |
Writing skills IS Test-Driven Development applied to process documentation.
You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes).
Core principle: If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.
REQUIRED BACKGROUND: You MUST understand superpowers:test-driven-development before using this skill.
A skill is a reference guide for proven techniques, patterns, or tools. Skills help future Claude instances find and apply effective approaches.
| TDD Concept | Skill Creation |
|---|---|
| Test case | Pressure scenario with subagent |
| Production code | Skill document (SKILL.md) |
| Test fails (RED) | Agent violates rule without skill (baseline) |
| Test passes (GREEN) | Agent complies with skill present |
| Refactor | Close loopholes while maintaining compliance |
Create when:
Don't create for:
Frontmatter (YAML):
name: Use letters, numbers, and hyphens onlydescription: Third-person, describes ONLY when to use (NOT what it does). Start with "Use when..."Critical: Description = When to Use, NOT What the Skill Does.
Testing revealed that when a description summarizes the skill's workflow, Claude may follow the description instead of reading the full skill content.
Write skill before testing? Delete it. Start over. Edit skill without testing? Same violation.
No exceptions.
Creating skills IS TDD for process documentation. Same Iron Law: No skill without failing test first. Same cycle: RED (baseline) → GREEN (write skill) → REFACTOR (close loopholes).