菜单
Requirements for creating and revising example sentences in je-dict-1. Covers minimum counts, progressive length, vocabulary restrictions by tier, and quality standards.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
General quality standards for all je-dict-1 dictionary entries. Use when creating or revising any entry type.
Requirements for creating or revising adjective entries in je-dict-1. Covers forms, conjugations, predicate vs modifier usage, and similar word distinctions.
Requirements for creating nouns, counters, adverbs, and expressions in je-dict-1. Covers collocations, counting patterns, register, and cultural notes.
Requirements for creating or revising verb entries in je-dict-1. Covers transitivity, aspect/ている behavior, particle patterns, and collocations.
Requirements for formatting and structuring the notes field in je-dict-1 entries. Covers formatting, content organization, and readability standards.
Guidelines for adding inline cross-reference links to example sentences and notes. Includes common word reference table.
| name | example-sentences |
| description | Requirements for creating and revising example sentences in je-dict-1. Covers minimum counts, progressive length, vocabulary restrictions by tier, and quality standards. |
This skill defines the standards for example sentences across all dictionary entries. All entry-creation and revision activities must follow these guidelines.
Every sense of every entry in the basic and core tiers must have at least 5 example sentences.
| Tier | Minimum Examples per Sense |
|---|---|
| Basic | 5 |
| Core | 5 |
Every sense of every entry in the general tier must have at least 3 example sentences.
| Tier | Minimum Examples per Sense |
|---|---|
| General | 3 |
Multi-sense entries: The requirements apply per sense. An entry with 3 senses in the basic tier needs at least 15 examples total (5 per sense).
Minimums are sufficient. Exceeding the minimum by 0–1 examples per sense is fine when a useful additional collocation comes to mind, but routinely producing 5 examples for a single general-tier sense (when 3 are required) inflates the entry without adding value. Match the example count to the entry's complexity; don't pad.
Examples within each sense should progress from shorter to longer:
Key principle: Early examples help learners recognize the word; later examples show how the word functions in natural, flowing Japanese.
| Example | Target Length (Japanese) |
|---|---|
| 1 | 5-15 characters |
| 2 | 10-20 characters |
| 3 | 15-30 characters |
| 4 | 25-45 characters |
| 5+ | 35-70 characters (or 2-3 short sentences) |
These are guidelines, not strict rules. Natural expression takes priority over hitting exact character counts.
For entries in the basic vocabulary tier:
| Examples | Vocabulary Restriction |
|---|---|
| 1-2 | Basic tier only - Use only words from the basic tier |
| 3-5 | Basic + Core tiers - May use basic and core vocabulary |
Critical: Basic tier examples must contain no general-tier or unlisted vocabulary. This ensures learners at the basic level can fully understand all examples without encountering unknown words.
For entries in the core vocabulary tier:
| Examples | Vocabulary Restriction |
|---|---|
| 1-2 | Basic + Core tiers - Use only basic or core vocabulary |
| 3-5 | No restriction - May use any vocabulary |
Recommendation: Even for unrestricted examples (3-5), avoid vocabulary that is not in the dictionary. Learners should be able to look up any unfamiliar word.
For entries in the general vocabulary tier:
| Examples | Vocabulary Restriction |
|---|---|
| 1-3+ | No restriction - May use any vocabulary |
Recommendation: Avoid obscure vocabulary not in the dictionary. Use common, natural expressions that learners are likely to encounter.
When creating examples for basic and core tier entries, verify vocabulary tier compliance:
# Check if a word is in the dictionary and its tier
python3 build/check_duplicate.py "word" "reading"
For systematic verification during polishing:
Common substitution patterns:
| Non-compliant | Basic alternative | Core alternative |
|---|---|---|
| {購入 | こうにゅう}する | {買 |
| {使用 | しよう}する | {使 |
| {非常 | ひじょう}に | とても |
| {困難 | こんなん} | {難 |
Every example must include a sense_numbers field linking it to the definition(s) it illustrates.
"examples": [
{
"id": "00001_word_ex1",
"japanese": "...",
"english": "...",
"sense_numbers": [1],
"has_audio": false,
"notes": null
}
]
[1] for all examples[1, 2] formatsense_number values in definitionsFor entries with multiple senses in basic/core tiers:
[1, 2] notation){kanji|reading} markupnotes field for explanations when neededExamples should illustrate:
{
"id": "00396_taberu_ex1",
"japanese": "{朝|あさ}ごはんを{食|た}べる。",
"english": "To eat breakfast.",
"sense_numbers": [1],
"has_audio": false,
"notes": null
}
Pattern: {entry_id}_ex{N}
entry_id: The entry's ID (e.g., 00396_taberu)N: Sequential number starting from 1| Field | Required | Description |
|---|---|---|
id | Yes | Unique example ID |
japanese | Yes | Japanese sentence with furigana |
english | Yes | Natural English translation |
sense_numbers | Yes | Array of sense numbers illustrated |
has_audio | Yes | Boolean (usually false) |
notes | Yes | Explanatory note or null |
prompts/polish_add_inline_links.md.お金が余った instead of お{金|かね}が{余|あま}ったWhen reviewing or revising examples, verify:
{entry_id}_ex{N} patternhas_audio is accuratenotes field present (null if not needed)When adding examples to bring an entry into compliance:
modified timestamp in metadataFor a basic-tier entry with one sense needing 5 examples:
Example 1: [short, basic vocab only]
Example 2: [short-medium, basic vocab only]
Example 3: [medium, basic+core vocab]
Example 4: [medium-long, basic+core vocab]
Example 5: [long or multi-sentence, basic+core vocab]
| Tier | Min Examples/Sense | Ex 1-2 Vocab | Ex 3+ Vocab |
|---|---|---|---|
| Basic | 5 | Basic only | Basic + Core |
| Core | 5 | Basic + Core | Any (prefer dictionary words) |
| General | 3 | Any | Any (prefer dictionary words) |