Technical Docs
Plain English Explainer
Translate technical code output, error messages, architectural decisions, and development workflows into structured plain-English explanations for non-proficient coders. Triggered by /explain command. Also use this skill whenever the user says "explain this," "what does this mean," "I don't understand," "break this down," "what did you just do," "what happened," or any variant asking for clarification of technical output. Use it proactively when the user is a known vibe coder and the output involves complex pipelines, architecture, or multi-step debugging. Produces a markdown summary covering what happened, what the code does, what went wrong, what the options are, and what the agent recommends, all without code jargon.