Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From doc-generator
Explains code in plain language with architecture diagrams. Use when the user asks to understand how code works, needs onboarding help, or wants a high-level explanation of a module or system.
npx claudepluginhub walis85300/marketplace --plugin doc-generatorHow this skill is triggered — by the user, by Claude, or both
Slash command
/doc-generator:explain-codeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When explaining code, follow this structure:
Explains code using visual diagrams, analogies, and step-by-step walkthroughs. Use when teaching a codebase or answering 'how does this work?'
Explains complex code, algorithms, and system architectures through clear narratives, diagrams, and step-by-step breakdowns for developers at all levels.
Explains complex code using narratives, Mermaid diagrams, and step-by-step breakdowns. Ideal for algorithms, design patterns, functions, and walkthroughs.
Share bugs, ideas, or general feedback.
When explaining code, follow this structure:
Start with a single sentence explaining what this code does at the highest level.
Describe the key components and how they interact. Use a text-based diagram if there are 3+ components:
[Component A] --> [Component B] --> [Component C]
| ^
+---> [Component D] ---------------+
List the 3-5 most important concepts someone needs to understand to work with this code. Avoid jargon — explain terms the first time you use them.
Trace how data moves through the system for the most common operation. Use numbered steps.
Identify where and how a developer would typically add new functionality.
Adjust depth based on what was asked. If the user asks about a single function, keep it brief. If they ask about a whole module or system, go deeper.