ormus-solutions/librecopy-claude-code/style-guide-patterns
- community
Checking that the SKILL.md file is still in the repository.
Style rule patterns: the 10-rule principle, do and don't pairs, terminology governance, voice and tone documentation, specific inclusive language rules, reading level enforcement, and anti-patterns. Use when writing the rules of a style guide.
Install
npx vskill@latest install ormus-solutions/librecopy-claude-code/style-guide-patternsSKILL.md
Style Guide Patterns
The 10-Rule Principle
A style guide with 100 rules is a style guide no one reads. A style guide with 10 high-impact rules, automated by Vale, will actually be followed.
Before writing any rule, answer: "Is this in the base guide already (Google, Microsoft)?" If yes, do not duplicate it. Link to it. Write only the rules where you differ or extend.
The 10 most impactful rules for most technical teams:
- Person (second vs. third)
- Tense (present vs. future)
- Voice (active vs. passive)
- Core terminology (3-5 terms your team consistently gets wrong)
- Code formatting (inline vs. block, language hints)
- Heading case (title case vs. sentence case)
- Inclusive language (team-specific banned terms)
- Tone by context (at minimum: tutorial vs. reference)
- Numbers (numeral vs. spelled out)
- Contractions (always/never/context-dependent)
The Do/Don't Pair Pattern
Every rule needs a concrete example from your domain. Abstract rules are ignored:
Terminology Governance Pattern
A terminology decision needs three things to stick:
- The rule (what to use)
- The rationale (why -- without this, people relitigate it forever)
- Automation (Vale substitution rule -- without this, it will be ignored)
The (?i) makes the pattern case-insensitive. Test with vale sync && vale docs/.
Voice vs. Tone Documentation Pattern
Most style guides document voice OR tone, not both. Document both explicitly:
Inclusive Language Rule Specificity
"Be inclusive" is not enforceable. Specific term substitutions are:
Reading Level Enforcement
Vale's built-in readability rules:
Or use a custom rule:
Anti-Patterns
The Rules-Without-Examples Guide
The 100-Rule Guide
A guide with 100 rules signals the author wanted to demonstrate thoroughness rather than change behavior. Rules beyond the top 10 will not be read. Provide a "quick reference" of 10 rules + link to the base guide for comprehensive coverage.
Unenforced Rules
A rule without automation is a rule that relies entirely on reviewer memory. For every rule, decide:
- Can Vale enforce this? → Write a Vale rule.
- Can a PR template remind reviewers? → Add to PR checklist.
- Relies only on writer training? → Prioritize Vale automation.
The Style Guide That Never Ships
Waiting for a perfect guide before sharing it means no guide ever ships. Start with 5 rules and a Vale config. Add rules as you encounter real inconsistencies in code review.
References
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/style-guides/skills/style-guide-patterns/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/ormus-solutions/librecopy-claude-code/style-guide-patterns)