MCPcopy
hub / github.com/typedgrammar/typed-japanese

github.com/typedgrammar/typed-japanese @main sqlite

repository ↗ · DeepWiki ↗
219 symbols 521 edges 128 files 20 documented · 9%
README

🌸 Typed Japanese

If you can write TypeScript, you can understand Japanese!

Open in StackBlitz

demo

🌸 New: Interactive Playground → — an in-browser TypeScript editor where the compiler resolves conjugations live, plus a Verb Lab, Adjective Lab, Phrase Builder, and Sentence Gallery. (source · run locally with cd playground && pnpm install && pnpm dev)

Typed Japanese is a TypeScript type-level library that enables the expression of complete Japanese sentences through the type system. It creates a domain-specific language (DSL) based on Japanese grammar rules, allowing a subset of grammatically correct natural language to be written and verified using TypeScript's compiler.

This project also explores an intermediate format for AI in language learning. For example, LLMs could return grammar analysis of Japanese sentences using this format instead of JSON, enabling verification through TypeScript's type checker to improve correctness.

📖 Want to learn more? Check out our detailed blog post which explains how the TypeScript type system can be used to learn Japanese grammar from the ground up. The article starts with basic programming concepts and gradually builds up to complex Japanese grammatical structures like conditional sentences and interrogative phrases.

// Define the proper noun "ヒンメル"
type ヒンメル = ProperNoun<"ヒンメル">;

// Define する verb
type する = IrregularVerb & { dictionary: "する" };

// Create the そうした pattern (past form of そうする)
type そうした = DemonstrativeAction<Demonstrative & "そう", する, "Ta">;

// Create the conditional phrase "ヒンメルならそうした"
type ヒンメルならそうした = ConditionalPhrase<ヒンメル, "なら", そうした>;

// Type checking examples
const properExample: ヒンメルならそうした = "ヒンメルならそうした"; // "If it were Himmel, he would do so"
// 如果是辛美尔的话,他也会这么做的

🤖 Verb System

Verb Classes

Japanese verbs are categorized into three main classes:

  1. Godan Verbs (五段動詞) - Also known as "Group 1" or "u-verbs"

  2. Endings: う, く, ぐ, す, つ, ぬ, ぶ, む, る

  3. Examples: 話す (hanasu - to speak), 書く (kaku - to write)

  4. Ichidan Verbs (一段動詞) - Also known as "Group 2" or "ru-verbs"

  5. Always end with る

  6. Examples: 食べる (taberu - to eat), 見る (miru - to see)

  7. Irregular Verbs (不規則動詞) - Only two main verbs

  8. する (suru - to do)
  9. 来る (kuru - to come)

Verb Conjugation Forms

The system supports these conjugation forms:

  • Dictionary (Dictionary form)
  • Masu (Polite form)
  • Te (Te form)
  • Ta (Past form)
  • Nai (Negative form)
  • Potential (Potential form)
  • Passive (Passive form)
  • Causative (Causative form)
  • Volitional (Volitional form)
  • Imperative (Imperative form)
  • Conditional (Conditional form)
  • Hypothetical (Hypothetical form)
type 買う = GodanVerb & { stem: "買"; ending: "う" };
type 買うTe = ConjugateVerb<買う, "Te">; // 買って
type 買うTa = ConjugateVerb<買う, "Ta">; // 買った

type 食べる = IchidanVerb & { stem: "食べ"; ending: "る" };
type 食べるTe = ConjugateVerb<食べる, "Te">; // 食べて
type 食べるTa = ConjugateVerb<食べる, "Ta">; // 食べた

🎨 Adjective System

Japanese adjectives are categorized into two main classes:

  1. I-Adjectives (い形容詞) - End with い

  2. Examples: いい (good), 楽しい (fun), 高い (expensive)

  3. Na-Adjectives (な形容詞) - Require な when modifying nouns

  4. Examples: 綺麗 (pretty), 静か (quiet), 好き (liked)

Adjective Conjugation Forms

