What does 中文老师 do?

What This Skill Is

A writing style engine for Chinese work documents. It offers four writing styles, ranging from "clear and actionable" to "bold judgment backed by data," covering everything from weekly reports to strategic proposals. When writing a document, it automatically inserts Feishu whiteboards for visual summaries at the beginning, key sections, and end — not rigid logic diagrams, but simple, editable showcases of key information.

Its rules are derived from three sources: distillations of public documentation style guides (Google, Microsoft, GitHub), analyses of native Chinese reports from MBB/Big Four/HR consulting firms, and a summary of Dai Tong's personal writing style. It is not a tool to "write more formally" — it is a writing system that gives documents judgment, a human touch, and the ability to drive decisions.

A general-purpose AI agent skill, not tied to any specific platform. Compatible with TRAE CLI, Claude Code, Cursor, Codex, and others. When actually creating or updating a Docx/Wiki document, use it in conjunction with a Feishu document skill (e.g., lark-doc).

Four Writing Styles

chinese-teacher offers four writing styles, progressing from baseline to extreme:

#	Style	Positioning	One-Line Description
1	Default Style	Baseline	Clear structure, directly actionable, professional and restrained. The foundation of all styles.
2	Colleague Style	Personal	Dai Tong's personal style. Business-driven, with judgment, like a colleague talking.
3	Consulting Style	Institutional	MBB/Big Four/HR consulting style. Framework-driven, data-backed, strong judgment.
4	Psycho Style	Fusion	Extreme fusion of human touch × consulting. Bold judgment, data-backed, sharp-tongued but every word holds up.

Relationship Between Styles

Default Style (Baseline)
  ├─ + Human touch + Business-driven → Colleague Style
  ├─ + Framework sense + Data sources + Methodological transparency → Consulting Style
  └─ + All the honesty of Colleague + All the professionalism of Consulting + Sharpness → Psycho Style

Default Style is the foundation. All styles are built on its structural rules (how to start, how to layer, how to conclude).
Colleague Style and Consulting Style are independent branches, each adding different emphases on top of the default.
Psycho Style is the fusion of both branches, and also the style with the most tension. For internal documents, Colleague Style and Psycho Style overlap heavily.

When to Choose Which

Scenario	Recommended Style	Why
Weekly reports, meeting minutes, announcements, routine proposals	Default Style	Needs clarity and actionability, no excessive stylization
Client-facing proposals, client training, internal thinking	Colleague Style	Needs to be business-driven, warm, with judgment
Strategic proposals, industry analysis, investment advice	Consulting Style	Needs framework sense, data support, methodological transparency
Internal strategic discussions, retrospectives, speaking the truth	Psycho Style	Needs sharp judgment, honesty that's uncomfortable
Client-facing proposals + strong framework sense	Colleague + Consulting	Personal warmth combined with institutional professionalism
Internal thinking + extreme honesty	Colleague + Psycho	In internal documents, these naturally overlap; no explicit combination needed

Usage Flow

Step 0: Proactively Ask About Style

When the user requests a document without specifying a style, do not start writing immediately. First, list the available styles and let the user choose. Use the following fixed script:

I currently support these writing styles. Which one do you think fits best?

