From compound-engineering
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. Triggers on "edit for style", "review article", "check grammar", "Every style guide", "proofread", "copy edit", or requests to check written content for grammar, punctuation, mechanics, and style compliance.
How this skill is triggered — by the user, by Claude, or both
Slash command
/compound-engineering:every-style-editorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- [Overview](#overview)
This skill provides a systematic approach to reviewing copy against Every's comprehensive style guide. It transforms Claude into a meticulous line editor specializing in grammar, mechanics, and style guide compliance.
Use when:
| Phase | Focus | Actions |
|---|---|---|
| 1. Initial Assessment | Context | Understand document type, audience, tone |
| 2. Detailed Line Edit | Content | Check grammar, punctuation, word choice, style rules |
| 3. Mechanical Review | Formatting | Verify spacing, formatting, numbers, links |
| 4. Recommendations | Actionable | Provide improvement suggestions |
Present findings using this structure:
DOCUMENT REVIEW SUMMARY
=====================
Document Type: [type]
Word Count: [approximate]
Overall Assessment: [brief overview]
ERRORS FOUND: [total number]
DETAILED CORRECTIONS
===================
**Location**: [Paragraph #, Sentence #]
**Issue Type**: [Grammar/Punctuation/Mechanics/Style Guide]
**Original**: "[exact text with error]"
**Correction**: "[corrected text]"
**Rule Reference**: [Specific style guide rule violated]
---
RECURRING ISSUES
===============
[Patterns of errors appearing multiple times]
STYLE GUIDE COMPLIANCE CHECKLIST
==============================
✓ [Rule followed correctly]
✗ [Rule violated - with count]
FINAL RECOMMENDATIONS
===================
[2-3 actionable suggestions]
| Category | Rule |
|---|---|
| Headlines | Title case for headlines, sentence case elsewhere |
| Tone | Active voice, avoid overused words (actually, very, just) |
| Numbers | Spell out one-nine; numerals for 10+ |
| Punctuation | Oxford commas, em dashes without spaces |
| Capitalization | Lowercase job titles, "it" for company, "they" for teams |
| Emphasis | Italics only (no bold for emphasis) |
| Links | 2-4 words, never "click here" |
Full style guide: EVERY_WRITE_STYLE.md
Based on Every's style guide:
Before delivering edited copy:
| File | Purpose |
|---|---|
| EVERY_WRITE_STYLE.md | Complete Every style guide (29KB) |
npx claudepluginhub spillwavesolutions/compound-engineering-plugin --plugin compound-engineeringCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.