Loading...
Loading...
Found 452 Skills
Analyzes changes since last release and updates CHANGELOG.md ONLY. Does NOT trigger releases.
Create concise, scannable quick-reference guides (50-100 lines) for technical topics. Use when developers need fast answers about project-specific paths, commands, and patterns. Triggers on "create cheat sheet", "quick reference guide", "where does X live", "what commands for Y".
Apply principles of good design taste when creating, reviewing, or critiquing any creative or technical work. Use this skill whenever the user asks you to design something, review a design, create UI/UX, architect a system, write something with aesthetic intent, evaluate the quality of code or creative work, or asks for feedback on whether something is "good." Also trigger when users mention taste, aesthetics, beauty in design, elegance, simplicity, or when they want help making something not just functional but genuinely well-crafted. This skill applies across domains: software, writing, visual design, architecture, presentations, APIs, data models, and more. Even if the user doesn't explicitly mention "design," use this skill when the underlying task is about making something better, more elegant, or more refined.
Explain English technical documents and text in Japanese with contextual understanding. Not a simple translator — reads the surrounding file or codebase context to provide deeper, more accurate explanations tailored for Japanese-speaking developers. Use when: "explain this English", "この英文を解説", "英語の解説", "en-explainer", "what does this mean", "この英文の意味", "英文を日本語で説明", "ドキュメントを解説", "README解説", "エラーメッセージの意味", "コメントの意味", "API仕様の解説", or when the user pastes English text and asks for explanation in Japanese. Also use when the user provides a file path and asks to explain specific English sections, or when they want to understand English code comments, error messages, config files, or technical documentation.
Three-stage code review protocol: spec compliance, code quality, and domain integrity. Activate when reviewing code, preparing PRs, assessing implementation quality, or checking that code matches requirements. Triggers on: "review this code", "prepare PR", "check implementation", "code quality", "does this match the spec".
Use when net revenue retention is below 110%, when churn patterns are reactive instead of predictive, when expansion revenue lacks systematic triggers, when onboarding fails to reach activation milestones, or when customer health scoring does not exist. Use when customer base is large enough for patterns (50-500 accounts) but retention is managed manually.
Diagnosis and repair guide for errors and failures including CI issues. Activate this guide when users mention something is broken, errors occur, things aren't working, CI failures, build errors, test failures, or pipeline issues. DO NOT use this guide for: successful builds, new feature implementation, or code reviews.
Navigates C3 architecture docs and explores corresponding code to answer architecture questions. Use when the user asks: - "where is X", "how does X work", "explain X", "show me the architecture" - "find component", "what handles X", "diagram of X", "visualize X" - "describe X", "list components", "trace X", "flow of X" - References C3 IDs (c3-0, c3-1, adr-*) <example> Context: Project with .c3/ directory user: "explain what c3-101 does and how it connects to other components" assistant: "Using c3-query to navigate the architecture docs." </example> <example> Context: Project with .c3/ directory user: "show me a diagram of the C3 architecture" assistant: "Using c3-query to generate an architecture overview." </example> DO NOT use for changes (route to c3-change). DO NOT use for pattern artifact management — listing, creating, updating refs (route to c3-ref). Requires .c3/ to exist.
Teaches learners to extract transferable design lessons from real-world codebases through critical evaluation and systematic exploration. Use when a learner wants to study existing code to learn patterns, architecture, or design decisions—not just understand what it does. Guides through navigation, pattern recognition, critical evaluation (deliberate choice vs. compromise), and lesson extraction. Triggers on phrases like "learn from this codebase", "study how X is implemented", "understand design patterns in Y", or when a learner wants to improve by reading real code.
TODO: Complete and informative explanation of what the skill does and when to use it. Include WHEN to use this skill - specific scenarios, file types, or tasks that trigger it.
Generates WAFFLES Declarations for social media posts — preemptive lists of what a post does NOT say. Use when users mention WAFFLES, ask for clarifications on their post, want to prevent misinterpretation, or request disclaimers for controversial/nuanced takes.
Check and validate MTHDS bundles for issues. Use when user says "validate this", "check my workflow", "check my method", "does this .mthds make sense?", "review this pipeline", "any issues?", "is this correct?". Reports problems without modifying files. Read-only analysis.