Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From learning-guide
Use when the user asks to "create a learning guide", "make an interactive tour", "generate onboarding doc", "build a learning module", or any variant of turning an artifact (codebase, planning session, refactor plan, design doc) into an interactive HTML guide. Dispatches to learning-guide:analyze for new tours or learning-guide:render for re-renders after spec edits. Also use when the user is uncertain which step they need.
How this skill is triggered — by the user, by Claude, or both
Slash command
/learning-guide:learning-guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Discoverability shim. Decides whether the user needs to start fresh (analyze) or re-render an existing spec (render).
Discoverability shim. Decides whether the user needs to start fresh (analyze) or re-render an existing spec (render).
Does a tour-spec.json already exist at the target path?
learning-guide:render), update spec (dispatch learning-guide:analyze in update mode), or regenerate from scratch (dispatch learning-guide:analyze after deleting the spec).learning-guide:analyze.Does the user want to manually edit tour-spec.json and just re-render?
node "${CLAUDE_PLUGIN_ROOT}/scripts/render.cjs" tour-spec.json directly. They don't need to invoke any skill for that.analyze or render — let those run.learning-guide:render's references (renderer-cli.md, browser-compatibility.md).Always state which skill you're about to dispatch and why, in one sentence, before invoking it.
npx claudepluginhub dmitriyyukhanov/claude-plugins --plugin learning-guideGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.