dsa-coach
A Claude Code plugin that turns your DSA practice repo into a coached, spaced-repetition study loop. It bundles four skills that pick what to solve next, capture metadata for problems you've solved, schedule reviews, and grade your understanding with a Feynman teach-back session.
Skills
- suggest-problem — picks the next unsolved problem from bundled curricula (LeetCode Top Interview 150, GFG 160, HackerRank Interview Kit, InterviewBit), detecting what you've already done by scanning your local solution folders.
- add-problem — fetches and writes metadata for a newly-solved problem into your metadata file, self-healing the file if it's missing and regenerating stats if a stats command is configured.
- review-problem — picks an already-solved problem for a spaced-repetition re-solve without revealing the solution, using your practice history.
- feynman-coach — runs a teach-back coaching session where you explain a problem in your own words and get graded on understanding, writing notes to your Feynman notes directory.
- fresh-problem — (opt-in) suggests the freshest recently-asked coding interview problem you haven't solved, pulled live from a configurable community feed (default source: HelloInterview), tagged with the company, level, and date it was asked. Off by default; enable via
liveQuestions.enabled.
Install
/plugin marketplace add arkajyotiadhikary/dsa-coach
/plugin install dsa-coach
Setup
The plugin works zero-config if your repo mirrors the default layout (see the table below). If it doesn't, drop a config file at your repo root:
- Copy
dsa-coach.config.example.json to dsa-coach.config.json at the root of your DSA repo (the directory where you run Claude).
- Edit the folder names, file paths, and commands to match your repo.
- Any key you omit falls back to the documented default, so you only need to set what differs.
Every skill begins with a "Step 0 — Load config" step: it reads dsa-coach.config.json from the current working directory if present, falls back to defaults for any missing key, and uses all defaults if the file is absent entirely.
Config reference
| Key | Default | Meaning |
|---|
language | "ts" | File extension of your solution files. |
solutionDirs.leetcode | "leetcode" | Folder holding your LeetCode solutions. |
solutionDirs.geeksforgeeks | "geeksforgeeks" | Folder holding your GeeksforGeeks solutions. |
solutionDirs.hackerrank | "hackerrank" | Folder holding your HackerRank solutions. |
solutionDirs.interviewbit | "interviewbit" | Folder holding your InterviewBit solutions. |
metaFile | "data/problems-meta.json" | JSON file the plugin manages for per-problem metadata (created on demand if missing). |
practiceFile | "data/practice.json" | JSON file holding review/practice history (a missing file is treated as empty history). |
feynmanDir | "feynman" | Directory where Feynman teach-back notes are written. |
statsCommand | "npm run stats" | Command run to regenerate stats; skipped gracefully if null or absent. |
practiceLogCommand | "npm run practice -- {file} \"{note}\"" | Command template for logging a practice session. {file} and {note} are literal placeholders the skill substitutes. Skipped if unconfigured. |
liveQuestions.enabled | false | Master opt-in for the fresh-problem live feed. When false, no network call is ever made. |
liveQuestions.endpoint | HelloInterview tRPC URL | The live questions endpoint. The only place the current source is named; override to point elsewhere. |
liveQuestions.interviewTypes | ["CODING","AI_ENABLED_CODING"] | Which interview types to keep from the feed. |
liveQuestions.maxPages | 3 | How many pages (×25 questions) to pull before filtering. |
Assumptions
- Solutions are one file per problem, stored under per-platform folders (the
solutionDirs values).
- Problem metadata is a JSON file (
metaFile) that the plugin reads and writes for you. Practice history lives in a second JSON file (practiceFile).
- File naming is consistent enough for the local scan to map files back to curriculum problems.
If you already follow these conventions with the default folder and file names, the plugin runs with no config file at all.
The fresh-problem skill is the only one that uses the network, and it is opt-in (off by default). When enabled it fetches questions live for your own practice; fetched data is never written to your repo or redistributed.
Worked example
tests/fixtures/sample-repo/ is a tiny, self-contained DSA repo that demonstrates the expected layout: solution folders, a dsa-coach.config.json, and seeded metaFile / practiceFile. Use it as a reference for how to structure your own repo.
Contributing
