communicate（communicate 搜索）

Communicate

Comprehensive written expression skill. 16 techniques across 5 categories (plus a tradition meta-lens and omit gate) for crafting prose that communicates clearly, honestly, engagingly, and appropriately for its audience and rhetorical tradition. Routes to structured workflows for common tasks or applies techniques ad-hoc.

Intent Routing

Detect user intent and route to the appropriate mode. When ambiguous, default to ad-hoc technique application. If scope becomes clear mid-conversation, route to the appropriate workflow.

Bridge as interrupt: The Bridge workflow can interrupt any active workflow. When a thought resists English expression mid-workflow, load @./references/workflow-bridge.md for the stuck passage, then return to the active workflow.

Context Loading

Load only what the current route requires. Never load all references upfront.

Tradition Meta-Lens and Omit Gate

Tradition. Load before any technique. Identify the rhetorical tradition operating in the prose before applying diagnostics — this prevents Anglo-American conventions from functioning as an invisible default and modifies how all downstream questions fire.

@./references/tradition.md

Why it matters: every diagnostic question below assumes a rhetorical context. "Can a reader follow linearly?" fails for Arabic parallel-restatement. "Does language commit?" fails for Japanese epistemic calibration. Tradition identification prevents misdiagnosis.

Omit gate. Before repairing any passage, ask: *Should this content exist at all?* Not every gap is a flaw — some silences are structural. Intentional omission sharpens focus by refusing to dilute a point. Strategic silence lets the reader complete the thought, which lands harder than spelling it out. Productive ambiguity preserves openness where premature precision would close inquiry. If the answer is "this content shouldn't exist," the repair is deletion, not technique application.

Orientation

Treat reader attention as finite. Interrogate each word: does it earn its place?

Difficulty should come from complex ideas, not complex sentences. When prose is hard to parse, the writer has shifted work to the reader. Expression techniques identify where this happens and provide repair strategies.

Most common failures — watch for these before loading technique files:

• NEVER let abstractions float without grounding — load illustrate (which includes grounding moves) to anchor claims in concrete instances.
• NEVER preserve passive voice because it sounds formal — passives hide actors, which hides responsibility.
• NEVER conflate confidence with certainty — absolute language on inferred content creates dishonest prose.
• NEVER allow AI diction patterns to survive: "it's worth noting", "it's important to", "in conclusion" — these are register failures, not stylistic choices.
• NEVER fix word-level issues before structural ones — hedges and weak verbs on misordered prose are noise, not signal.
• NEVER treat all hedging as weakness — hedging split (calibration vs. cushioning) is mandatory.

Default triage path: When unsure where to start, load tradition first, then check form-function alignment, then structural clarity — most prose problems are sequence problems. The default path is: tradition (load first) → fit → clarify → activate → strengthen → signal-confidence.

Diagnostic Questions

When improving prose ad-hoc, interrogate it with diagnostic questions. Each question that surfaces issues points to its technique file for detailed repair instructions.

Purpose

Clarity

Integrity

Shape

Depth

Loading Techniques

To apply a technique, load its reference file:

@./references/{name}.md

CRITICAL: A technique reference file MUST be loaded before claiming to apply that technique. Reading the technique name in this skill file does NOT constitute applying the technique.

Technique Library

16 techniques in ./references/.

Load the full technique index for extended navigation:

@./references/index.md

Ad-Hoc Use

For applying techniques outside workflow routes:

1. Load tradition lens — identify the rhetorical tradition before any diagnostic
2. Check the omit gate — ask whether the content should exist before repairing it
3. Interrogate the prose with diagnostic questions from the tables above
4. Select technique(s) based on which questions surface issues
5. Load technique reference file(s) for detailed instructions
6. Follow the Instructions section of each loaded technique

NEVER

• NEVER apply any diagnostics without first loading tradition — tradition meta-lens must precede all technique application.
• NEVER treat all hedging as weakness — the hedging split is mandatory: distinguish epistemic calibration (preserve) from habitual cushioning (cut).
• NEVER smooth productive friction without asking — irregular rhythm, unresolved tension, and deliberate register shifts are interrogated before normalized.
• NEVER fill intentional gaps — gap-check precedes every addition: ask "is this gap doing rhetorical work?" before filling.
• NEVER correct L1 grammatical patterns as errors — diagnose what the pattern encodes before treating it as a problem.
• NEVER fix word-level issues before structural ones — hedges and weak verbs on misordered prose are noise, not signal.
• NEVER default to Anglo-American conventions invisibly — name tradition-specific choices as tradition-specific, not universal.

Additional Resources

• @./references/clarify-patterns.md — Detection heuristics and repair strategies
• @./references/clarify-examples.md — Before/after transformations by issue type