What’s inside

One SKILL.md (the playbook) + one starter template. A preview:

Waveform Audio Landing

When to use

• You're launching headphones, a synth plugin, a podcast app, a sample library, or any product people judge by hearing it, and your current page reads like a parts list
• Visitors bounce before pressing play because the listen button is buried below three paragraphs of specs
• Your product has one sound that sells it — a signature tone, a before/after cleanup, a spatial mix — and the page doesn't put that sound first
• You need a page that works for two audiences at once: casual listeners who decide in seconds and audio-savvy buyers who want the details
• You're running ads or a launch post and need a single page that turns a click into a listen, and a listen into a signup or purchase

Workflow

1. Define the one sound (input: product + audience → output: listening promise)
   Pick the single listening moment that sells the product. Write one sentence: "Press play and hear X change in Y seconds." If you can't name that moment, you don't have a landing page yet — you have a brochure. Everything on the page exists to get the visitor to that one listen.
2. Build the listen-first hero (input: listening promise → output: hero copy + CTA layout)
   The headline names the listening payoff, not the technology. The primary CTA is Listen or Play — never "Learn more." A waveform motif frames the hero: a decorative waveform strip, a player with a visible waveform, or both. Show the clip's duration and what the listener will hear ("12 sec: same track, flat vs. tuned"). Never autoplay with sound.
3. Turn features into listening tests (input: feature list → output: feature sections with audio demos)
   Each feature gets a paired audio demo: before/after, A/B, or on/off. Write 2–3 sentences per feature in listening terms — what changes in what the ear hears — not in engineering terms. If a feature can't be heard, either say what it changes in listening terms or cut it from the page. A feature without a demo is a claim without evidence.
4. Add proof listeners can check (input: testimonials + specs → output: proof section)
   Quotes tied to specific listening moments ("the vocal stepped forward in the first chorus") beat generic praise ("amazing sound!"). Specs go in a compact table for the savvy buyer — frequency response, latency, formats — stated plainly, with no superlatives you can't back up. No "best sound ever," no unverifiable claims.

Template preview

Waveform Audio Landing — Page Brief Template

Fill this in before any copy gets written. One product = one brief.

Product: {product name}

What it is (one sentence): {…} Who it's for: {…} The one sound that sells it: {…}

Listening promise

> "Press play and hear {what changes} in {how many} seconds."

Hero clip: {file / link} | Duration: {… sec} | What the listener hears: {…}

Hero

• Headline (≤12 words): {…}
• Subhead (≤25 words): {…}
• Primary CTA: ▶ Listen — {… sec}
• Secondary CTA (at most one): {…}
• Waveform motif: {waveform strip / player waveform / both} — {placement}

Feature sections (3–5, each with a paired demo)

Buy the full skill pack — $4.99 Pro — all 471 skills