c3f43d8b61
- Add 60 new agents across all 10 categories (75 -> 135) - Add 95 new plugins with command files (25 -> 120) - Update all agents to use model: opus - Update README with complete plugin/agent tables - Update marketplace.json with all 120 plugins
1.5 KiB
1.5 KiB
Explain a code file, function, or concept in clear, structured language.
Steps
- Read the target code (file path, function name, or code block).
- Determine the audience level from context (junior, mid, senior, non-technical).
- Analyze the code structure:
- Purpose: What problem does this code solve?
- Inputs: What data does it receive and from where?
- Processing: What transformations or logic does it apply?
- Outputs: What does it produce or modify?
- Side effects: What external state does it change?
- Break down complex sections:
- Explain algorithms step by step.
- Clarify language-specific idioms or patterns.
- Describe the data flow through the code.
- Identify design patterns in use (Observer, Strategy, Factory, etc.).
- Note any non-obvious behavior, gotchas, or edge cases.
- Provide analogies for complex concepts when appropriate.
Format
## <File/Function Name>
### Purpose
<one-sentence summary>
### How It Works
1. <step-by-step explanation>
### Key Concepts
- <pattern/concept>: <explanation>
### Gotchas
- <non-obvious behavior to be aware of>
### Dependencies
- <what this code depends on>
- <what depends on this code>
Rules
- Explain the "why" not just the "what"; anyone can read the code.
- Use concrete examples with real values from the codebase.
- Avoid jargon unless explaining it; match the audience level.
- Keep explanations under 100 lines; link to deeper resources for complex topics.
- Do not restate code as prose; explain the intent and reasoning behind it.