learn-guidance
About
The learn-guidance skill enables Claude to act as a structured learning coach for developers. It assesses a user's knowledge, creates a tailored learning path, and guides them through material with adaptive testing and spaced repetition planning. Use this skill when starting a new technology, feeling overwhelmed by documentation, or needing to bridge knowledge gaps between domains.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/learn-guidanceCopy and paste this command in Claude Code to install this skill
Documentation
Learn (Guidance)
Guide person through structured learning process for new topic, technology, or skill. AI acts as learning coach — helps assess starting knowledge, plan study path, walk through material at right pace, test understanding with questions, adapt approach based on feedback, consolidate for retention.
When Use
- Person wants to learn new technology, framework, language, or concept. Doesn't know where to start
- Someone overwhelmed by documentation or learning resources. Needs structured path
- Person keeps forgetting material. Needs spaced repetition guidance
- Someone transitioning between domains (e.g., backend to frontend). Needs gap analysis
- Person wants accountability and structure for self-directed learning
- After
meditate-guidancecleared mental noise, creating space for focused learning
Inputs
- Required: What person wants to learn (topic, technology, skill, concept)
- Required: Their purpose for learning (job requirement, personal interest, project need, career change)
- Optional: Current knowledge level in this area (self-assessed or demonstrated)
- Optional: Time available for learning (hours per day/week, deadline if any)
- Optional: Preferred learning style (reading, hands-on, video, discussion)
- Optional: Prior failed attempts at learning this topic (what did not work before)
Steps
Step 1: Assess — Determine Starting Position
Before designing learning path, understand where person currently stands.
- Ask about their experience with topic: "What do you already know about X?"
- Ask about adjacent knowledge: "What related topics are you familiar with?" (these become bridges)
- They claim some knowledge? Ask calibration question that reveals depth vs. surface familiarity
- Note their vocabulary: do they use domain terms correctly, approximately, or not at all?
- Identify learning goal specifically: "After learning this, what do you want to be able to do?"
- Identify primary motivation: curiosity, practical need, career advancement, creative project
Starting Position Assessment:
┌───────────────┬────────────────────────────┬──────────────────────────┐
│ Level Found │ Indicators │ Path Approach │
├───────────────┼────────────────────────────┼──────────────────────────┤
│ No exposure │ No vocabulary, no mental │ Start with "what" and │
│ │ model, everything is new │ "why" before "how" │
├───────────────┼────────────────────────────┼──────────────────────────┤
│ Surface │ Has heard terms, no hands- │ Fill vocabulary gaps, │
│ awareness │ on experience, vague model │ then move to hands-on │
├───────────────┼────────────────────────────┼──────────────────────────┤
│ Partial │ Some experience, gaps in │ Identify specific gaps │
│ knowledge │ understanding, can do some │ and target them directly │
│ │ things but not others │ │
├───────────────┼────────────────────────────┼──────────────────────────┤
│ Refresher │ Knew it before, now rusty │ Quick review + practice │
│ needed │ │ to reactivate knowledge │
└───────────────┴────────────────────────────┴──────────────────────────┘
Got: Clear picture of person's starting position, goal, constraints. Assessment warm and encouraging, not like exam — frame questions as curiosity about their background.
If fail: Person cannot articulate current level? Ask them to describe recent attempt to use or understand topic. Concrete stories reveal level more accurately than self-assessment. Embarrassed about level? Normalize: "Everyone starts somewhere — knowing where you are helps me design best path for you."
Step 2: Plan — Design Learning Path
Create structured path from current position to goal.
- Break topic into 4-7 learning milestones (not too granular, not too vague)
- Order milestones by dependency: what must be understood before what?
- For each milestone, identify core concept (what they need to understand) and core skill (what they need to be able to do)
- Estimate time per milestone based on their available hours
- Identify first milestone — this is where learning begins
- Build in early wins: first milestone achievable quickly to build momentum
- Present path visually: numbered list with brief descriptions
Got: Learning path person can see and understand. Feels manageable — not overwhelming. Person can point to any milestone and understand why it is there.
If fail: Path feels too long? Goal may be too ambitious for available time — discuss scope reduction. Path feels too short? Topic may be simpler than expected — or milestones too coarse, need decomposition.
Step 3: Guide — Walk Through Material
For each milestone, guide person through material at right pace.
- Introduce milestone concept with brief overview: "In this section, we will learn X, which lets you do Y"
- Present material in small chunks — one concept per chunk
- Use person's preferred learning style: reading → provide text. Hands-on → provide exercises. Discussion → use Socratic questioning
- Connect each new concept to something they already know (from assessment)
- Provide concrete examples before abstract definitions
- Using documentation? Guide them through relevant sections rather than sending them off to read alone
- Pause after each chunk: "Does this make sense so far?"
Got: Person progresses through material with comprehension, not just exposure. Can explain each concept in own words before moving to next. Pace feels right — not rushed, not dragged.
If fail: Struggling? Slow down, check for missing prerequisites. Breezing through? Speed up — do not waste time on what they already grasp. Material itself confusing (bad documentation)? Provide clearer explanation, note resource quality for future reference.
Step 4: Test — Check Understanding
Verify learning with questions that require application, not just recall.
- Ask prediction questions: "What would happen if you changed X?"
- Ask comparison questions: "How is this different from Y, which you learned earlier?"
- Ask application questions: "How would you use this to solve Z?"
- Ask debugging questions: "This code has bug related to what we just learned — can you spot it?"
- Celebrate correct answers specifically: "Yes — and reason that works is..."
- Incorrect answers? Explore their reasoning: "Interesting — walk me through your thinking"
- Never frame incorrect answers as failure — they are diagnostic information
Got: Testing reveals whether person has working mental model or surface-level recall. Working models handle variations. Surface recall cannot. Testing feels like collaborative exercise, not exam.
If fail: Person cannot answer application questions? Learning was too passive — needs hands-on practice before more material. Answers recall questions but not application questions? Concepts understood individually but not integrated — focus on connections between concepts.
Step 5: Adapt — Adjust Path
Based on test results and person's feedback, adjust learning path.
- Milestone easy? Consider combining with next one, or deepening content
- Milestone hard? Break into smaller steps, or add prerequisite review
- Person's interest shifts during learning? Adjust path to follow curiosity where possible — engagement drives retention
- Fatigued? Suggest break and review session later rather than pushing through
- Particular teaching approach not working? Try different modality (switch from reading to doing, or from abstract to concrete)
- Update learning path, communicate changes: "Based on how this went, I suggest we adjust..."
Got: Learning path evolves based on real data. No fixed curriculum survives contact with actual learner — adaptation is the value.
If fail: Repeated adaptations still leave person struggling? May be fundamental prerequisite gap not caught in assessment. Return to Step 1, probe deeper. Person losing motivation? Discuss original goal — sometimes adjusting goal more appropriate than changing path.
Step 6: Review — Consolidate and Plan Next Session
Solidify what was learned. Set up for continued learning.
- Summarize what was covered: "Today we learned X, Y, and Z"
- Ask them to state key takeaway in own words
- Provide brief practice exercise for independent work (not homework — optional reinforcement)
- Recommend 2-3 resources for further exploration (documentation, tutorials, examples)
- Using spaced repetition? Schedule review points — "Review these concepts again in 2 days, then in a week"
- Set up next milestone: "Next time, we will tackle..."
- Ask for feedback: "What worked well? What could I do differently?"
Got: Person leaves with clear understanding of what they learned, what they can practice, what comes next. Session has clean closing, not abrupt stop.
If fail: Person cannot state key takeaway? Session covered too much or too little stuck. Identify one concept that most needs reinforcement, focus review on that. No motivation for independent practice? Learning path may need to be more self-contained (all learning within sessions).
Checks
- Starting position assessed before learning path designed
- Learning path has clear milestones ordered by dependency
- Material presented in small chunks with comprehension checks between them
- Testing used application questions, not just recall
- Path adapted at least once based on person's actual progress
- Session ended with summary, practice suggestion, next steps
- Person felt encouraged throughout, not tested or judged
Pitfalls
- Information dumping: Providing all material at once instead of pacing through milestones. Overwhelm kills learning
- Skipping assessment: Assuming person's level instead of checking. Frontend expert learning backend may know adjacent concepts but not ones you expect
- Teaching to average: Person faster or slower than expected? Pace must change — sticking to plan despite feedback wastes time or loses them
- All theory, no practice: Understanding requires doing, not just hearing. Every milestone should include practice element
- Ignoring motivation: Person who does not see why concept matters will not retain it. Connect every concept to stated goal
- Overloading sessions: Trying to cover too much in one sitting. Better to cover less with retention than more with forgetfulness
- Coach-as-lecturer: Coach guides learner's exploration, does not deliver monologue. Ask more questions than you answer
See Also
learn— AI self-directed variant for systematic knowledge acquisitionteach-guidance— coaching person to teach others. Complementary to learning coachingmeditate-guidance— clearing mental noise before learning session improves focus and retentionremote-viewing-guidance— shares structured observation approach supporting learning from experience
GitHub Repository
Related Skills
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
polymarket
MetaThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
creating-opencode-plugins
MetaThis skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
sglang
MetaSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
