brand-writer

Generates Zed brand-voice-compliant developer copy via structured workflow and rubrics.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/botterYosuke/The-Trader-Was-Replaced --skill brand-writer-botteryosuke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brand-writer
Source: https://github.com/botterYosuke/The-Trader-Was-Replaced/tree/main/.claude/skills/zed/src/docs/.conventions/brand-voice
Command: npx skills add https://github.com/botterYosuke/The-Trader-Was-Replaced --skill brand-writer-botteryosuke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of creating clear, developer-first copy that aligns with Zed's brand voice and principles.

Core Features & Use Cases

  • Brand Voice Guidance: Follows Zed's brand voice guidelines for thoughtful, technically grounded, and confidently expressed copy.
  • Writing Principles: Adheres to Zed's writing principles, ensuring the most important information is upfront, and avoiding hype or emotional manipulation.
  • Structured Workflow: Offers a structured workflow with clear steps for understanding the ask, gathering context, drafting, and validation.

Quick Start

To start a writing session, invoke the skill with '/brand-writer'. For review, use '/brand-writer --review "paste copy"'.

Frequently Asked Questions about brand-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write developer-focused copy that matches a specific brand voice?

To write developer-focused copy, use a structured workflow that applies predefined rubrics, voice examples, and taboo phrases. This ensures your technical communication remains consistent and adheres to specific brand standards.

What are the key writing principles for developer copywriting?

Developer copywriting principles require putting the most important information upfront and avoiding hype or emotional manipulation. Copy should be thoughtful, technically grounded, and confidently expressed to respect the developer audience.

How do I review existing technical communication against brand voice guidelines?

You can review existing technical communication by passing it through a validation step that checks the draft against predefined rubrics and taboo phrases. This structured process identifies deviations from the required brand voice.

Can I use this structured workflow for generating technical communication outside of software documentation?

The structured workflow is optimized for developer-focused copy and technical communication. While the core writing principles apply broadly, using it for non-technical audiences may require adjusting the predefined rubrics and voice examples.

What is the best way to avoid hype when writing developer copy?

The best way to avoid hype in developer copy is to follow a structured writing process that enforces technical grounding and utilizes predefined taboo phrases. This guarantees the final copy remains clear and objectively stated.