Loading...
Loading...
Found 8,087 Skills
Compound engineering loop — 5 stages to reduce rework. Use when: (1) starting new work (brainstorm); (2) planning implementation (plan); (3) writing code (work); (4) evaluating output (review); (5) capturing lessons (compound). NOT for: daily rhythm (use daily); task management only (use task).
Feishu (Lark) API Integration Guide. Use this when users request to "create Feishu apps", "manage base tables", "add collaborators", "generate Feishu reports", "set Feishu permissions" or "automate Feishu operations". Prioritize using MCP tools for real-time interactive operations.
Summarize code changes by author type and scope. Inputs are author and scope with product plus PR as defaults.
Curates insights from reflections and critiques into CLAUDE.md using Agentic Context Engineering
Comprehensive guide for skill development based on Anthropic's official best practices - use for complex skills requiring detailed structure
Reset the FPF reasoning cycle to start fresh
NEVER escalate without investigation first. This is the Iron Law. Use when evaluating whether to escalate models, facing genuine complexity requiring deeper reasoning, novel patterns with no existing solutions, high-stakes decisions requiring capability investment. Do not use when thrashing without investigation - investigate root cause first. DO NOT use when: time pressure alone - urgency doesn't change task complexity. DO NOT use when: "just to be safe" - assess actual complexity instead.
Merges valuable content into permanent documentation, then deletes source files. Use when you have untracked *_REPORT.md or *_ANALYSIS.md files, git status shows markdown artifacts that shouldn't be committed, preparing PR and need to clean up working artifacts, preserving insights from code reviews. Do not use when files are already in docs/ or skills/ locations. DO NOT use when: files are intentionally temporary scratch notes. DO NOT use when: source files have no extractable value.
Use when you need to generate `{FEATURE_DIR}/verification/report-{date}-{version}.md` (test report) during the verification phase of Spec Pack, provide deliverable conclusions that are traceable to test cases and defect references.
Generate Git branch names from staged or branch changes
Generate branch name, commit message, and PR content from one shared diff context
Use when you need to generate or update `{FEATURE_DIR}/verification/suites.md` (test suite) during the verification phase of Spec Pack, organize test cases into executable sets and define blocking rules and execution order.