Skip to content

Add JLPT N3 curriculum requirements and implementation guide - #19

Merged
alanfwilliams merged 2 commits into
mainfrom
claude/create-n3-requirements-7V5pQ
Feb 18, 2026
Merged

Add JLPT N3 curriculum requirements and implementation guide#19
alanfwilliams merged 2 commits into
mainfrom
claude/create-n3-requirements-7V5pQ

Conversation

@alanfwilliams

Copy link
Copy Markdown
Owner

Summary

This PR introduces a comprehensive requirements document for extending the JLPT course curriculum from N4 (day 660) through N3 readiness (day 960). The document serves as a specification for implementing 300 new curriculum days organized into 6 new phases, along with supporting features for vocabulary, grammar, kanji, and reading comprehension.

Key Changes

  • Curriculum expansion: Defines 6 new phases (15–20) spanning days 661–960, with specific content targets:

    • Phase 15: N4 Review (30 days)
    • Phase 16: N3 Vocabulary (~1,500 words across 80 days)
    • Phase 17: N3 Verbs & Adjectives (50 days)
    • Phase 18: N3 Grammar (~120 patterns across 75 days)
    • Phase 19: N3 Kanji (~170 new kanji across 35 days)
    • Phase 20: N3 Test Prep (30 days)
  • New lesson features:

    • Introduces "reading" type for paragraph-level comprehension lessons
    • Defines passage field structure with Japanese/English text and comprehension questions
    • Specifies furigana toggle functionality for reading passages
  • Exercise system enhancements:

    • Documents 4 new exercise types: reading, conjugation, pair_match, fill_blank
    • Recommends increasing exercise cap from 5 to 6–8 per lesson for N3 content
  • Content organization:

    • Vocabulary grouped by 10 topic clusters (daily life, emotions, work, nature, health, media, education, travel, abstract concepts, adverbs/conjunctions)
    • Grammar patterns organized into 9 thematic groups (conditionals, cause/reason, contrast, extent, hearsay, time, intention, obligation, listing, formal expressions)
    • Kanji grouped by semantic themes with guidance on handling multiple readings
  • Data integrity guidelines:

    • Establishes strict content authoring rules (3-element vocab arrays, 2-element char arrays, non-empty meanings, etc.)
    • References and prevents recurrence of bugs found in existing curriculum (days 85, 86–97, 173, 253–308)
  • Implementation roadmap:

    • Specifies file changes needed in curriculum.js, lib.js, index.html, tests.html, and documentation
    • Provides 11-step implementation order from phase constants through final testing

Notable Implementation Details

  • The document maintains backward compatibility with existing N5/N4 content (no changes to days 1–660)
  • SRS system requires no structural changes; existing SM-2 implementation scales to 960 days
  • UI components (overview calendar, progress bar) auto-scale without modification
  • Comprehensive test coverage plan includes regression protection for all 92 existing tests plus new N3-specific test modules

https://claude.ai/code/session_0163k3rusvAMQfxAr6dnkfSX

Outlines the full scope for extending the course from N4 (day 660)
through JLPT N3 readiness (~300 new days): curriculum phases, vocabulary,
grammar patterns, kanji, reading comprehension, exercise types, SRS
tuning, UI updates, and test coverage.

https://claude.ai/code/session_0163k3rusvAMQfxAr6dnkfSX
Extends the document from N3-only to a full N3/N2/N1 roadmap covering
1,060 new days (661–1720), 18 new phases, ~8,500 vocabulary, ~670
kanji, ~520 grammar patterns, 11 new exercise types, reading
comprehension with scaled passage complexity, SRS tuning, UI updates
(level selector, furigana, per-level progress), and a 31-step
implementation order across three phases.

https://claude.ai/code/session_0163k3rusvAMQfxAr6dnkfSX
@alanfwilliams
alanfwilliams merged commit da6d64c into main Feb 18, 2026
1 check passed
@alanfwilliams
alanfwilliams deleted the claude/create-n3-requirements-7V5pQ branch February 18, 2026 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants