learning-accelerator_skill

Overview

This skill accelerates learning new technologies by acting as an interactive tutor that adapts to your immediate needs. It offers just-in-time help, exploratory deep dives, and reference-style patterns so you can learn by doing and retain knowledge. Use it to move from zero to productive quickly and capture what you learn for future reuse.

How this skill works

The skill provides three learning modes: Just-In-Time for minimal runnable examples, Exploratory for conceptual foundations, and Reference for patterns and gotchas. It guides fast-track learning plans (e.g., one-hour framework, two-hour language) and uses techniques like build-to-learn, compare-and-contrast, and rubber-duck teaching. It also supports quick lookups for syntax, error explanations, and API usage, and can store learnings for reuse.

When to use it

• You need to start using a framework or library immediately and want the minimum working example.
• You want a conceptual mental model before committing to a deeper implementation.
• You encounter an unfamiliar error and need an actionable explanation and fix.
• You’re choosing between technologies and want a concise compare/contrast for your context.
• You want to capture a workflow or lesson so you don’t re-learn it later.

Best practices

• Start with a minimal runnable example, then extend it—learn by building.
• Use targeted quick questions for syntax or a single API method instead of broad searches.
• Compare new tech to what you already know to transfer mental models faster.
• Explain back what you learned (rubber duck) to surface gaps and consolidate memory.
• Capture key insights or workflows into a reusable note or skill immediately after learning.

Example use cases

• Get a one-hour crash plan to start a new JavaScript framework and ship a simple component.
• Walk through a 30-minute concept briefing (e.g., async patterns) with examples and gotchas.
• Paste an error message and receive an explanation, root cause, and step-by-step fix.
• Compare REST vs GraphQL for your product’s API needs with trade-offs and recommendations.
• Turn a discovered workflow into a reusable micro-skill so the next time you skip basics.