feat(rules): add clear technical prose to Manner layer - #2
Merged
Conversation
Extend Grice Manner with active voice, short full sentences, filler cuts, and exact preservation of code/paths/APIs/errors—without STE compliance claims or caveman-style fragment defaults. Co-authored-by: Cesar Delgado <beettlle@users.noreply.github.com>
beettlle
marked this pull request as ready for review
July 30, 2026 19:23
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
2 participants
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.
Summary
Adds a dense Clear Technical Prose rule under Grice Manner, inspired by Orwell-style brevity and Boeing’s public STE digest, while rejecting full ASD-STE100 dictionaries and caveman-style article-dropping fragments.
§9.8aingeneral-llm-anti-patterns.mdc: active voice, short full sentences, one claim per sentence, cut filler/pleasantries, keep code/paths/APIs/errors exact, expand for security/irreversible/ambiguous steps§9.6–9.8aTest plan
python3 scripts/validate-rules.py— 0 errorsverification pending) remains allowedRisks
general-llm-anti-patterns.mdc+~17 lines). Mitigated by dense Bad/Good format and no new always-on file.