write

Name: write
Author: tw93

6.6kstars384forks

How to install write?

tw93/waza/write

$npx -y skills add tw93/Waza --skill write

Installs into the current project.

Summary

Rewrites and polishes prose in Chinese or English, removes AI-like wording, and reviews product localization copy while preserving intent for drafts, docs, release notes, launch copy, and social posts. Use when users ask in any language to draft, rewrite, proofread, localize, pol

Files · 1

View on GitHub

SKILL.md

1	# Write: Cut the AI Taste
2
3	Prefix your first line with 🥷 inline, not as its own paragraph.
4
5	Update check (non-blocking). Once per conversation, run `bash <skill-base-dir>/scripts/check-update.sh` with `<skill-base-dir>` replaced by this skill's base directory; relay any printed line, otherwise continue silently (also when the script already ran, is missing, or errors). It checks at most once a day, reads only a public version file, and sends no data.
6
7	Strip AI patterns from prose and rewrite it to sound human. Do not improve vocabulary; remove the performance of improvement.
8
9	## Outcome Contract
10
11	- Outcome: the prose preserves the author's intent while sounding natural for its audience and surface.
12	- Done when: meaning, factual claims, and structure are preserved unless the user asked to change them, and AI-like wording is removed; punctuation and CJK/Latin mixing pass the Punctuation Gate for the output language.
13	- Evidence: supplied text, target audience, project style references, release or product state, and requested language.
14	- Output: the edited prose only, unless the user asked for notes, variants, or review comments.
15
16	## Core Stance
17
18	This skill is a catalog of smells, not a checklist to run top to bottom. Use it to recognize AI taste, then make judgment calls. The reference files (especially `write-zh.md`) are long because they accumulated examples over many sessions; do not try to apply every rule to every text. Applying more rules is not doing a better job.
19
20	- Over-editing is failure, equal to under-editing. If a sentence is already natural, clear, and stable, leave it. Most polish is subtraction (cut repetition, summary-tone, restated conclusions), not phrase-by-phrase replacement.
21	- The author's voice wins. Keep the author's existing colloquial words, cadence, and stance. When a rule conflicts with a deliberate authorial or genre choice (a question title in a narrative piece, a list the author wants kept), the author wins. Rules are defaults, not laws.
22	- Banned-phrase lists and replacement tables are examples, not find-and-replace. A flagged word that reads naturally in context stays. Match the smell, not the string.
23	- Prefer fewer, stronger edits. Three changes that matter beat thirty mechanical swaps that flatten the voice.
24
25	When distilling a new lesson into this skill, fold it into an existing principle instead of appending another banned phrase. This skill must not grow monotonically; collapsing specifics back into principles is part of maintaining it.
26
27	## Pre-flight
28
29	1. Text present? If the user gave only an instruction with no actual prose to edit, ask for the text in one sentence. Do not proceed.
30	2. Audience locked? If the intended audience is unclear and cannot be inferred from the text (blog reader vs RFC vs email), ask before editing. Junior engineer and senior architect prose should read completely different.
31	3. Language detected from the text being edited, not the user's command:
32	- Contains Chinese characters + release notes or social post mode → load `references/write-zh-release-notes.md`
33	- Contains Chinese characters + bilingual or translation review → load `references/write-zh-bilingual.md`
34	- Product/site/app localization review across multiple locales → load `references/write-product-localization.md`; also load `references/write-zh-bilingual.md` when Chinese copy is present
35	- Contains Chinese characters (default prose) → load `references/write-zh-prose.md` (quick rules); load `references/write-zh.md` for the full AI-taste pattern catalog
36	- Otherwise → load `references/write-en.md`
37
38	No summary, no commentary, no explanation of changes unless explicitly asked.
39
40	## Durable Context Preflight
41
42	See [references/durable-context.md](references/durable-context.md) for when to read durable context, the read-order budget, and the memory-type mapping.
43
44	For `/write`: the supplied text and current release state override memory. Durable preferences can set brevity, tone, and social-post shape; they do not override the hard rule to edit in place, keep meaning intact, and avoid change lists unless the user explicitly asks.
45
46	## Hard Rules
47
48	- Meaning first, style second. If removing a

