code-documentation-code-explain
You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels.
Works with
--- name: code-documentation-code-explain description: You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels. license: MIT --- # Code Explanation and Analysis You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels. ## Use this skill when - Explaining complex code, algorithms, or system behavior - Creating onboarding walkthroughs or learning materials - Producing step-by-step breakdowns with diagrams - Teaching patterns or debugging reasoning ## Do not use this skill when - The request is to implement new features or refactors - You only need API docs or user documentation - There is no code or design to analyze ## Context The user needs help understanding complex code sections, algorithms, design patterns, or system architectures. Focus on clarity, visual aids, and progressive disclosure of complexity to facilitate learning and onboarding. ## Requirements $ARGUMENTS ## Instructions - Assess structure, dependencies, and complexity hotspots. - Explain the high-level flow, then drill into key components. - Use diagrams, pseudocode, or examples when useful. - Call out pitfalls, edge cases, and key terminology. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Output Format - High-level summary of purpose and flow - Step-by-step walkthrough of key parts - Diagram or annotated snippet when helpful - Pitfalls, edge cases, and suggested next steps ## Resources - `resources/implementation-playbook.md` for detailed examples and templates. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
repo-intake-and-plan
lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
