Native Writing

Native writing

Write so the reader can follow the thought on the first read. Choose language for the reader's task: deciding whether a product fits, using an interface, following a document, or reading a story. Natural writing can be professional, persuasive, technical, or conversational.

Process

1. Find the point. Infer the reader, purpose, language, and level of formality from the request. For a rewrite, identify the claims, qualifications, requests, and emotional stance that must survive. For a draft, use the supplied facts and intended message. Proceed when you can state what the reader should understand or do; ask only if a missing detail would change that message.

2. Choose the language and form. Read the relevant language reference and any applicable form reference below. The user's samples and explicit preferences take precedence. For mixed text, follow the main language while preserving established terms. For work in a product or repository, inspect nearby copy and the relevant behavior before writing. Proceed when the vocabulary, tone, and form suit the reader and the actual surface.

3. Write the thought. Lead an explanation with its point, then give the reason or detail the reader needs next. Preserve the unfolding of a story when that is its purpose. When a sentence is hard to understand, recover what it says and rebuild it around the action or relationship. Keep clear passages as they are. Finish when each paragraph or interface string serves its purpose and every pronoun or abstract label has a recoverable meaning.

4. Check meaning, then read for flow. Compare the result against the input: names, quantities, dates, conditions, negations, uncertainty, attribution, commitments, and the writer's attitude must retain their meaning. Check both for lost information and newly invented information. Apply the language reference's locale check and the form reference's completion check. Read through in the intended voice; repair places that require backtracking or sound implausible for this speaker. Deliver when the meaning survives and the prose holds together, without chasing a word count or a style score.

References to load

Choose the reference for the requested output language. For multilingual deliverables, read each language being written:

• English
• 台灣繁中, including its required Taiwan terminology reference
• 简体中文

Form, when applicable:

• Website and app copy: landing pages, feature and pricing copy, labels, onboarding, errors, and other interface states. Apply while building a product as well as during copy editing.
• Documentation: README files, tutorials, API references, help articles, specifications, proposals, and internal documents.
• Blogs and essays: developed arguments, personal essays, technical articles, and newsletters.
• Books and manuscripts: fiction, dialogue, and edited nonfiction.

Messages and ordinary replies need only the language reference. A task spanning multiple forms loads only the forms being written.

Editorial judgment

• Give the actor and action when they matter. Keep the same name for the same thing. Use an established technical term when it is clearer than a paraphrase; explain it for readers who need that help. Unpack newly coined labels into what actually happens.
• Let sentence length follow the thought. Keep the connective words that explain cause, sequence, conditions, or disagreement. Use paragraphs for developed ideas, lists for items the reader needs to scan, and headings when they help navigate a longer piece.
• Preserve the author's warmth, frustration, humor, and degree of politeness. Express those through the situation and the writer's actual stance. Do not invent anecdotes, opinions, emotions, measurements, sources, or experience to make a piece feel personal.
• Treat punctuation, familiar idioms, repeated words, and groups of three as ordinary tools. Change them when they obstruct this passage. Follow the language guide’s punctuation reference for the actual surface: a short message, developed prose, a manuscript, and an interface label need different treatment. Preserve useful sentence boundaries, relationships, and intentional rhythm. Code and literal quotations keep their punctuation. Style editing is not an AI-authorship test.
• Replace vague praise with its supported substance. If the input gives no substance, retain only what it actually establishes and flag a material gap briefly. Do not turn an unspecified improvement into an invented feature or a tentative result into a promise. Fact-checking, when requested, is a separate operation from preserving meaning during an edit.

Delivery

For a writing-only request, return the finished prose by default. Add a short note only for an unresolved ambiguity, unsupported material claim, or consequential editorial choice. If asked for critique or alternatives, provide those instead. During implementation, edit the requested product copy or documentation and follow the parent task's delivery requirements. Keep the editorial checklist out of the deliverable.

For a requested voice that these references do not cover, follow the research method in CONTRIBUTING.md to gather suitable samples. Routine writing does not require browsing.