Creates a staged learning plan from a topic, course page, or documentation set with goals, practice tasks, and checkpoints. Use when the user wants a "study plan", "learning roadmap", "curriculum", "syllabus", "learning path", or asks "how do I learn X" or "help me learn X in N weeks".
Build a staged learning plan from a topic, course page, or documentation set so the learner moves from where they are now to a concrete target outcome. Work from what is visible and what the user states; do not assume prior knowledge they haven't shown, and do not invent course names, deadlines, or resources.
Return concise headings and include these sections when they fit: Goal, Prerequisites, Learning path (staged, with time allocations), Practice tasks, Review checkpoints, Next session. If the context is insufficient, say what is missing and give the best supported next step.
Request:
I want to learn React in 4 weeks, I already know JavaScript, about 5 hours a week.
Plan:
Goal: Build and ship a small React app in 4 weeks (~5 hrs/week).
Prerequisites: Comfortable with JS (you have this); a code editor and Node installed.
Learning path
- Week 1 — Fundamentals (5 hrs): components, JSX, props, state. Read the official "Learn React" intro; build a counter and a to-do list.
- Week 2 — Hooks & effects (5 hrs):
useState,useEffect, lists and keys. Fetch and render data from a public API.- Week 3 — Composition & routing (5 hrs): lifting state, forms, React Router. Add multiple pages to your week-2 app.
- Week 4 — Project (5 hrs): ship one app end to end (e.g. a movie search), then deploy it.
Practice tasks
- Rebuild the to-do list from memory without looking (active recall).
- Refactor one component to lift shared state up a level.
Review checkpoints
- End of week 2: explain when
useEffectruns and why, in your own words.- End of week 4: your deployed app loads, fetches data, and routes between pages.
Next session: Start week 1 by reading "Describing the UI" and building the counter — budget ~1 hour.
Approved by Chrome Web Store, Firefox Add-ons, and Apple App Store
Portfolio Project Review
surfmindEvaluates whether a portfolio project, side project, or resume project idea is worth building to land a target role, scoring role signal, uniqueness, demo ability, metrics, time to a working version, and interview-story potential. Use when the user asks if a project idea is worth building, wants to evaluate side projects for a job search, or wants to pick a project that signals to hiring managers.
Paper Reader
surfmindExplains academic papers, abstracts, PDFs, and technical articles by laying out their method, findings, limitations, and implications. Use when the user says "explain this paper", "summarize this study", "read this paper", "break down this research", or asks what a paper or abstract means.
Repo Onboarder
surfmindExplains a repository's purpose, structure, setup and run commands, key scripts, and the first files worth opening. Use when the user wants to understand a new repo or codebase — "what does this project do", "how do I get started", "give me a codebase overview", "onboard me to this repo".