Explains code and subsystems by combining how and why skill findings into plain explanations.
npx skills add https://github.com/edivad1999/stuc-stack --skill teach-edivad1999
Please help me install this Agent Skill. Skill: teach Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/teach Command: npx skills add https://github.com/edivad1999/stuc-stack --skill teach-edivad1999
how and why skills in parallel to gather how the work functions and why it was built that way, then weaves the findings into one account. - Audience-calibrated depth: Chooses the few key takeaways based on why the person is asking (about to change it, reviewing it, debugging it, new to it) and what they already know. - Progressive visual teaching: Builds understanding diagram by diagram, adding one part per step, using mermaid for flows and generated whiteboard-style images for spatial ideas. - Use Case: A developer joining a team asks "teach me how the chat virtualization works" and receives a plain, layered explanation of the rendering and disk-loading mechanisms, with offers to go deeper. ## Quick Start Ask the assistant to teach you how a specific subsystem or recent change in this repository works and why it is built that way.High-intent search queries and answers about installing and using this skill.
Ask to be taught how the subsystem works and why it is built that way. The skill runs the how and why investigations, then blends the findings into one plain explanation calibrated to what you already know.
Request an explanation of the change scoped to your review goal. The skill reads the code for orientation, runs targeted how and why passes, and leads with the few things you should walk away understanding.
No, the goal is understanding, not changing anything. It investigates through the how and why skills and delivers only the explanation, with offers to go deeper at the end.
Use it when you need the reasoning and mechanism, not just the code listing: before modifying a subsystem, when new to a codebase, or when debugging behavior you cannot explain. Direct reading suits quick lookups of specific functions.
The hedges come from the why skill's findings and are preserved deliberately, since they record how certain the historical reasoning is. They are findings about the code's rationale, not stylistic choices.
alastor0325Retrieve prior Firefox Knowledge Wiki context before code search.
cursorExplains code and subsystems plainly by combining how and why skill investigations.
semantica-agiGenerate human-readable explanations for Semantica decisions and graph reasoning.
NeKon69Reference Lazygit.nvim Vim commands and Lua module functions for Git operations.