Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From paideia
Shows HW/example coverage of course sections, ranks sections by exam probability, and recommends drill strategies. Also supports "hot" to list exam-primary zones and "all" for a distribution table.
npx claudepluginhub taewooopark/paideia --plugin paideiaHow this command is triggered — by the user, by Claude, or both
Slash command
/paideia:hwmap § number or "hot" to list exam-primary zones or "all"The summary Claude sees in its command listing — used to decide when to auto-load this command
## Output language Read `INTERFACE_LANG` from `.course-meta` (default `en`). All user-facing prose must be in that language. Keep in English regardless: file paths, slash command names, pattern IDs (P1, P2…), tier markers (🔥🔥/🔥/🟡/⚪), and the literal section anchors downstream tools regex on. Read `course-index/coverage.md`. If missing, tell the user to run `/analyze` first. Query: $ARGUMENTS **Core premise.** HW coverage is an exam-probability signal. Sections the professor drilled into HW are where the exam points live. "No HW coverage" is not a red flag — it's a low-risk zone the ...
/reviewDisplays learning progress dashboard: quiz scores, weak/strong areas, module completion, and next study recommendations for all topics or specific topic.
/learn-reportGenerates learning insights report from accumulated LEARN.md files in the project, analyzing top skills, coverage gaps, and overall health with next-step suggestions. Supports markdown or json format.
Share bugs, ideas, or general feedback.
Read INTERFACE_LANG from .course-meta (default en). All user-facing prose must be in that language. Keep in English regardless: file paths, slash command names, pattern IDs (P1, P2…), tier markers (🔥🔥/🔥/🟡/⚪), and the literal section anchors downstream tools regex on.
Read course-index/coverage.md. If missing, tell the user to run /analyze first.
Query: $ARGUMENTS
Core premise. HW coverage is an exam-probability signal. Sections the professor drilled into HW are where the exam points live. "No HW coverage" is not a red flag — it's a low-risk zone the professor chose to omit.
Procedure:
If query is a § number or section name: Show which problems cover that section, and adjacent sections (§±1) for context. List the patterns involved. State the exam tier (🔥🔥 / 🔥 / 🟡 / ⚪) and the drill recommendation that follows.
If query is hot (or primary, exam, risk, blind for backwards compatibility):
Return 🔥🔥 Exam-primary and 🔥 Exam-likely sections, ranked by HW density (highest first). For each:
/twin <hw-id> (build surface variance)/blind <hw-id> (strategy-check on the real HW)/pattern <Pk> then /quiz §<n> 3Do not recommend /derive here as a default — derivations are for reading gaps, not for drilling exam-likely zones. Use /derive only if the user explicitly asks for a clean reference.
If query is all or empty:
Render an exam-tier distribution table:
| Exam tier | Count | Sections |
|---|---|---|
| 🔥🔥 Exam-primary (3+ HW) | n | list |
| 🔥 Exam-likely (2 HW) | n | list |
| 🟡 Exam-possible (1 HW) | n | list |
| ⚪ Low-risk (no HW) | n | list |
Plus the "Recommended drill priority" section from coverage.md (ordered by HW density, not by absence).
Low-risk section handling. If the user insists on drilling a ⚪ section, warn once (in $INTERFACE_LANG): "Sections with no HW have low exam probability. If time is short, start from 🔥🔥." Then comply if they still want to.
Always close with (in $INTERFACE_LANG): "If you could pick just one 🔥🔥 item to drill right now, which one — and how many minutes do you have?"
Output goal: exam-point maximization. Steer time toward HW-dense zones.