This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
/plugin marketplace add EveryInc/compound-engineering-plugin/plugin install compound-engineering@every-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/EVERY_WRITE_STYLE.mdThis skill provides a systematic approach to reviewing copy against Every's comprehensive style guide. It transforms Claude into a meticulous line editor and proofreader specializing in grammar, mechanics, and style guide compliance.
Use this skill when:
This skill enables performing a comprehensive review of written content in four phases:
Begin by reading the entire piece to understand:
Review each paragraph systematically, checking for:
Reference the complete EVERY_WRITE_STYLE.md for specific rules when in doubt.
Verify:
Present findings using this structure:
DOCUMENT REVIEW SUMMARY
=====================
Document Type: [type]
Word Count: [approximate]
Overall Assessment: [brief overview]
ERRORS FOUND: [total number]
DETAILED CORRECTIONS
===================
[For each error found:]
**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]
**Explanation**: [Brief explanation of why this is an error]
---
RECURRING ISSUES
===============
[List patterns of errors that appear multiple times]
STYLE GUIDE COMPLIANCE CHECKLIST
==============================
✓ [Rule followed correctly]
✗ [Rule violated - with count of violations]
FINAL RECOMMENDATIONS
===================
[2-3 actionable suggestions for improving the draft]
The complete Every style guide is included in EVERY_WRITE_STYLE.md. Key areas to focus on:
Based on Every's style guide, pay special attention to:
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.