메뉴
Requirements for creating or revising adjective entries in je-dict-1. Covers forms, conjugations, predicate vs modifier usage, and similar word distinctions.
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 and revising example sentences in je-dict-1. Covers minimum counts, progressive length, vocabulary restrictions by tier, and quality standards.
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 | adjective-entry |
| description | Requirements for creating or revising adjective entries in je-dict-1. Covers forms, conjugations, predicate vs modifier usage, and similar word distinctions. |
Reminder: Write each entry individually by hand. Do not use scripts to mass-produce entries. See entry-guidelines skill.
When creating or revising ADJECTIVE entries (both i-adjectives and na-adjectives), work from the sections below as an inventory — not a checklist. Adjective notes typically run ~300–800 chars and cover two or three of: forms, predicate-vs-modifier usage, similar-word distinctions, register. Conjugation for i-adjectives lives in the structured conjugation field, not in notes. Include a section only when it adds something the gloss and examples don't.
Include derived forms where natural:
FORMS:
- Adverbial: {遠|とお}く (i-adj) / {静|しず}かに (na-adj)
- Noun form: {遠|とお}さ (where natural)
Note: Not all adjectives have natural noun forms. Only include if commonly used.
I-adjective entries must include a conjugation field with all conjugated forms hard-coded in the JSON (parallel to verb conjugation tables). Use python3 build/add_adjective_conjugations.py to generate conjugation data after creating i-adjective entries.
The conjugation table includes 6 forms: Present, Past, て form, Adverbial, Conditional ば, Conditional たら. See the verb-conjugations skill for the JSON structure (same format, different type values).
Do NOT include a CONJUGATION: section in the notes field — that information belongs in the structured conjugation field.
Na-adjective conjugation is still shown in notes:
CONJUGATION:
- Negative: {静|しず}かではない
- Te-form: {静|しず}かで
- Past: {静|しず}かだった
Indicate which form is more common:
USAGE PATTERN:
- More common as: Predicate / Modifier / Equal
- Example: この{道|みち}は{遠|とお}い (predicate) vs. {遠|とお}い{道|みち} (modifier)
For adjectives with semantic overlap, include distinctions:
SIMILAR WORDS:
- {楽|らく} vs. {簡単|かんたん} vs. {易|やさ}しい
- {楽|らく}: comfortable, at ease (subjective feeling)
- {簡単|かんたん}: simple, straightforward (objective complexity)
- {易|やさ}しい}: gentle, easy to understand (approachable)
Key adjective groups to distinguish:
Mark as: Casual / Neutral / Formal / Emphatic
Example: すごい - [Register: Casual/Emphatic]
When kanji vs. hiragana matters:
ORTHOGRAPHY:
- すごい is commonly written in hiragana; {凄|すご}い appears in formal writing
- {可愛|かわい}い vs. かわいい - both common
Important: Follow the formatting guidelines in the vocabulary-notes skill for proper structure.
[Adjective] is an [i-adjective/na-adjective].
FORMS:
- Adverbial: [form]
- Noun form: [form] (if natural)
SIMILAR WORDS:
- [word 1] vs. [word 2]: [distinction]
[Register notes if applicable]
[Any special usage patterns or restrictions]
See the example-sentences skill for complete requirements including:
For adjectives with multiple senses, each example must include a sense_numbers field:
"examples": [
{
"id": "00001_adj_ex1",
"japanese": "...",
"english": "...",
"sense_numbers": [1]
}
]
Adjective-specific guidelines:
All adjective entries must include these tags in metadata.tags:
"metadata": {
"tags": {
"pos": ["adjective-i"], // adjective-i, adjective-na, adjective-no, adjective-taru
"formality": "neutral", // formal, neutral, informal, vulgar
"politeness": "plain", // honorific, humble, polite, plain
"semantic": ["descriptive"] // Choose appropriate category
}
}
POS tag values for adjectives:
adjective-i: い-adjectives (高い, 大きい, 美しい)adjective-na: な-adjectives (静か, 便利, きれい)adjective-no: の-adjectives (本当の, 普通の)adjective-taru: たる-adjectives (堂々たる, 悠々たる) - literary/formalSemantic categories for adjectives:
emotion: 嬉しい, 悲しい, 怖い (feelings)size: 大きい, 小さい, 長い, 高い (dimensions)color: 赤い, 青い, 白い (colors)descriptive: Fallback for adjectives not fitting specific categoriespython3 build/verify_furigana.py <entry_id> shows "✓ OK"conjugation field present with 6 forms (run add_adjective_conjugations.py or include directly)