wenyan-mode_skill

Overview

This skill enforces a classical Chinese (wenyan) writing style for all assistant responses once installed. It activates automatically and requires no trigger phrase. Technical terms remain in their original form and code/command content is left unchanged. The style favors concise, elegant phrasing while preserving technical accuracy.

How this skill works

Upon activation, the skill intercepts generated text and rewrites it into wenyan-style sentences while retaining technical tokens (function, API, commit, TypeScript, etc.). It applies minimal rhetorical particles and adapts address terms by context (you,君,閣下 equivalents handled conceptually). Code blocks, commands, file contents, and literal technical strings are exempt from transformation to avoid breaking syntax.

When to use it

• You want all assistant replies to read in concise classical Chinese style.
• Maintaining precise technical terminology while changing surface tone.
• Producing brief, elegant explanations, summaries, or suggestions for developers.
• Keeping code, commands, and file contents verbatim while shifting narrative language.
• Applying a consistent literary voice across documentation drafts or code reviews.

Best practices

• Keep technical statements precise; the skill will not alter technical tokens or code blocks.
• Avoid embedding executable code inside prose that you expect rewritten; place code in proper code blocks to preserve exact text.
• State the intended audience when formality matters (casual, advisory, respectful) to guide address tone.
• Use short, direct prompts for clearer wenyan conversions and fewer ambiguous rewrites.
• Rely on the skill for style only; verify factual or diagnostic details as usual.

Example use cases

• Code review comments rendered in concise wenyan phrasing while preserving code snippets.
• Bug triage summaries that read elegantly yet keep error messages and stack traces intact.
• API documentation introductions rewritten with classical concision while retaining endpoint names and parameters.
• Pull request descriptions that present rationale succinctly, leaving commit titles and command examples unchanged.
• Developer chat replies that sound literary but remain technically precise.