1. Most important information first — Start with what the developer needs to know right now: what changed, what's possible, or how it works. Follow with brand storytelling or philosophical context if space allows.
2. Thoughtful, not performative — Write like you're explaining something you care about, not pitching it.
3. Explanatory precision — Share technical detail when it matters. Terms like "GPU acceleration" or "keystroke granularity" show expertise and respect.
4. Philosophy first, product second — Start from an idea about how developers work or what they deserve, then describe how Zed supports that.
5. Natural rhythm — Vary sentence length. Let ideas breathe. Avoid marketing slogans and forced symmetry.
6. No emotional manipulation — Never use hype, exclamation points, or "we're excited." Don't tell the reader how to feel.

1. Lead with the most essential fact or change a developer needs to know.
2. Explain how Zed addresses it.
3. Add brand philosophy or context to deepen understanding.
4. Let the reader infer the benefit — never oversell.

• AI/marketing tropes (em dashes, mirrored constructions, "it's not X, it's Y")
• Buzzwords ("revolutionary," "cutting-edge," "game-changing")
• Corporate tone or startup voice
• Fragmented copy and slogans
• Exclamation points
• "We're excited to announce..."

• Would a senior developer respect this?
• Does it sound like something from zed.dev?
• Does it read clearly and naturally aloud?
• Does it explain more than it sells?

• What is this for? (homepage, release notes, docs, social, product page)
• Who's the audience? (prospective users, existing users, developers in general)
• What's the key message or feature to communicate?
• Any specific constraints? (character limits, format requirements)

1. Load reference files (auto-loaded from skill folder):

   • rubric.md

     — 8 scoring criteria for validation

   • taboo-phrases.md

     — patterns to eliminate

   • voice-examples.md

     — transformation patterns and fact preservation rules
2. Search for relevant context (if needed):
   • Existing copy on zed.dev for tone reference
   • Technical details about the feature from docs or code
   • Related announcements or prior messaging

[FACT]

• Technical specifications
• Proper nouns and product names
• Version numbers and dates
• Keyboard shortcuts and URLs
• Attribution and quotes

Zed is [FACT: written in Rust] with [FACT: GPU-accelerated rendering at 120fps]. Built by [FACT: the team behind Atom and Tree-sitter].

1. Identify the specific problem
2. Rewrite the flagged section
3. Verify

   [FACT]

   markers survived
4. Re-score the rewritten section

• [FACT: Rust] ✓
• [FACT: GPU-accelerated] ✓
• [FACT: 120fps] ✓

**Output formats by context:**

| Context       | Format                                               |
| ------------- | ---------------------------------------------------- |
| Homepage      | H1 + H2 + supporting paragraph                       |
| Product page  | Section headers with explanatory copy                |
| Release notes | What changed, how it works, why it matters           |
| Docs intro    | Clear explanation of what this is and when to use it |
| Social        | Concise, no hashtags, link to learn more             |

---

--review

1. Load reference files (rubric, taboo phrases, voice examples)
2. Score the provided copy against all 8 rubric criteria
3. Scan for taboo phrases — list each with line number:

   Line 2: "revolutionary" (hype word)
   Line 5: "—" used 3 times (em dash overuse)
   Line 7: "We're excited" (empty enthusiasm)

4. Present diagnosis:

   ## Review: [Copy Title]
   
   | Criterion           | Score | Issues |
   |---------------------|-------|--------|
   | Technical Grounding |   3   | Vague claims about "performance" |
   | Natural Syntax      |   2   | Triple em dash chain in P2 |
   | ...                 |       |        |
   
   ### Taboo Phrases Found
   - Line 2: "revolutionary"
   - Line 5: "seamless experience"
   
   ### Verdict
   ❌ Does not pass (3 criteria below threshold)

5. Offer rewrite if any criterion scores <4:
   • Apply transformation patterns from voice-examples.md
   • Preserve all facts from original
   • Present rewritten version with new scores

Zed is written in Rust with GPU acceleration for every frame. When you type or move the cursor, pixels respond instantly. That responsiveness keeps you in flow.

We're excited to announce our revolutionary new editor that will change the way you code forever! Say goodbye to slow, clunky IDEs — Zed is here to transform your workflow.

Zed is a new kind of editor, built from scratch for speed. It's written in Rust with a GPU-accelerated UI, so every keystroke feels immediate. We designed it for developers who notice when their tools get in the way.