source-command-grammar-inflection

Use this skill when the user asks to run the migrated source command grammar-inflection.

Command Template

CryptoGlossario — Grammar Inflection · v2.0

This command owns englishNumberBehavior, englishPlural, italianNumberBehavior, italianPlural, italianGender, grammarInflectionNote and derived searchAliases only. Do not touch any other field.

Pipeline, ownership and versioning rules live in lib/skill-registry.ts.

Purpose

Record the minimal grammar profile needed for a bilingual technical glossary:

• number behavior for the original lemma (title)
• number behavior for the visible Italian form (translation or baselineTranslation)
• grammatical gender only for the visible Italian form

This data is used for:

• dictionary UI near the lemma
• search aliases, so plural queries can find singular lemmas

English common nouns do not have grammatical gender in the same sense as Italian nouns. Do not add or infer an English gender field. If an English form has a natural-gender referent, mention it only when it affects Italian usage.

Number Behaviors

Italian Gender Values

Rules

• englishNumberBehavior describes title.
• englishPlural is required only when englishNumberBehavior = "has_plural".
• italianNumberBehavior describes translation when present; otherwise it describes title as borrowed in Italian usage.
• italianPlural is required only when italianNumberBehavior = "has_plural".
• italianGender describes the visible Italian form shown in the UI; it is not an English gender.
• Do not use baselineTranslation as the visible Italian grammar target unless it is also saved in translation.
• Use not_applicable only when assigning masculine/feminine/common would mislead the reader.
• The number behavior describes the visible form, not the underlying referent. If the Italian expression can refer to multiple items but the visible form does not change, use invariable, not has_plural.
• Do not invent a plural just because one is mechanically possible.
• Use no_common_plural for mechanisms, protocols, properties and conceptual names where plural usage is not normal in technical prose.
• Use invariable for acronyms or borrowed forms that stay unchanged in Italian, such as NFT.
• grammarInflectionNote must be short, factual and in Italian. Include gender only when it helps explain the decision.
• searchAliases must also include any morphological variant of the lemma that title-normalization rejected (e.g. if the lemma is Token Burning, add Token Burn), so search finds the term under either form.

Compounds and Borrowings

• For full Italian translations, gender and plural normally follow the head noun: prova di lavoro is feminine because the head is prova; agenti AI is masculine plural because the head is agenti.
• For hybrid Italian forms and direct borrowings, prefer attested Italian usage over literal translation. Example: il token, gli NFT, la blockchain, la cache.
• For acronyms, protocol names, product names and fixed technical expressions, avoid mechanical plurals unless plural use is normal in sources.
• If usage is split, use common for gender or context_dependent for number only when the split is real and relevant; otherwise choose the dominant technical use and explain it in grammarInflectionNote.

Web Verification Default

Follow AGENTS.md "Web research standard" (lemma autonomy vs gloss, domain matching, currency window, minimum source count). Use web search by default for doubtful cases before writing or applying a batch. Doubtful cases include:

• borrowed English forms in Italian (token, asset, pool, rollup, prompt, standard, wallet, suite, repository)
• acronyms and protocol names whose plural or gender is not obvious from standard grammar
• context_dependent, invariable, and no_common_plural decisions where normal technical usage is uncertain
• cases where a mechanically possible plural exists but may be unnatural in technical prose
• Italian expressions where the proposed plural is identical to the singular visible form
• borrowed terms where article usage is split or uncertain

Prefer authoritative or usage-rich sources: official documentation, project docs, reputable technical glossaries, standards docs, product docs, or established Italian technical usage. Keep the batch note concise; do not include citations in grammarInflectionNote, but retain source links in the working audit file when doing a review.

Web verification must match the term's semantic domain. Use the term's disciplines and definition to avoid evidence from unrelated homonyms or everyday meanings.

Examples

``json { "slug": "ai-agent", "title": "AI Agent", "englishNumberBehavior": "has_plural", "englishPlural": "AI Agents", "italianNumberBehavior": "has_plural", "italianPlural": "Agenti AI", "italianGender": "masculine", "grammarInflectionNote": "Il termine è numerabile in entrambe le lingue; in italiano il nome principale è maschile." } ``

``json { "slug": "nft", "title": "NFT", "englishNumberBehavior": "has_plural", "englishPlural": "NFTs", "italianNumberBehavior": "invariable", "italianGender": "masculine", "grammarInflectionNote": "In inglese è comune il plurale “NFTs”; in italiano l'acronimo resta normalmente invariabile e si usa soprattutto al maschile." } ``

``json { "slug": "proof-of-work", "title": "Proof of Work", "englishNumberBehavior": "no_common_plural", "italianNumberBehavior": "no_common_plural", "italianGender": "feminine", "grammarInflectionNote": "È trattato come nome concettuale o nome di meccanismo; la resa italiana 'prova di lavoro' è femminile." } ``

Batch Format

``json [ { "id": "convex_id_here", "slug": "term-slug", "title": "Term Title", "englishNumberBehavior": "has_plural", "englishPlural": "Term Titles", "italianNumberBehavior": "has_plural", "italianPlural": "Termini italiani", "italianGender": "masculine", "grammarInflectionNote": "Nota breve in italiano." } ] ``

``bash bun run apply:grammar-inflection /tmp/cg_grammar_inflection_batch.json bun run apply:grammar-inflection /tmp/cg_grammar_inflection_batch.json --apply ``