every-style-editor▌
everyinc/compound-engineering-plugin · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
This 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.
Every Style Editor
This 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.
When to Use This Skill
Use this skill when:
- Reviewing articles, blog posts, newsletters, or any written content
- Ensuring copy follows Every's specific style conventions
- Providing feedback on grammar, punctuation, and mechanics
- Flagging deviations from the Every style guide
- Preparing clean copy for human editorial review
Skill Overview
This skill enables performing a comprehensive review of written content in four phases:
- Initial Assessment - Understanding context and document type
- Detailed Line Edit - Checking every sentence for compliance
- Mechanical Review - Verifying formatting and consistency
- Recommendations - Providing actionable improvement suggestions
How to Use This Skill
Step 1: Initial Assessment
Begin by reading the entire piece to understand:
- Document type (article, knowledge base entry, social post, etc.)
- Target audience
- Overall tone and voice
- Content context
Step 2: Detailed Line Edit
Review each paragraph systematically, checking for:
- Sentence structure and grammar correctness
- Punctuation usage (commas, semicolons, em dashes, etc.)
- Capitalization rules (especially job titles, headlines)
- Word choice and usage (overused words, passive voice)
- Adherence to Every style guide rules
Reference the complete style guide at references/EVERY_WRITE_STYLE.md for specific rules when in doubt.
Step 3: Mechanical Review
Verify:
- Spacing and formatting consistency
- Style choices applied uniformly throughout
- Special elements (lists, quotes, citations)
- Proper use of italics and formatting
- Number formatting (numerals vs. spelled out)
- Link formatting and descriptions
Step 4: Output Results
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]
Style Guide Reference
The complete Every style guide is at references/EVERY_WRITE_STYLE.md. Key areas to focus on:
- Quick Rules: Title case for headlines, sentence case elsewhere
- Tone: Active voice, avoid overused words (actually, very, just), be specific
- Numbers: Spell out one through nine; use numerals for 10+
- Punctuation: Oxford commas, em dashes without spaces, proper quotation mark usage
- Capitalization: Lowercase job titles, company as singular (it), teams as plural (they)
- Emphasis: Italics only (no bold for emphasis)
- Links: 2-4 words, don't say "click here"
Key Principles
- Be specific: Always quote the exact text with the error
- Reference rules: Cite the specific style guide rule for each correction
- Maintain voice: Preserve the author's voice while correcting errors
- Prioritize clarity: Focus on changes that improve readability
- Be constructive: Frame feedback to help writers improve
- Flag ambiguous cases: When style guide doesn't address an issue, explain options and recommend the clearest choice
Common Areas to Focus On
Based on Every's style guide, pay special attention to:
- Punctuation (comma usage, semicolons, apostrophes, quotation marks)
- Capitalization (proper nouns, titles, sentence starts)
- Numbers (when to spell out vs. use numerals)
- Passive voice (replace with active whenever possible)
- Overused words (actually, very, just)
- Lists (parallel structure, punctuation, capitalization)
- Hyphenation (compound adjectives, except adverbs)
- Word usage (fewer vs. less, they vs. them)
- Company references (singular "it", teams as plural "they")
- Job title capitalization
How to use every-style-editor on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add every-style-editor
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches every-style-editor from GitHub repository everyinc/compound-engineering-plugin and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate every-style-editor. Access the skill through slash commands (e.g., /every-style-editor) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★32 reviews- ★★★★★Aarav Okafor· Dec 24, 2024
every-style-editor reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Pratham Ware· Dec 12, 2024
every-style-editor reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ren Singh· Nov 15, 2024
I recommend every-style-editor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sakshi Patil· Nov 3, 2024
I recommend every-style-editor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Chaitanya Patil· Oct 22, 2024
Useful defaults in every-style-editor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ren Rahman· Oct 6, 2024
Useful defaults in every-style-editor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Layla Agarwal· Sep 25, 2024
every-style-editor has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Piyush G· Sep 13, 2024
every-style-editor has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Oshnikdeep· Sep 9, 2024
every-style-editor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yuki Khan· Sep 9, 2024
every-style-editor reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 32