From taches-principled
Apply Strunk & White's Elements of Style to make documentation clearer, stronger, and more professional. Active voice, positive form, concrete language, omit needless words.
How this skill is triggered — by the user, by Claude, or both
Slash command
/taches-principled:write-conciselyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
IF writing or editing documentation for human readers → Apply the full set of composition principles
IF writing or editing documentation for human readers → Apply the full set of composition principles IF reviewing existing text for conciseness → Apply Omit Needless Words, Active Voice, Positive Form IF writing code comments or internal docs → Focus on clarity and concreteness, skip usage rules IF translating technical content to user-facing docs → Prioritize concrete language and positive form
Apply Strunk & White's Elements of Style principles to any text a human will read. Claude already knows these rules — this skill exists to remind you to apply them. Do not explain the rules in your output; simply apply them.
| Avoid | Prefer |
|---|---|
| the fact that | since, because |
| in a hasty manner | hastily |
| he is a man who | he |
| due to (adverbial) | because of |
| along these lines | rephrase directly |
| the question as to whether | whether |
| there is no doubt but that | no doubt |
When writing documentation, run through each principle mentally and check your text for violations. The most impactful ones to apply:
Do not enumerate which rules you applied in your output. Simply produce cleaner text.
Claude already knows these rules from training. The skill's only job is to trigger their application. Full rule text wastes context and adds no behavioral change.
npx claudepluginhub git-fg/taches-principled --plugin tp-session-auditProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.