/suede-copy

name: suede-copy
description: "Suede AI writing skill for every copy surface: conversion copy for landing sections, heroes, headlines, CTAs, and microcopy; email and social posts; product listings, README and docs pages; public explainers; brand-voice retunes; and agent-facing docs such as SKILL.md, CLAUDE.md, and AGENTS.md. Includes an answer-first SEO and AEO pass (direct answer up top, question headings, quotable facts, FAQ, metadata), persona and framework selection, labeled variants, evidence boundaries, and a 70-point ship score. Use when asked to write, rewrite, sharpen, or retune copy on one surface or several, explain a product publicly, or tighten a doc an agent reads. NOT FOR: stripping AI patterns from text you are not otherwise rewriting (use suede-deslop); one high-stakes public piece that needs research and an adversarial fact audit before publishing (use suede-ship-copy); layout, tokens, or visual design (use suede-design); a scored standalone SEO audit (use suede-seo-audit)."

Suede Copy

Write copy that earns its place with concrete nouns, outcomes a buyer can see, real proof, and one primary action. Default voice is Suede AI. A supplied company brief overrides every default here.

Gate policy: advisory, not blocking

Every score and ship verdict in this skill is a recommendation to the user, not a control on the agent. Deliver the copy that was asked for and attach the verdict as advice. A failed gate changes what you report, never what you do. Single exception: an extreme-risk finding (legal or rights violation, payment mistake, irreversible public damage). Pause, state the risk and options, and let the user choose. Their choice is final.

Pick the job

| The request | Job | Where the method lives | |---|---|---| | Write or rewrite a page, section, button set, email, post, or listing | **Write** | Write Modes, below | | Improve copy that already exists | **Edit** | `references/edit-passes.md`, then Anti-Slop | | Make existing copy sound like the house voice | **Voice retune** | Brand-Voice Retune, below | | Give a user words to explain the product to someone else | **Public explainer** | Public Explainer, below | | Write or tighten a doc a model reads | **Agent doc** | `references/writing-for-agents.md` | | Review copy and return findings plus a score | **Audit** | Output: Copy audit |

Cross-job requests run in sequence on shared context (write the page, retune it, then spin variants). State the chain you ran.

Large multi-surface jobs (a full launch package across a dozen surfaces) can run as a coordinated team. Ask first: "Run this as a multi-agent team (more thorough, more tokens) or single-agent?" Never spawn a fleet silently. For one surface, just write it.

Before writing

Read what exists before asking: `PRODUCT.md`, `README.md`, `AGENTS.md`, `DESIGN.md`, brand notes, task docs, and the live page if there is one. Then ask only for what blocks accurate copy: surface type, primary reader, the one action the reader should take, the offer, proof that is safe to claim, claims or numbers that are not approved, and where the copy will be published.

Company brief

Company:            Product or offer:       Audience:
Category:           Voice:                  Terms to use / avoid:
Proof:              Allowed claims:         Forbidden claims:
Primary CTA:        Reference URLs:         Brand rules:

With a brief active, replace Suede positioning, vocabulary, proof, and evidence boundaries with the company's. Keep the workflow. Rename `Cue Suede` to `Cue <Company>`.

Core rules

**Name the outcome, not the feature.** Weak: "Suede supports multiple metadata formats." Strong: "Export ISRC, ISWC, and split data in one command."

**Buttons say what happens on click.** Weak: "Learn more" → Strong: "Read how rights routing works" Weak: "Get started" → Strong: "Register your first release" Test: describe the result of the click in three words. If you cannot, rewrite.

**Replace vague claims with artifacts.** Weak: "Suede makes rights management easy." Strong: "Paste your folder path. Suede returns your ISRC, split sheet, and licensing flags."

**No invented proof.** No stats, testimonials, partner names, pricing, rankings, or legal clearance that was not supplied or verified. Write around the gap or leave `[NEEDS PROOF: what]` for the human.

**Competitor-swap test.** Put a competitor's name in place of yours. If the line still reads true, it is not specific enough.

**Suede AI house style.** No em dashes, no "moreover", none of the house-banned words (delve, game-changer, unlock, elevate, seamless, landscape, tapestry), no promotional exclamation points, no default rule-of-three rhythm. The full list and replacements live in suede-deslop.

Write modes

State the mode, persona, and framework in the output header.

• **Long-form** (blog post, case study, docs page, listing description): lead

with the outcome. Hook, problem, mechanism, proof, action. Needs an H1, two or three question-shaped H2s, an FAQ block, a meta description, and a direct answer in the first 60 words. Target 62/70.

• **Short-form** (tagline, hero, CTA, caption, onboarding screen): one concrete

noun, one visible outcome, one verb. Deliver three variants at different lengths with character counts. Target 65/70.

• **GitHub and docs** (README, SKILL.md for humans, changelog, API docs): first

sentence says what it does. One-line description, install, quickstart, reference. Proof is working commands and code. No marketing language. Target 60/70.

• **Agent-facing docs** (SKILL.md, CLAUDE.md, AGENTS.md, a referenced file):

the reader is a model, so the target is the same route through the doc on every run. Write the trigger line before the body. End every step on a checkable test. Cut sentences the model already obeys. Full method in `references/writing-for-agents.md`. Target 60/70.

• **Social** (LinkedIn, X, Instagram, launch post): open with the mo