Extend §13 to cover subjectless fragments from humanizing overcorrection#147
Open
juleslemee wants to merge 1 commit into
Open
Extend §13 to cover subjectless fragments from humanizing overcorrection#147juleslemee wants to merge 1 commit into
juleslemee wants to merge 1 commit into
Conversation
§13 currently targets technical/UI voice ("No configuration file needed").
The same surface tell (missing subject) shows up in a different register
when the editor is asked to humanize text and reaches for fragments to
sound casual ("Want to see if X?", "Hit reply to opt out", "Ninety
days since X.").
Extends §13 to cover both registers under the same head:
- SKILL.md: rewrite the Problem paragraph to name two registers,
add a second Before/After pair for the humanizing-overcorrection
case, and add a Distinguished-from-§31 note clarifying that §31
is about runs of fragments for drama; §13 now also covers isolated
fragments produced as a casual-register shortcut.
- README.md: update the §13 row with the second example and a tighter
After-column summary; add 2.8.1 version-history line.
- SKILL.md frontmatter: bump version 2.8.0 -> 2.8.1.
Closes blader#146.
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.
Closes #146.
Extends §13 to cover subjectless fragments produced as a humanizing overcorrection, alongside the existing technical-voice case.
Why
I saw this happen in real use. I was applying the skill to a set of transactional email templates and produced lines like:
All three drop the subject as a shortcut to "sounding casual." The user (a real human) called it staccato and asked for complete grammatical sentences like "Would you like to see how your stance moved?" instead.
§13 already covers the missing-subject tell but only in the technical/UI register ("No configuration file needed"). §31 covers fragments-for-drama but not fragments-for-casual. Neither catches this specific failure: an isolated fragment produced because the editor thought brevity equals naturalness.
What
SKILL.md§13: rewrite the Problem paragraph to name two registers (technical/UI and humanizing-overcorrection), add a second Before/After pair, and add a Distinguished-from-§31 note.README.md: update the §13 table row with the second example and a tighter After-column summary; add a 2.8.1 line to Version History.SKILL.mdfrontmatter: bump version2.8.0->2.8.1.Pattern count stays at 33.
Out of scope
I considered adding this as a new §34 pattern. Decided against it because the underlying tell (missing subject) is identical to §13; the only difference is the register the editor was aiming for. Extending §13 keeps the count stable and surfaces both registers under the same head. Happy to split if you'd rather have a separate §34, though.