tomthebearded
UserTurns your own idea into a learn-as-you-go build guide: a Claude Code plugin that plans a gated milestone ladder and drafts atomic step files that explain every action where it happens.
Categories
Indexed Skills (10)
pre-pr-check
Pre-flight a contribution to the GuideForge repo before opening a PR — verify every CONTRIBUTING ground rule and PR-checklist item is respected, and that the repo is internally consistent (skill frontmatter valid, README/EXPLAINER skill list in sync, CHANGELOG updated, version stamps aligned, no dead links). Read-only: it reports PASS/FAIL with a checklist, it does not fix. Use right before you `git push` / open a PR against GuideForge. Invoke with no argument to check the current branch's diff, e.g. "/pre-pr-check", or name a base branch, e.g. "/pre-pr-check main".
clarify-step
Run the pedagogy pass over ONE existing step of a learn-as-you-go guide to remove confusion — without changing what the step does. Use when a step reads unclearly, a reader got stuck, or a term went undefined. Invoke with the step to clarify, e.g. "/clarify-step 03_first-route.md".
draft-milestone
Draft an approved learn-as-you-go build guide into folders of atomic, teaching step files — the WHOLE guide by default (every milestone, in one pass), or a single named milestone if one is given (for re-drafts/fixes). Use after a plan from the plan-guide skill has been approved. Invoke with no argument to draft the whole guide, or a milestone to draft just that one, e.g. "/draft-milestone M2". Honors the approved ladder, audience model, conventions, and pedagogy rules.
log-feedback
A reader hit friction while following a learn-as-you-go guide — capture it to the guide's feedback log WITHOUT changing the guide. Appends one dated, structured entry (where · reader · what happened · suspected class · severity · tags · quote) to guide/feedback-log.md, so friction becomes durable data for improving the guide and the GuideForge method later. Log-only: it does not diagnose or fix (that's /report-issue). Use when you want to record a reader's snag, confusion, or error without editing the guide yet. Invoke with the report, e.g. "/log-feedback M2/03 — reader confused by the token step, expected a value".
modernize-guide
Restructure an EXISTING flat tutorial / README / runbook / legacy guide into a learn-as-you-go GuideForge plan: reverse-engineer its implicit ladder, diagnose it against the pedagogy principles, verify its (likely stale) stack online, and re-cast it as a plan with a source-map. Use when the user has an existing guide/tutorial to modernize or convert — not a from-scratch idea (that's plan-guide). Invoke with the doc, e.g. "/modernize-guide README.md", attaching the source file(s) and any real target code.
plan-guide
Plan a learn-as-you-go, step-by-step developer build guide from a one-line idea. Use when the user wants to create a tutorial, course, onboarding doc, or build guide that TEACHES while it builds — for any domain (games, libraries, web, CLIs, APIs). Runs an audience interview, then produces a milestone-laddered plan. Invoke with the idea as the argument, e.g. "/plan-guide a REST API in Go".
report-issue
A reader hit a real issue while following a learn-as-you-go guide — report it and fix the guide so the issue can't recur. Diagnoses the root cause, fixes the step where they got stuck, then sweeps the WHOLE guide for every other place the same class of defect appears and fixes those too, adds a failure-note guard, logs it in status.md + decision-log.md, proposes a pedagogy rule if it's a general confusion, marks affected milestones for re-verification (never ✅), and hands off to audit-guide. Use when a reader got stuck, hit an error, or found something wrong following the guide. Invoke with the issue(s), e.g. "/report-issue M2/03 — npm run dev fails, needs .env first".
review-before-follow
Reconcile a learn-as-you-go guide (or one step) against reality BEFORE you execute it — catch stale APIs, moved files, renamed UI, missing prerequisites. Use right before acting on a guide written a while ago, or against a codebase/tool that may have moved. Invoke with the step to review, e.g. "/review-before-follow M2/03_persist.md", optionally attaching the real project files to check against.
scaffold-guide
Stamp the folder skeleton + five foundation docs (stack, status, glossary, conventions, decision-log) of a GuideForge guide from an approved plan, pre-filled from the plan and with a placeholder overview per milestone — so drafting can start immediately. Use after a plan is approved and before drafting the first milestone. Invoke with the plan, e.g. "/scaffold-guide", attaching PLAN.md.
update-stack
Re-verify a guide's framework/library versions online and bring the guide up to date. Re-checks each tool's latest stable version, rewrites stack.md, then scans the guide and rewrites ONLY the steps whose code/commands/APIs/doc-links the bump affects (using the new version's features), logs the drift in status.md + decision-log.md, refreshes the README Updates log, and hands off to audit-guide to QA the changes. Use when the user wants to update/bump framework or library versions in a guide. Invoke with the tools to bump (or none for all), e.g. "/update-stack" or "/update-stack Go modernc.org/sqlite".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.