Add catalog-colon writing pattern#171
Open
creatornader wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
What
Adds pattern #34 for a sentence shape where an LLM writes a lead-in claim, a colon, and a polished catalog of abstract benefits.
This is related to the existing rule-of-three and inline-header list patterns, but it catches the prose form rather than bullet labels.
Why
This is not a blanket colon ban or phrase ban. It is meant for the cluster where the colon introduces the sentence's real point, the list is abstract benefit language, and the line often overlaps with rule-of-three rhythm.
The false-positive rule keeps ordinary definitions, commands, labels, and code-oriented colons intact.
Prior feedback
I saw the feedback on #132 about overfit phrase guardrails. This patch avoids that shape: it adds a real numbered pattern, keeps README, version, and plugin metadata in sync, and describes a reusable sentence pattern rather than banning a common technical phrase.