Tutor Skill

File Structure

StudyVault/
├── *dashboard*              ← Compact overview: proficiency table + stats
└── concepts/
    ├── {area-name}.md       ← Per-area concept tracking (attempts, status, error notes)
    └── ...

• Dashboard: Only aggregated numbers. Links to concept files. Stays small forever.
• Concept files: One per area. Tracks each concept with attempts, correct count, date, status, and error notes. Grows proportionally to unique concepts tested (bounded).

Workflow

Phase 0: Detect Language

{LANG}

{LANG}

Phase 1: Discover Vault

1. Glob

   **/StudyVault/

   in project
2. List section directories
3. Glob

   **/StudyVault/*dashboard*

   to find dashboard
4. If found, read it. Preserve existing file path regardless of language.
5. If not found, create from template (see Dashboard Template below)

Phase 2: Ask Session Type

1. If unmeasured areas (⬜) exist → include "Diagnostic" option targeting those areas
2. If weak areas (🟥/🟨) exist → include "Drill weak areas" option naming the weakest area(s)
3. Always include "Choose a section" option so the user can pick any area
4. If all areas are 🟩/🟦 → include "Hard-mode review" option

Phase 3: Build Questions

1. Read markdown files in target section(s)
2. If drilling weak area: also read

   concepts/{area}.md

   to find 🔴 unresolved concepts — rephrase these in new contexts (don't repeat the same question)
3. Craft exactly 4 questions following

   references/quiz-rules.md

references/quiz-rules.md

Phase 4: Present Quiz

• 4 questions, 4 options each, single-select
• Header: "Q1. Topic" (max 12 chars)
• Descriptions: neutral, no hints

Phase 5: Grade & Explain

1. Show results table (question / correct answer / user answer / result)
2. Wrong answers: concise explanation
3. Map each question to its area

Phase 6: Update Files

1. Update concept file (

concepts/{area}.md

)

• New concept: Add row to table + if wrong, add error note under

  ### 오답 메모

  (or localized equivalent)
• Existing 🔴 concept answered correctly: Increment attempts & correct, change status to 🟢, keep error note (learning history)
• Existing 🟢 concept answered wrong again: Increment attempts, change status back to 🔴, update error note

| Concept | Attempts | Correct | Last Tested | Status |
|---------|----------|---------|-------------|--------|
| concept name | 2 | 1 | 2026-02-24 | 🔴 |

### Error Notes

**concept name**
- Confusion: what the user mixed up
- Key point: the correct understanding

2. Update dashboard

• Recalculate per-area stats from concept files (sum attempts/correct across all concepts in that area)
• Update proficiency badges: 🟥 0-39% · 🟨 40-69% · 🟩 70-89% · 🟦 90-100% · ⬜ no data
• Update stats: total questions, cumulative rate, unresolved/resolved counts, weakest/strongest

Dashboard Template

{LANG}

# Learning Dashboard

> Concept-based metacognition tracking. See linked files for details.

---

## Proficiency by Area

| Area | Correct | Wrong | Rate | Level | Details |
|------|---------|-------|------|-------|---------|
(one row per section, last column = [[concepts/{area}]] link)
| **Total** | **0** | **0** | **-** | ⬜ Unmeasured | |

> 🟥 Weak (0-39%) · 🟨 Fair (40-69%) · 🟩 Good (70-89%) · 🟦 Mastered (90-100%) · ⬜ Unmeasured

---

## Stats

- **Total Questions**: 0
- **Cumulative Rate**: -
- **Unresolved Concepts**: 0
- **Resolved Concepts**: 0
- **Weakest Area**: -
- **Strongest Area**: -

Concept File Template

# {Area Name} — Concept Tracker

| Concept | Attempts | Correct | Last Tested | Status |
|---------|----------|---------|-------------|--------|

### Error Notes

(added as concepts are missed)

Important Reminders

• ALWAYS read

  references/quiz-rules.md

  before creating questions
• NEVER include hints in option labels or descriptions
• NEVER use "(Recommended)" on any option
• Randomize correct answer position
• After grading, ALWAYS update both concept file AND dashboard
• Communicate in user's language