prose-standard
Prose Standard
Write enough to preserve the contract, then remove reasoning transcripts, repetition, and decoration. A contract is an obligation, invariant, precondition, postcondition, or compatibility promise that a caller, callee, implementer, producer, consumer, reader, or maintainer relies on. This skill owns editorial judgment and required prose coverage; follow your repository's documentation standard for placement, budgets, bilingual pairs, and documentation gates, and audit reasoning-transcript leakage — dead session citations, change narration, review choreography, hedges — with its own taxonomy. It is guidance, not a script.
Treat contract, boundary, shape, surface, seam, gate, and vocabulary as terms to check before use, not banned words. First ask whether the exact rule, API, field set, type, validation, timing point, component split, or failure states the fact better. Keep a term when it names the exact technical subject, including caller/callee contracts and security or process boundaries.
Inputs and exclusions
Require an explicit scope. If it is missing, report the required input and stop; do not infer a repository-wide scope or begin an interview.
Accept mode: automatic | interactive; default to automatic. Enter interactive mode only when the user explicitly requests questions or calibration. mode controls questions, not write authority: review and audit tasks report findings without editing; explicitly requested write, fix, or trim tasks apply clear changes.
Always exclude vendor/ from discovery, review, and edits, even when the requested scope is the whole repository. Do not follow a symlink into it. Put exclusions after inclusion globs so a later include cannot re-admit it — for example, end ripgrep commands with --glob '!vendor/**' and give Git commands an explicit :(exclude)vendor/** pathspec. If the requested scope contains only vendor/, report that no eligible files remain.
Also exclude frozen archived notes from review and edits. Archived notes are frozen snapshots; inspect an exact target only to understand a historical inbound citation, never to modernize its prose or outbound links.
Treat generated catalogs, snapshots, and fixtures as derivative. Edit the owning source or scenario first, then regenerate the artifact. When a generator extracts a summary from owner prose, make the extracted sentence complete for that surface. Bilingual pairs have no permanent owner: either language may be the authored side for an update, and the counterpart must follow in the same change.