From arete
Generates structured markdown explanations of technical concepts using a fixed template with sections: What It Is, Why It Matters (tied to brainstorm), How It Works (diagrams/code), Trade-offs, Further Reading. Saves as dated files in context/teachings/.
npx claudepluginhub jesgarram/arete --plugin areteThe structured format for concept explanations. All sections are required. ```markdown --- concept: "{concept name}" date: YYYY-MM-DD context: "{one-line brainstorm context}" --- [1-2 paragraphs defining the concept. Be precise, not academic. Use concrete examples.] [Connect to the current brainstorm. Why should the user care about this concept RIGHT NOW? Reference the specific problem or decis...Generates deep-dive markdown explanations of concepts with mermaid diagrams tailored to brainstorm phase context. Writes to context/teachings/{filename}.md and returns brief notification.
Generates clear, structured API documentation, user guides, tutorials, and developer docs. Transforms complex technical concepts into accessible content with examples, error handling, and best practices.
Explanation writer agent producing Diataxis methodology docs for conceptual understanding. Crafts discursive prose illuminating why things work, cross-topic connections, and multiple perspectives. Delegate for 'why' questions.
Share bugs, ideas, or general feedback.
The structured format for concept explanations. All sections are required.
---
concept: "{concept name}"
date: YYYY-MM-DD
context: "{one-line brainstorm context}"
---
# {Concept Name}
## What It Is
[1-2 paragraphs defining the concept. Be precise, not academic. Use concrete examples.]
## Why It Matters
[Connect to the current brainstorm. Why should the user care about this concept RIGHT NOW? Reference the specific problem or decision being discussed.]
## How It Works
[The mechanics. Break down into steps, components, or layers as appropriate.]
[Mermaid diagram if component interactions exist]
[Code snippet if implementation pattern helps]
## Trade-offs
**When to use:**
- [Scenario 1]
- [Scenario 2]
**When to avoid:**
- [Scenario 1]
- [Scenario 2]
**Common pitfalls:**
- [Pitfall 1]
- [Pitfall 2]
## Further Reading
- [Authoritative source 1](URL)
- [Practical guide 2](URL)
- [Deep dive 3](URL)
{YYYY-MM-DD}-{concept-slug}.mdcontext/teachings/domain-driven-design, event-sourcing)