The system supports these conjugation forms for adjectives:

  • Basic (Basic form)
  • Polite (Polite form)
  • Past (Past form)
  • Negative (Negative form)
type いい = IAdjective & { stem: "い"; ending: "い"; irregular: true };
type 綺麗 = NaAdjective & { stem: "綺麗" };

🔗 Copula System

The copula (だ / です) turns a 体言 (noun or na-adjective stem) into a statement — "X is …". It is not a particle: like a verb or an adjective it inflects for politeness, tense and polarity, so it is modeled as a conjugable word via ConjugateCopula<Taigen, Form> (mirroring ConjugateVerb / ConjugateAdjective).

Copula Conjugation Forms

  • Plain → だ (plain) ・ Polite → です (polite)
  • Past → だった ・ PolitePast → でした
  • Negative → ではない ・ PoliteNegative → ではありません
  • NegativePast → ではなかった ・ PoliteNegativePast → ではありませんでした
  • CasualNegative → じゃない ・ CasualPoliteNegative → じゃありません
  • Written → である(formal written)・ Te → で(connective)

The copula has no generic attributive form: な is licensed only for な-adjectives (静かな町), never for plain nouns (×医者な — a noun takes の), so it lives in the adjective system, not here.

type 医者だ = ConjugateCopula<"医者", "Plain">; // 医者だ
type 医者ではありません = ConjugateCopula<"医者", "PoliteNegative">; // 医者ではありません

📚 Phrase and Sentence Composition

The system now supports:

  • Adjectives and verbs with particles
  • Connecting phrases with Japanese punctuation
  • Basic sentence structures
  • Conditional expressions with particles like なら
  • Demonstrative forms with actions

Example: Connecting simple adjective and imperative verb phrases

// I-adjective "ii" (good) with irregular conjugation
// Then add particle "yo" to basic form of "ii" -> "ii yo"
type いい = IAdjective & { stem: "い"; ending: "い"; irregular: true };
type いいよ = PhraseWithParticle<ConjugateAdjective<いい, "Basic">, "よ">;

// Irregular verb "kuru" (to come)
// Then add particle "yo" to imperative form of "kuru" -> "koi yo"
type 来る = IrregularVerb & { dictionary: "来る" };
type 来いよ = PhraseWithParticle<ConjugateVerb<来る, "Imperative">, "よ">;

// Connect both phrases -> "ii yo, koi yo"
type いいよ来いよ = ConnectedPhrases<いいよ, 来いよ>;

// Type checking examples
const correctPhrase1: いいよ = "いいよ"; // "It's good!" (114)
const correctPhrase2: 来いよ = "来いよ"; // "Come here!" (514)
const correctFullPhrase: いいよ来いよ = "いいよ、来いよ"; // "It's good, come here!"

Example: More flexible component-based sentence construction

type SentenceParts = [
  AdverbPart<"なんで">, // "Why" - question adverb
  IntensifierPart<"そんなに">, // "So much" - intensifier
  VerbPart<慣れる, "Te">, // "Get used to" in te-form
  ContractedPart<"ん">, // Contraction of "の" - colloquial nominalizer
  CopulaPart<"Plain">, // Copula "is" (だ) — a conjugable copula, not a particle
  ParticlePart<"よ"> // Emphatic sentence-ending particle
];

// Combines all parts into a single string
type JoinedSentence = JoinPhrasePartsValue<SentenceParts>;
const joinedSentence: JoinedSentence = "なんでそんなに慣れてんだよ"; // "Why are you so used to it?!"
// 你为什么这么熟练啊?

⚙️ Technical Implementation

The system uses TypeScript's template literal types, conditional types, and mapped types to create a purely type-level representation of Japanese grammatical rules.

Key components:

  • Type definitions for grammatical elements
  • Rule mapping via conditional types
  • String literal manipulation for form generation
  • Type inference for grammatical validation

