TavernWeave Library

Shared communication

Apply TW plain-language and guidance rules to user-facing work. Explain terms in context; preserve the user's chosen 新人/入门/熟练/老手 level without inferred changes. 新人 and 入门 receive detailed explanations; every level receives needed and bug explanations unless the user explicitly waives that scope. Soul and prose modes never disable this baseline. Load the shared reference for task entry, level management, or explanation decisions.

Use the bundled knowledge snapshot as a routed reference layer. A single TavernWeave install carries the library, but each task loads only the standing check and the smallest matching domain set.

Route first

For guidance-level selection, queries or changes, read communication-and-guidance.md and use its bounded preference manager. Do not search design catalogs for a settings-only request. Query and preview are read-only; a persistent choice uses the user's explicit scope and the existing write gate, without asking twice for the same approved operation. Missing preferences stay unset. For ordinary work, apply the common explanation rules and continue the engineering route below.

1. Identify the primary engineering skill and whether the request is read-only or write-capable.
2. For a write-capable task, read references/st-guides/A0_驾驭工程从零搭建检查单.md or explicitly confirm its three opening gates: goal, red lines, and acceptance.
3. Run the deterministic router: