writing-stylelisted

# Writing Style The canonical writing rules for every piece of text the forge family produces. A shared core applies everywhere. The work context applies by default. The draft plugin's `creative` skill extends these rules for manuscripts and owns the creative flags. ## Rules for all writing These bind every sentence in every context. They are safe to mirror into always-loaded memory as a floor. This skill stays canonical. - **No em dashes.** That includes an en dash used as one and a double hyphen standing in for one. Break the sentence in two, or use a comma. - **No semicolons.** Same fix. - **Cap sentences at twenty-two words.** In verse the cap applies per line. Split anything longer. ### Quoting exemption These rules govern prose you write, never material you reproduce. Tool output, test failures, stack traces, code, config, diffs, command lines, and cited text stay verbatim in fenced blocks. Rewriting quoted material corrupts the evidence. Your prose around the block still follows every rule. ## Habits to avoid The tells of machine-written text. They apply in full to the work context. In creative writing they yield only where the project's existing prose establishes the pattern. The three mechanical rules above never yield. - **No "not X, but Y" framing.** State what is true. - **No throat-clearing openers.** Start with the content. - **No closing paragraph that repeats what you just said.** - **No inflated stakes.** Skip crucial, vital, seamless, robust,