💡 Why Typed Japanese?

  • Educational tool - Learn Japanese grammar through code
  • AI-assisted learning - Provide structured formats for language analysis
  • Grammar verification - Express and verify Japanese grammar in code
  • Integration potential - Basis for typed Japanese language tools

⚠️ Limitations

  • This is a type-level system only - it doesn't provide runtime functionality
  • The system handles standard forms but doesn't account for linguistic nuances
  • Some rare or archaic language patterns may not be accurately represented

This project is still in very early stages and heavily relies on LLM-generated grammar rules, which may occasionally contain hallucinations or inaccuracies. If you find any issue during actual use, please help by confirming and providing feedback.

🛠️ Development

If you're interested in contributing to or experimenting with Typed Japanese:

  1. Ensure you have Node.js and pnpm installed
  2. Clone the repository
  3. Install dependencies: pnpm install
  4. Run the tests: pnpm test

The tests validate that the type system functions correctly and all grammatical rules are properly implemented.

We welcome contributions! Feel free to open issues for bugs or feature requests, or submit pull requests with improvements.

📬 Contact

For sponsorship opportunities, research collaborations, or commercial inquiries, please reach out to contact@typedgrammar.com.

⚖️ License

MIT

Copyright (c) 2025-present, Yifeng Wang

Extension points exported contracts — how you extend this code

PerItem (Interface)
* Eval view — renders the committed parsing-accuracy benchmark results as-is. * * Data source: playground/eval/history
playground/src/components/Eval.tsx
AttemptTiming (Interface)
(no doc)
apps/TypedTranslate/bridge/tt-bridge.ts
Args (Interface)
(no doc)
playground/scripts/annotate.ts
RouteMeta (Interface)
(no doc)
playground/src/entry-server.tsx
AnnotateRequest (Interface)
(no doc)
apps/TypedTranslate/bridge/tt-bridge.ts
ModelResult (Interface)
(no doc)
playground/scripts/annotate.ts
Props (Interface)
(no doc)
playground/src/components/CompositionTree.tsx
ParseRequest (Interface)
(no doc)
apps/TypedTranslate/bridge/tt-bridge.ts

Core symbols most depended-on inside this repo

e
called by 74
playground/src/vocab/function-words.ts
push
called by 14
playground/src/vocab/extract.ts
nowMs
called by 12
apps/TypedTranslate/bridge/tt-bridge.ts
esc
called by 11
playground/scripts/prerender.mjs
toString
called by 10
playground/src/components/Analyzer.tsx
d
called by 9
apps/TypedTranslate/smoke.ts
emit
called by 9
apps/TypedTranslate/bridge/tt-bridge.ts
pct
called by 9
playground/scripts/eval-record.mjs

Shape

Function 173
Interface 45
Method 1

Languages

TypeScript100%

Modules by API surface

playground/scripts/annotate.ts29 symbols
playground/src/analysis/parse.ts22 symbols
apps/TypedTranslate/bridge/tt-bridge.ts19 symbols
apps/TypedTranslate/bridge/tree.ts17 symbols
playground/src/components/Eval.tsx11 symbols
playground/src/components/Concepts.tsx10 symbols
playground/src/components/Analyzer.tsx8 symbols
playground/src/context/route.tsx7 symbols
playground/scripts/eval-codex.mjs7 symbols
apps/TypedTranslate/smoke.ts7 symbols
playground/src/tutorial/types.ts5 symbols
playground/src/entry-server.tsx5 symbols

Dependencies from manifests, versioned

@eslint/js9.39.4 · 1×
@monaco-editor/react4.6.0 · 1×
@types/react18.3.12 · 1×
@types/react-dom18.3.1 · 1×
@typescript-eslint/eslint-plugin8.61.0 · 1×
@typescript-eslint/parser8.61.0 · 1×
@vitejs/plugin-react6.0.2 · 1×
eslint9.39.4 · 1×
monaco-editor0.52.2 · 1×
react18.3.1 · 1×
react-dom18.3.1 · 1×

For agents

$ claude mcp add typed-japanese \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact