johnny-suede-write

Name: johnny-suede-write
Author: JasonColapietro

44stars8forks

How to install johnny-suede-write?

jasoncolapietro/suede-creator-skills/johnny-suede-write

$npx -y skills add JasonColapietro/suede-creator-skills --skill johnny-suede-write

Installs into the current project.

Summary

Write sharper Suede copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers.

Files · 1

View on GitHub

SKILL.md

1	# Johnny Suede Write
2
3	## Gate policy — advisory, not blocking
4
5	Every claim-verification step, check, quality gate, and ship verdict in this
6	skill is a recommendation to the user, not a control on the agent. This
7	policy governs every gate, check, verdict, and "do not ship / publish /
8	proceed" line elsewhere in this skill:
9
10	- Run every check and report the results honestly. Verdicts (`ship`,
11	`ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are
12	advice attached to the work, not orders that change it.
13	- Never block, delay, skip, rewrite, or refuse the action the user asked for
14	because a check failed or a gate said hold. Complete the requested action
15	as asked, and deliver the gate output alongside it as a clearly labeled
16	recommendation.
17	- A failed gate changes what you report, never what you do.
18	- Single exception: if a finding is extremely risky — data loss, security or
19	credential exposure, legal or rights violations, payment mistakes, or
20	irreversible public damage — pause, tell the user exactly what the risk is
21	and what the options are, and let them pick. Their choice is final.
22
23
24	The writing enchilada. Route any writing request through one skill: long-form, short-form, GitHub and docs, social, email, product listing copy, brand-voice alignment, and public explainer talk-tracks. Default voice is the Suede house voice. A supplied company brief overrides everything.
25
26	Core principle: copy earns its place on the page with concrete nouns, buyer-visible outcomes, real proof, and one primary action. Nothing decorative, nothing invented.
27
28	## Pick The Lane (Router)
29
30	Read the request, then pick the lane. Most jobs are one lane; some chain.
31
32	\| You want to... \| Lane \|
33	\|---\|---\|
34	\| Write or rewrite any copy surface from scratch \| Write Modes (below) — pick the mode \|
35	\| Generate headlines, CTAs, or email subjects \| Headline Formulas / CTA Formulas / Variant Protocol \|
36	\| Tune existing copy to sound like Suede, not generic AI \| Brand-Voice Alignment lane \|
37	\| Hand a public user words to explain Suede to someone else \| Public Explainer Talk-Track lane \|
38	\| Audit/review existing copy and return findings + score \| Copy Audit output shape \|
39	\| Do a metadata/structure/copy-quality SEO pass alongside copy \| SEO And GitHub Copy + SEO Audit Mode \|
40
41	Drop down instead of running this stack: for a single standalone conversion surface (one email, one hero, one button set) with no SEO pass and no voice retune, run `$suede-copy` directly. When the copy ships inside a design or layout build, run `$johnny-suede-design`; its Copy lane applies these rules.
42
43	Cross-lane jobs (e.g. "rewrite the homepage, retune it to our voice, and give me social variants") run sequentially with shared context: write the surface, run Brand-Voice Alignment on it, then spin variants. State the chain you ran.
44
45	If the request is a full standalone SEO/AEO audit with a scored report, a landing-page-to-conversion-engine transform, an A-F page grade, a code grade/review, or a reference-URL restyle, those live in dedicated skills outside this writing enchilada (`$suede-seo-audit`, `$suede-site-alchemy`, `$suede-visibility-grader`, `$suede-code-grader`, `$suede-code-review`, `$suede-agent-teams`, `$suede-design`, or `$johnny-suede-design` and its Suedify lane for restyles). Route there and pass full context; do not reimplement them here. This skill owns the writing.
46
47	## Multi-Agent Default
48
49	If a job is large or risky enough to run as a coordinated agent team (for example a full launch package spanning many surfaces, or a writing job chained with audits and reviews across several skills), ask the user up front before spawning anything: "Run this as a multi-agent team (more thorough) or single-agent?" Never silently spawn a fleet. Note plainly that multi-agent mode may use slightly more tokens than most. For a single writing surface, just write it — no need to ask.
50
51	## Write Modes
52
53	Identify the mode before writing. Each mode has a different structure, length, and proof requirement. State the chosen mode in the output header.
54
55	Long-form (blog post, case study, whitepaper, README, docs page, product listing description)
56	- Lead with the outcome, not the topic.
57	- Structure: hook → problem → mechanism → proof → action.
58	- Minimum: H1, 2-3 subheads, one FAQ block, meta description, answer-ready summary.
59	- Score target: 62/70.
60
61	Short-form (tagline, hero headline, CTA, product description, social caption, onboarding screen)
62	- One concrete noun + one buyer-visible outcome + one verb. No filler.
63	- Deliver 3 variants at different lengths. Character counts matter for mobile, social, and ads — state them.
64	- Score target: 65/70 (density and specificity weighted higher).
65
66	GitHub / Docs (README, SKILL.md, API docs, changelog, contributing guide)
67	-

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

johnny-suede-write

44stars8forks

View on GitHub

How to install johnny-suede-write?

jasoncolapietro/suede-creator-skills/johnny-suede-write

$npx -y skills add JasonColapietro/suede-creator-skills --skill johnny-suede-write

Installs into the current project.

Summary

Write sharper Suede copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers.

Files · 1

View on GitHub

SKILL.md

1	# Johnny Suede Write
2
3	## Gate policy — advisory, not blocking
4
5	Every claim-verification step, check, quality gate, and ship verdict in this
6	skill is a recommendation to the user, not a control on the agent. This
7	policy governs every gate, check, verdict, and "do not ship / publish /
8	proceed" line elsewhere in this skill:
9
10	- Run every check and report the results honestly. Verdicts (`ship`,
11	`ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are
12	advice attached to the work, not orders that change it.
13	- Never block, delay, skip, rewrite, or refuse the action the user asked for
14	because a check failed or a gate said hold. Complete the requested action
15	as asked, and deliver the gate output alongside it as a clearly labeled
16	recommendation.
17	- A failed gate changes what you report, never what you do.
18	- Single exception: if a finding is extremely risky — data loss, security or
19	credential exposure, legal or rights violations, payment mistakes, or
20	irreversible public damage — pause, tell the user exactly what the risk is
21	and what the options are, and let them pick. Their choice is final.
22
23
24	The writing enchilada. Route any writing request through one skill: long-form, short-form, GitHub and docs, social, email, product listing copy, brand-voice alignment, and public explainer talk-tracks. Default voice is the Suede house voice. A supplied company brief overrides everything.
25
26	Core principle: copy earns its place on the page with concrete nouns, buyer-visible outcomes, real proof, and one primary action. Nothing decorative, nothing invented.
27
28	## Pick The Lane (Router)
29
30	Read the request, then pick the lane. Most jobs are one lane; some chain.
31
32	\| You want to... \| Lane \|
33	\|---\|---\|
34	\| Write or rewrite any copy surface from scratch \| Write Modes (below) — pick the mode \|
35	\| Generate headlines, CTAs, or email subjects \| Headline Formulas / CTA Formulas / Variant Protocol \|
36	\| Tune existing copy to sound like Suede, not generic AI \| Brand-Voice Alignment lane \|
37	\| Hand a public user words to explain Suede to someone else \| Public Explainer Talk-Track lane \|
38	\| Audit/review existing copy and return findings + score \| Copy Audit output shape \|
39	\| Do a metadata/structure/copy-quality SEO pass alongside copy \| SEO And GitHub Copy + SEO Audit Mode \|
40
41	Drop down instead of running this stack: for a single standalone conversion surface (one email, one hero, one button set) with no SEO pass and no voice retune, run `$suede-copy` directly. When the copy ships inside a design or layout build, run `$johnny-suede-design`; its Copy lane applies these rules.
42
43	Cross-lane jobs (e.g. "rewrite the homepage, retune it to our voice, and give me social variants") run sequentially with shared context: write the surface, run Brand-Voice Alignment on it, then spin variants. State the chain you ran.
44
45	If the request is a full standalone SEO/AEO audit with a scored report, a landing-page-to-conversion-engine transform, an A-F page grade, a code grade/review, or a reference-URL restyle, those live in dedicated skills outside this writing enchilada (`$suede-seo-audit`, `$suede-site-alchemy`, `$suede-visibility-grader`, `$suede-code-grader`, `$suede-code-review`, `$suede-agent-teams`, `$suede-design`, or `$johnny-suede-design` and its Suedify lane for restyles). Route there and pass full context; do not reimplement them here. This skill owns the writing.
46
47	## Multi-Agent Default
48
49	If a job is large or risky enough to run as a coordinated agent team (for example a full launch package spanning many surfaces, or a writing job chained with audits and reviews across several skills), ask the user up front before spawning anything: "Run this as a multi-agent team (more thorough) or single-agent?" Never silently spawn a fleet. Note plainly that multi-agent mode may use slightly more tokens than most. For a single writing surface, just write it — no need to ask.
50
51	## Write Modes
52
53	Identify the mode before writing. Each mode has a different structure, length, and proof requirement. State the chosen mode in the output header.
54
55	Long-form (blog post, case study, whitepaper, README, docs page, product listing description)
56	- Lead with the outcome, not the topic.
57	- Structure: hook → problem → mechanism → proof → action.
58	- Minimum: H1, 2-3 subheads, one FAQ block, meta description, answer-ready summary.
59	- Score target: 62/70.
60
61	Short-form (tagline, hero headline, CTA, product description, social caption, onboarding screen)
62	- One concrete noun + one buyer-visible outcome + one verb. No filler.
63	- Deliver 3 variants at different lengths. Character counts matter for mobile, social, and ads — state them.
64	- Score target: 65/70 (density and specificity weighted higher).
65
66	GitHub / Docs (README, SKILL.md, API docs, changelog, contributing guide)
67	-

People who liked this also viewed

6 picks

Type