taerv-entry-editing

Convert legacy Taerv dictionary markers to +/* format while preserving pronunciation lines.

22|8|Updated Jul 14, 2019
One-click install
npx skills add https://github.com/hqzxzwb/taerv_czdin_jihua --skill taerv-entry-editing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taerv-entry-editing
Source: https://github.com/hqzxzwb/taerv_czdin_jihua/tree/main/.codex/skills/taerv-entry-editing
Command: npx skills add https://github.com/hqzxzwb/taerv_czdin_jihua --skill taerv-entry-editing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty when editing the Taerv dictionary by prescribing the exact structure, pronunciation handling, and note placement that every entry must follow.

Core Features & Use Cases

  • Entry modernization: Convert legacy entries with >/- markers into the newer +/* structure while preserving intended meanings and examples.
  • Pronunciation governance: Ensure the pronunciation line and any locality prefixes reflect normalized phonology and that irregular readings are documented as notes.
  • Guided example handling: Place shared examples under * 通用, keep source-specific notes tied to their markers, and never leave blank lines between entries.

Quick Start

Update the taerv entry under the appropriate letter directory, converting legacy markers to + and * while preserving pronunciation notes.

Frequently Asked Questions about taerv-entry-editing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format taerv dictionary entries consistently?

To format taerv dictionary entries consistently, update entries under the appropriate letter directory by converting legacy markers to the newer + and * style while preserving pronunciation lines and noting locality readings according to guidelines.

What is the correct way to convert legacy markers in a dictionary entry?

Converting legacy markers in a dictionary entry requires replacing older > and - markers with the newer + and * structure. This modernization process preserves intended meanings, examples, and source-specific notes tied to their original markers.

How do I handle pronunciation lines and locality prefixes in markdown entries?

Handling pronunciation lines and locality prefixes in markdown entries requires ensuring they reflect normalized phonology. Any irregular readings found in the pronunciation line must be documented explicitly as notes within the entry.

Where should I place shared examples when editing dictionary entries?

When editing dictionary entries, place shared examples under the * 通用 marker. You must keep source-specific notes tied to their respective markers and never leave blank lines between individual entries.

Can I use standard markdown formatting for taerv entry maintenance?

Taerv entry maintenance uses markdown formatting but requires a specific style guide. You must apply the prescribed + and * structure for entries across letter directories and temp staging areas instead of standard markdown conventions.

What are the limitations when modernizing taerv dictionary entries?

A key limitation when modernizing taerv dictionary entries is that blank lines between entries are never permitted. Additionally, you must carefully preserve all original pronunciation notes and source-specific details during the marker conversion process.