bug
Create a plan for fixing a bug
Discover devops knowledge base skills, compare source repositories and read the instructions for each workflow.
Create a plan for fixing a bug
Project documentation with MkDocs Material - consistent structure, API auto-generation, GitHub Pages deployment
Hierarchical machine-readable documentation - root CLAUDE.md with module index, per-module CLAUDE.md for significant modules
Find and fix bugs systematically. Use when encountering errors, test failures, or unexpected behavior. Hypothesis-driven debugging to locate root causes and implement minimal fixes.
Generates comprehensive documentation including README, docstrings, and API docs. Use when creating documentation, writing README files, or adding code comments.
Systematic debugging approach for identifying and fixing issues. Use when debugging, troubleshooting errors, or asking about bugs and problems.
Multi-disciplinary strategy council with 5 expert personas. Use for strategic analysis, impact assessment, complex decisions requiring diverse expertise. Includes cross-examination to identify contradictions be...
Tree of Thoughts exploration for brainstorming and finding unknown unknowns. Recursively branches hypotheses, ranking by NOVELTY not probability. Use for idea generation, creative unblocking, exploring possibil...
Adversarial research validation using Red Team/Blue Team methodology. Use when researching complex topics, fact-checking claims, or producing research reports. Validates outputs through Gemini 3 Pro critic befo...
3x3 Parallel Debate system for high-confidence research. Spawns 9 agent instances (3 Proposer/Skeptic/Judge cohorts) to argue, critique, and adjudicate claims. Use for complex queries, controversial topics, or...
Guidelines for clear technical writing and documentation.
Surface emergent patterns and insights from the AI-ready vault memory system. Use periodically to discover connections between memories, identify recurring themes, and generate meta-insights that aren't obvious...
Search the AI-ready vault memory system by keyword or concept. Use when needing to retrieve previously stored information, find past decisions, or locate relevant context from earlier sessions.
Writes feature specification documents from user requirements. Use when asked to write a spec, create a spec, draft a feature spec, or document a new feature.
Writes feature specification documents from user requirements. Use when asked to write a spec, create a spec, draft a feature spec, or document a new feature.
Explore codebase, understand architecture, find how things work. Navigate unfamiliar repositories, discover code structure, find where functionality lives by intent rather than exact text. NOT for debugging fai...
This skill should be used when the user asks to "create a skill", "write a skill", "build a skill", "author a skill", "improve a skill description", "make my skill better", or needs guidance on skill structure,...
Initialize a new problem tree for recursive problem solving. Use when the user wants to set up a new problem to solve using the tree decomposition approach.
Personalize textbook chapter content for logged-in users based on their background, preferences, and learning style collected during signup.
Manage development and content logs for Hugo static sites. Use this skill when working with Hugo websites to track changes, add log entries for code modifications or content updates (posts, tutorials, projects)...
Understanding and using StickerNest's self-improving AI system. Use when the user asks about AI self-improvement, prompt versioning, reflection loops, AI evaluation, auto-tuning prompts, or the AI judge system....
Expert guidance for clue workspace coordination. Use when working in a directory with .clue/, when multiple Claude sessions need coordination, or when managing repositories in a shared workspace.
OpenAI Codex CLIでタスクを実行し、Claude以外の視点を得る。 コードレビュー、設計分析、実装提案でセカンドオピニオンが欲しいときに使用。 Use for: "codexで見て", "別の視点で", "Codexにレビューさせて", "OpenAIの意見...
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects the agent ('No, that's wrong...', 'Actually...'), (3) Use...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.