1. **Default Style** — Clear structure, directly actionable. Good for proposals, reports, meeting minutes, and weekly reports.
2. **Colleague Style** (Dai Tong's personal style) — Business-driven, with judgment, like a colleague talking. Good for client-facing proposals, internal thinking, and training materials.
3. **Consulting Style** (MBB/Big Four/HR Consulting) — Professional, credible, drives decisions. Good for strategic proposals, industry analysis, and investment advice.
4. **Psycho Style** — An extreme fusion of human touch × consulting. Bold judgment, data-backed, sharp-tongued but every word holds up. Good for internal strategic discussions and retrospectives.

You can also combine styles: "Colleague Style + Consulting Style" or "Colleague Style + Psycho Style."

Whiteboard visual summaries will be automatically inserted at the beginning, key sections, and end of the document. No extra specification needed. The whiteboard style follows the writing style you choose.

If the user specifies a style upfront, skip this step.

Steps 1-5: Assess → Choose Structure → Write Sentences → Add Whiteboard → Publish

Assess the document type, audience, and target action. If the information is incomplete but reasonable assumptions can be made, continue writing without interrupting the flow for minor gaps.
Choose the structure before writing sentences. Prioritize using the skeleton from references/templates.md.
Write sentences following the rules of the selected style. Default style rules are below; rules for other styles are in their respective reference files.
After finishing writing, generate the whiteboard. Read references/whiteboard-guide.md. Select the whiteboard style based on the writing style, and determine the content for three whiteboards based on the document type. Whiteboard capabilities and 24 color schemes are built into this skill's whiteboard/ directory (from zara's beautiful-feishu-whiteboard, MIT license). Generate SVG according to the hard constraints in whiteboard/RULES.md and insert into a Feishu whiteboard. If whiteboard generation fails, do not block; fallback to a plain text-only document.
When actually creating or updating a Feishu document, switch to lark-doc for execution, embedding the whiteboard link into the corresponding position in the document.

When Rewriting an Existing Document

First, determine whether the user provides a "target draft" or "reference material."
Reference material: First extract the topic, conclusions, audience, and reusable facts, then rewrite for the target scenario. Do not treat the original structure, length, or wording as constraints.
Target draft: First preserve the facts and decisions, then address tone, order, and redundancy. Delete duplicates first, then fill gaps, then adjust tone.
If the original facts are unclear, do not add facts on your own; mark them with "To be confirmed" or "Assumption."
Only polish if the user asks for it, without changing facts, messaging, conclusions, or responsibility assignments.

Default Style Rules

The following 8 rules are the baseline for the default style and the foundation for all other styles. When using the Consulting, Colleague, or Psycho styles, these rules still apply but may be overridden or adjusted by the specific rules of each style.

0. Be Human — The Writer Must Be Present

A document without a "human touch," even if clearly structured and complete in information, reads like machine-generated. A human touch is not about being "casual" — it's about making the reader feel: This is a person, based on their own judgment and experience, writing to another person.

Use specifics instead of generalizations. Don't write "There is some risk," write "If the data validation can't be completed by Friday, the historical records will be missing after launch." Don't write "User feedback has increased recently," write "Ticket volume has increased by 40% over the past three days, concentrated on login timeouts."
Have judgment, not just information. Dare to say "I think," "I'm not sure," "I lean toward."
Sentences should breathe. Short sentences are powerful; long sentences provide detail. Alternate between them. A paragraph should not exceed 5 lines.
Honesty is more important than being correct. If you don't know, say so. If you're not sure, say "still verifying."
Delete the markers of an absent writer. "Upon evaluation, we believe…" → "I judge…" ; "It is suggested to consider…" → "I suggest…" ; "In summary…" → delete it.

For detailed techniques, see references/voice-guide.md.

1. State the Purpose at the Beginning

The first 2-4 sentences must answer: What is this? Why is it relevant now? What does the reader need to know or do? Do not start with a large background section before getting to the main content. For decision-oriented documents, start directly with the recommendation or conclusion. For status-update documents, start directly with progress, risks, and next steps.

2. Structure Content Around the Reader's Questions

Titles must be specific, including the object and action. Avoid empty titles like "Project Progress" or "Proposal Description."
A section should do only one thing. Do not mix background, conclusions, and action items in the same paragraph.
Write processes as numbered lists. Write parallel comparisons as tables. Do not force explanatory content into tables.
Prioritize stable H2s: Background, Goal, Current Status, Proposal, Impact, Risk, Next Steps, Items to Confirm.

3. Keep Sentences Short, Subject Clear, and Actions Explicit

Prefer active voice over passive voice.
Be clear about the subject: who is responsible, who decides, who is affected. Avoid vague terms like "this," "it," "relevant parties."
Try to convey only one judgment per line.
Use "need," "please," "will," "must" for actions that are required. Do not use "can," "could consider," "it is recommended that" to create ambiguity.
Minimize nominalizations; prioritize converting abstract nouns back into verbs.