People who liked this also viewed

6 picks

Type

write

6.6kstars384forks

View on GitHub

How to install write?

tw93/waza/write

$npx -y skills add tw93/Waza --skill write

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Write: Cut the AI Taste
2
3	Prefix your first line with 🥷 inline, not as its own paragraph.
4
5	Update check (non-blocking). Once per conversation, run `bash <skill-base-dir>/scripts/check-update.sh` with `<skill-base-dir>` replaced by this skill's base directory; relay any printed line, otherwise continue silently (also when the script already ran, is missing, or errors). It checks at most once a day, reads only a public version file, and sends no data.
6
7	Strip AI patterns from prose and rewrite it to sound human. Do not improve vocabulary; remove the performance of improvement.
8
9	## Outcome Contract
10
11	- Outcome: the prose preserves the author's intent while sounding natural for its audience and surface.
12	- Done when: meaning, factual claims, and structure are preserved unless the user asked to change them, and AI-like wording is removed; punctuation and CJK/Latin mixing pass the Punctuation Gate for the output language.
13	- Evidence: supplied text, target audience, project style references, release or product state, and requested language.
14	- Output: the edited prose only, unless the user asked for notes, variants, or review comments.
15
16	## Core Stance
17
18	This skill is a catalog of smells, not a checklist to run top to bottom. Use it to recognize AI taste, then make judgment calls. The reference files (especially `write-zh.md`) are long because they accumulated examples over many sessions; do not try to apply every rule to every text. Applying more rules is not doing a better job.
19
20	- Over-editing is failure, equal to under-editing. If a sentence is already natural, clear, and stable, leave it. Most polish is subtraction (cut repetition, summary-tone, restated conclusions), not phrase-by-phrase replacement.
21	- The author's voice wins. Keep the author's existing colloquial words, cadence, and stance. When a rule conflicts with a deliberate authorial or genre choice (a question title in a narrative piece, a list the author wants kept), the author wins. Rules are defaults, not laws.
22	- Banned-phrase lists and replacement tables are examples, not find-and-replace. A flagged word that reads naturally in context stays. Match the smell, not the string.
23	- Prefer fewer, stronger edits. Three changes that matter beat thirty mechanical swaps that flatten the voice.
24
25	When distilling a new lesson into this skill, fold it into an existing principle instead of appending another banned phrase. This skill must not grow monotonically; collapsing specifics back into principles is part of maintaining it.
26
27	## Pre-flight
28
29	1. Text present? If the user gave only an instruction with no actual prose to edit, ask for the text in one sentence. Do not proceed.
30	2. Audience locked? If the intended audience is unclear and cannot be inferred from the text (blog reader vs RFC vs email), ask before editing. Junior engineer and senior architect prose should read completely different.
31	3. Language detected from the text being edited, not the user's command:
32	- Contains Chinese characters + release notes or social post mode → load `references/write-zh-release-notes.md`
33	- Contains Chinese characters + bilingual or translation review → load `references/write-zh-bilingual.md`
34	- Product/site/app localization review across multiple locales → load `references/write-product-localization.md`; also load `references/write-zh-bilingual.md` when Chinese copy is present
35	- Contains Chinese characters (default prose) → load `references/write-zh-prose.md` (quick rules); load `references/write-zh.md` for the full AI-taste pattern catalog
36	- Otherwise → load `references/write-en.md`
37
38	No summary, no commentary, no explanation of changes unless explicitly asked.
39
40	## Durable Context Preflight
41
42	See [references/durable-context.md](references/durable-context.md) for when to read durable context, the read-order budget, and the memory-type mapping.
43
44	For `/write`: the supplied text and current release state override memory. Durable preferences can set brevity, tone, and social-post shape; they do not override the hard rule to edit in place, keep meaning intact, and avoid change lists unless the user explicitly asks.
45
46	## Hard Rules
47
48	- Meaning first, style second. If removing a

People who liked this also viewed

6 picks

Type