Agent skill · Documentation

house-style-enforcer

Apply a team's writing style consistently — extract the house style from exemplar documents into a checkable rule card, run the conformance pass on new drafts, and fix violations without flattening the author's voice. Use when asked make this match our style, why do our docs all sound different, build a style guide from our best docs, or check this draft against house style. Produces the extracted rule card, the conformance pass with per-fix reasons, and the voice-preservation line.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill house-style-enforcer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/house-style-enforcer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# House Style Enforcer Skill Most teams have a house style nobody wrote down — it lives in the three documents everyone calls "really good" and gets enforced by vibes in review. This skill makes it checkable: extract the rules from the exemplars (structure, tone registers, formatting conventions, banned constructions), compress them into a one-page rule card, then run drafts against the card — fixing violations *of the card* while leaving the author's voice alone, because style guides that flatten everyone into one android author get ignored in self-defense. ## What This Skill Produces - **The rule card** — one page: structure rules, tone register, formatting conventions, the banned list — each rule with an example from the exemplars - **The conformance pass** — the draft checked rule-by-rule, fixes applied with the violated rule cited - **The voice line** — what the card deliberately does NOT govern (word choice within register, sentence rhythm, personality) — written down so enforcement has a boundary - **The card's maintenance rule** — how rules get added/killed, so the card doesn't become the forty-page guide nobody reads ## Required Inputs Ask for these if not provided: - **Th

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Enforcement Rules
  4. Output Format
  5. The Rule Card (one page)
  6. Conformance Pass: [draft]
  7. Maintenance
  8. Quality Checks
  9. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the house-style-enforcer skill do?

Apply a team's writing style consistently — extract the house style from exemplar documents into a checkable rule card, run the conformance pass on new drafts, and fix violations without flattening the author's voice. Use when asked make this match our style, why do our docs all sound different, build a style guide from our best docs, or check this draft against house style. Produces the extracted rule card, the conformance pass with per-fix reasons, and the voice-preservation line.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill house-style-enforcer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going