Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR builds on #825: its evaluations and rule decisions framed this work. It adds rules for the problems that kept coming back in Claude's docs drafts over the last two weeks, across different articles and often after an earlier correction.
Why these changes
Each change starts from a recurring correction, compared with
editorandwriting-planneras they stand after #825. I reviewed every change individually: many were rewritten or narrowed, and the ones that didn't hold up as general rules were dropped.The main finding: most rules exist, but their tests or examples don't match the cases that actually come up. As a result, most changes extend an existing line with a sharper test or a ❌/✅ pair taken from accepted wording, instead of adding a new rule.
Fit with #825
The changes follow #825's decisions and reverse none of them. Corrections that conflicted with a decision stayed out, and most changes extend an existing line rather than add to
editor.What changes
writing-plannerheading tree: each heading answers its own question, names what the reader wants to do, and differs from its siblings on what the reader decides by.editorArea 4: terms explained before use, comparisons with a stated base, a test for second readings, and a reason for every constraint.editorprocess sections: referent tests on every proposed rewrite, and a cut instead of a patch for a claim proven wrong.Next
Test these rules the way #825 tested its own, and add the correction-to-rule loop to
doc-author.