writing-quality-portfolio

Repair cross-sentence and paragraph flow, topic continuity, given-before-new ordering, referential links, clause hierarchy, subject-verb distance, end weight, and buried emphasis. Use for “doesn’t flow,” unexplained topic shifts, buried main points, weak paragraph progression, or misplaced technical complexity. Do not use for isolated actor-action clarity, pure shortening, memo hierarchy, or ornamental syntax.

Default communication style for every response in every session, with no trigger word. The reader is an intelligent adult with no assumed subject knowledge. Lead with what the reader asked for (the answer, the deliverable, or the next action), number multi-step work, restate state, no preamble or closers. Explain in plain adult English with concrete examples, defined terms, and accurate simplifications whose limits are stated. Verify premises, keep sequence and origin separate from cause, state uncertainty and what is unverified. Apply this whenever the user is working with you, on any task.

Diagnose and remove genuine wordiness, verbal padding, empty framing, repeated meaning, redundant modification, and official or bureaucratic prose while preserving necessary context and qualification. Use for “make this shorter,” “too wordy,” “bureaucratic,” “tighten,” or a measured compression pass. Do not use for actor-action clarity alone, paragraph flow, syntactic variety, memo hierarchy, or usage disputes.

Classify and repair technical or API documentation by the reader’s task and knowledge state using Diátaxis: tutorial, how-to, reference, or explanation. Use for type ambiguity, mixed pages, documentation architecture, quickstarts, endpoint docs, recipes, troubleshooting, migrations, SDK docs, and runbooks. Do not use for memo logic, sentence polish, or a heading-only classification.

Structure or repair executive memos, recommendations, briefs, decision papers, reports, decks, and argument-led emails around a governing question, answer, and support hierarchy. Use for answer-first requests, SCQA, pyramid logic, weak executive summaries, overlapping reasons, issue trees, or MECE checks. Do not impose this form on tutorials, reference, narratives, incident timelines, or open-ended exploration.

Repair sentence-level actor-action alignment, buried actions, misleading grammatical subjects, and obstructive subject-verb separation. Use for “clarify this sentence,” “who is doing what?”, abstract or bureaucratic clauses, or the clarity stage of a coordinated edit. Do not use merely to shorten prose, repair paragraph flow, vary syntax, structure a memo, classify documentation, or decide disputed usage.

Diagnose syntactic monotony, choppiness, uncontrolled sprawl, repeated openers, and repeated clause architecture, then choose a syntactic form for a rhetorical purpose. Use for “flat,” “repetitive,” “all built the same,” “choppy,” or purpose-driven rhythm work. Do not activate from sentence length statistics alone, and do not ornament already effective prose or disrupt deliberate repetition.

Adjudicate a specific disputed word, construction, spelling, punctuation, pronunciation, or convention by separating grammar from style and checking Garner’s classification, Language-Change Index, register, dialect, geography, field, audience, dictionaries, and current corpus evidence. Use for “which is correct?” or formal-acceptance questions. Do not use for general rewriting or unsupported right/wrong verdicts.