This skill provides guidance for using Brave Search MCP to search the web. Use when searching for current information, news, articles, local businesses, or any web content. Supports both general web searches and location-based local searches.
Use when creating PRDs or PRPs to populate the Gotchas/Prior Failures section. Reads learning files from memory/learnings and matches entries based on file paths, keywords, or tags. Returns curated list suitable for PRD/PRP insertion.
Research WoW addon development topics using CLI tools, Blizzard UI source, and documentation. Covers API discovery, pattern research, and Ace3 usage. Use when investigating unfamiliar APIs, finding Blizzard patterns, or learning. Triggers: research, find, search, API, Blizzard UI, documentation, Ace3.
Skill（SKILL.md）の保守・更新・新規作成を対話で行い、整合性と検証手順を維持したまま反映する。Skill更新、skill update、Skillメンテナンス、Skill追加を依頼されたときに使用する。
Historical record of expert tips and learnings that have been integrated into the plugin skills. Consult this when patterns emerge or to understand the evolution of knowledge.
Context for Mechanic - the WoW addon development hub. Covers the CLI, MCP server, dashboard, in-game modules, and MechanicLib. Load this for deep understanding of Mechanic tooling. Triggers: mechanic, mech, cli, mcp, dashboard, tools, development hub.
Two-phase cleanup - normalize long filenames, then consolidate semantic duplicates using AI
First, determine the root cause of the reported bug. Then, create a clear, step-by-step plan for the bug fixing. Use this skill whenever a user reports a bug.
Access past architectural and technical decisions with their rationale. Contains decisions made over time with context, alternatives considered, and reasoning. Use when asked why something was decided, checking past rationale, understanding trade-offs, or reviewing architectural history. Triggers: why did we decide, past decision, rationale, what was decided, trade-offs, ADR.
Brief description of what this Skill does and when to use it. Include key technologies and scenarios.
Diagnose requirements problems and guide discovery of real needs and constraints. This skill should be used when the user asks to 'analyze requirements', 'clarify what to build', 'define the problem', 'scope a project', 'prioritize features', or needs help distinguishing stated wants from underlying problems. Keywords: requirements, problem statement, scope, constraints, needs, prioritization, MoSCoW, discovery.
Software engineering planning specialist that helps structure ideas into well-architected plans. Proactively asks questions to discover hidden requirements. Use when users provide unorganized thoughts, feature requests, todo lists, or need help planning work.
This skill should be used when the user says "brainstorm", "deep analysis", "let's think through", "analyze this with me", or "help me think through". Also used by /humaninloop:specify for input enrichment when feature descriptions lack Who/Problem/Value clarity. Provides progressive deep analysis through one-by-one questioning with 2-3 options per question and clear recommendations. Challenges disagreement to strengthen thinking and concludes with a synthesis document.
Guide AI-assisted learning that empowers learners while maintaining appropriate boundaries. Use when teaching, explaining concepts, or helping someone who is struggling to understand.
Act as an assistive outline coach who guides structural development through questions. Use when helping someone develop their own outline through diagnosis and frameworks. Critical constraint - never generate outline content. Instead ask questions, identify structural issues, suggest approaches, and let the writer structure.
Generate patent-style technical diagrams (flowcharts, block diagrams, system architectures) with automatic reference numbering.
Comprehensive description of what this skill does and when to use it. Include technologies, use cases, and any special requirements or dependencies.
Run a research-first, multi-perspective debate to explore complex technical decisions (trade-offs, architecture choices, integration strategies) using concrete codebase evidence. Use when the user asks to "debate" approaches, compare options, or needs a structured exploration before deciding.
Transform overwhelming development tasks into manageable units. This skill should be used when the user says 'task too big', 'can't estimate', 'overwhelmed by scope', 'where do I start', 'epic needs breakdown', or has dependency problems. Keywords: decomposition, breakdown, estimate, scope, INVEST, vertical slice, spike, dependencies.
Create Astro/Starlight MDX content pages. Use when the user says "write a new article", "add a blog post", "create content in Tech/Life category", or "add an MDX page".
This skill should be used when generating lesson summaries for educational content. It extracts key concepts, mental models, patterns, and common mistakes from lesson markdown files using a Socratic extraction process. Use this skill when a lesson file needs a `.summary.md` companion file, or when reviewing/refreshing existing summaries.
Semantic search over skill libraries using ColBERT embeddings. Use when: - "find a skill for..." or "search for skills that..." - "what skill handles..." or "which skill can..." - "index my skills" or "rebuild the skill index" - "show me relevant skills for this task"