4. Tone Should Be Restrained, Not Pompous

The tone should be direct, calm, and credible — not lively or slogan-like.
Delete filler words that convey no information: comprehensive, systematic, in-depth, strong, empower, leverage, closed-loop, high-quality advancement.
Avoid phrases like "we believe," "it should be noted here," "in order to better." If you can state the conclusion directly, do so.
Restraint is not coldness. After deleting empty words, what should remain is the writer's genuine judgment, specific observations, and honest attitude.

5. Make Execution Information Explicit

Write specific dates or ranges for timing. Do not write "soon" or "as soon as possible."
Write the responsible person or role. Do not write "relevant colleague" or "corresponding team."
List decisions separately under "Conclusion" or "Decisions Needed."
Write the trigger conditions, impact, and mitigation actions for risks. Do not just write "there is some risk."
Use specific scenarios instead of abstract descriptions. Do not write "when concurrency is high, performance bottlenecks may occur," write "if QPS exceeds 5000, the current single-instance deployment will experience timeouts. See the appendix for load test data."

6. Formatting Serves Readability, Not Aesthetics

Keep paragraphs short. Split continuous long paragraphs.
List items should be parallel; the first word of each item should preferably be of the same type.
Use bold only for key conclusions, objects, and actions; do not bold entire paragraphs.
Use callouts only for warnings, critical constraints, and critical decisions. Do not add hint boxes to every section.
Use tables only when a two-dimensional comparison is clearly better for readability.

7. Output According to Document Type

Proposals, pitches, decisions: Conclusion first, then background, followed by proposal, impact, risks, and next steps.
Status reports, weekly reports: Start with changes in the current period, then risks and blockers, then actions for the coming week.
Meeting minutes: Start with conclusions and action items, then record the discussion process.
Announcements, notifications: Start with the change, effective date, scope of impact, and reader actions.

Style Reference Files

Each style has its own reference file with detailed techniques, examples, and rules. These are only read when the user selects the corresponding style:

Style	Reference File	When to Read
All styles (Human touch techniques)	`references/voice-guide.md`	When needed for Default, Colleague, or Psycho styles
Consulting Style	`references/consulting-style.md`	When user requests Consulting Style
Colleague Style	`references/colleague-style.md`	When user requests Colleague Style
Psycho Style	`references/psycho-style.md`	When user requests Psycho Style

Tool Reference Files

The following files are writing tools, not tied to any specific style:

File	Purpose	When to Read
`references/templates.md`	Common document skeletons	When drafting from scratch or restructuring
`references/rewrite-patterns.md`	Common bad writing patterns and rewrite examples	When polishing sentences or deleting filler
`references/sources.md`	Rule sources and rationale for distillation	When user asks "why write this way" or when resolving rule conflicts
`references/whiteboard-guide.md`	Whiteboard usage guide (style mapping, insertion strategy, generation flow)	When writing a document that needs a whiteboard
`whiteboard/`	24 whiteboard color schemes + whiteboard hard constraints (embedded, from zara's beautiful-feishu-whiteboard)	When generating a whiteboard

By default, do not expand all references at once. Read minimally based on the current task.

Example Requests

"Use Chinese Teacher to rewrite this proposal to sound more like an official work document."
"Polish this weekly report, keep the facts the same, but make it clearer."
"Draft a meeting minutes for me, starting with the conclusion and action items."
"Rewrite this client proposal using Colleague Style, business-driven, like a colleague talking."
"Write this industry analysis in Consulting Style, with judgment, like McKinsey."
"Write this industry analysis in Colleague Style + Consulting Style, with judgment and a sense of framework."
"Write this strategic suggestion in Psycho Style. I want a human touch, and professional judgment."

Final Self-Check

After writing any document, check against these 5 points:

Can a reader understand "What this is, why now, and what I need to do" within 30 seconds?
Does the title of each section stand independently?
Does every important action have an owner, timing, or trigger condition?
Are there no filler words kept just to sound formal?
If most of the adjectives were deleted, would the document still hold up?

Chinese Teacher / 中文老师

What is 中文老师?

Ask in your favorite AI

Documentation