JasonColapietro/suede-creator-skills / skills/suede-copy
suede-copy
VerifiedUse when asked "rewrite this landing page" or to write, sharpen or retune conversion copy, public explainers and agent-facing docs across surfaces. Suede applies voice, frameworks, labeled variants, answer-first SEO/AEO, evidence boundaries and a 70-point ship score. NOT FOR: a standalone anti-slop pass (use suede-deslop), high-stakes research orchestration (use suede-ship-copy), visual design (use suede-design), or scored SEO audits (use suede-seo-audit).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.3 KB |
| SKILL.md | skill md | 16.3 KB |
| agents/openai.yaml | config | 422 B |
| references/edit-passes.md | markdown | 3.1 KB |
| references/email-and-social-formats.md | markdown | 4.9 KB |
| references/frameworks-and-personas.md | markdown | 2.8 KB |
| references/headline-and-cta-formulas.md | markdown | 3.5 KB |
| references/usage-contract.md | markdown | 864 B |
| references/writing-for-agents.md | markdown | 6.4 KB |
references/frameworks-and-personas.md
View on GitHub# Persuasion Frameworks and Buyer Persona Modes
The frameworks to structure an argument around, and how the same claim changes shape for a different buyer.
## Persuasion Frameworks
Match framework to surface and reader temperature:
- Reader arrives cold, no prior awareness: **AIDA** (Awareness → Interest → Desire → Action). Lead with the category problem, build specificity, make the outcome concrete, drive a single action.
- Reader has a named pain and is actively searching: **PAS** (Problem → Agitate → Solution). Name the problem, surface the cost of inaction, position the product as the specific relief.
- Hero section, social post, launch email: **Before-After-Bridge**. Describe life before the product, paint life after, bridge with the product as the mechanism.
- Product page, onboarding, in-app copy: **JTBD**. Write around what the reader is trying to accomplish: the job they hired the product to do, not around features.
- Homepage, About, long-form brand page: **Customer-as-Hero Arc**. The customer has a goal → a specific problem blocks it → your brand shows up as the guide with proof → a short plan → one CTA → what failure costs → what success looks like.
State the chosen framework and reader temperature before drafting. If multiple frameworks could apply, pick one and note why.
## Buyer Persona Modes
State the persona before writing. If multiple personas share a page, write the hero for the decision-maker and include practitioner proof in the secondary section.
**Decision-maker** (exec, founder, buyer)
- Lead: outcome and cost of inaction
- Proof: outcomes, not features ("Cut release prep from 3 days to 40 minutes")
- CTA: low-risk, high-clarity ("See the workflow" not "Transform your process")
- Skip: implementation details, CLI commands
**Practitioner** (developer, designer, operator)
- Lead: how it works, not why it matters
- Proof: commands, file paths, schema examples, error outputs
- CTA: direct action ("Run the linter" / "Fork the skill")
- Skip: ROI language, vague transformation claims
**Skeptic** (comparison shopper, previously burned)
- Lead: the objection, named directly ("Every tool claims to solve this. Here's what's different.")
- Proof: third-party verifiable, not internal ("Open the script. Read the output.")
- CTA: zero-pressure ("Read the code" / "Run it yourself")
- Skip: hype, superlatives, bold claims without evidence
**Creator / end-user** (non-technical)
- Lead: what changes for them, in plain language
- Proof: before/after in human terms ("Your release looks like this. After Suede, it looks like this.")
- CTA: lowest-friction path ("Try it with one release folder")
- Skip: technical vocabulary, command syntax, implementation framing
Default persona when none is named: practitioner for GitHub and docs copy, decision-maker for sales and landing pages, skeptic for comparison copy.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |