mem-consolidate
Two-phase cleanup - normalize long filenames, then consolidate semantic duplicates using AI
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.
Adds docstrings, comments, and WHY/DECISION tags to code. Use when documenting functions/classes with language-specific standards (JSDoc, PEP 257, GoDoc).
Sets up Johnny.Decimal documentation system for projects. Use when initializing docs/ structure, creating JD categories, or organizing project documentation.
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.
Meta-skill for auditing and validating skill quality. Use when reviewing skills for consistency, completeness, accuracy, and adherence to standards. Provides structured rubrics, scoring frameworks, and actionable recommendations.
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.
Best practices for documenting APIs and code interfaces, eliminating redundant documentation guidance per agent.
Generate comprehensive analysis articles from Claude skills. This skill should be used when you want to analyze a skill from the Anthropic skills repository and create a detailed tutorial article explaining its structure, design patterns, and usage. Perfect for creating documentation, tutorials, and educational content about existing skills.
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".
Markdown documentation standards for LLM-optimized architecture including section numbering rules for Pandoc PDF generation. Use when writing markdown documentation, creating skills, or authoring content that may be converted to PDF.
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.
Generic ground truth documentation template for creating verifiable reference skills. Auto-invoke when user requests ground truth skill creation, validation criteria framework, or canonical documentation templates. Do NOT load during actual ground truth usage (use project-specific skills instead).