Contenu du pack

Un fichier SKILL.md (le guide pratique) + un modèle de départ. Aperçu :

Confetti Marketing Landing

When to use

• You're launching a product, feature, or event and want the page to feel celebratory and urgent
• You're running a seasonal promotion, sale, or limited offer and need a page that sells the excitement
• Your current landing page converts poorly because it reads like a spec sheet — visitors bounce before the offer lands
• You need a waitlist or signup page for something fun: a party product, a game, a course, a community
• You have a launch deadline in days, not weeks, and need one focused page, not a full site
• Your offer has a deadline or a limited quantity — the page needs to make that felt, not just stated

Workflow

1. Pin down the one offer (input: product + campaign details → output: offer statement)
   Write the offer in one sentence with a verb, a benefit, and a deadline or limit: "Join the waitlist today and get 30% off launch week — 500 spots." If you can't write it in one sentence, the page will try to sell three things and convert on none. Every later section — headline, proof, FAQ — exists to support this single sentence. Cut any section that doesn't.
2. Write the headline stack (input: offer statement → output: headline + subhead + CTA)
   The headline promises the outcome in the visitor's words ("Throw a party they'll actually remember"), the subhead names the product and the mechanism in one line ("Confetti kits with everything in the box — order by Friday for weekend delivery"), and the CTA button states the action and the payoff ("Get my kit — 30% off"). Write three headline options, pick the one a stranger understands in 3 seconds, and put the CTA button directly beneath it. No clever-but-unclear headlines on a landing page — clarity converts, wit doesn't.
3. Design the confetti system (input: headline stack + brand palette → output: confetti rules)
   Define confetti as a conversion tool, not decoration: a burst behind the hero headline, a scatter trail leading the eye toward the CTA, and a celebratory burst on the confirmation state after signup. Set rules — 2–3 confetti colours drawn from the offer's mood, dense in the hero, sparse or absent in pricing and FAQ where numbers must be read cleanly. Confetti near the CTA should frame it, never cover it.
4. Build the persuasion sections (input: offer statement → output: page body)
   In order: Hero (headline stack + one hero visual) → Proof strip (logos, count, or one-line stats) → Benefits (3–4, each one line: feature → outcome) → Social proof (2–4 short quotes or a rating) → Offer details (what's included, price, deadline) → FAQ (the 4–6 objections that actually block signups) → Final CTA (headline repeated, button repeated). Each section answers one visitor question: "What is it? Does it work? What's in it? What if…? What do I do?" If a section doesn't answer a question, cut it.
5. Make the offer mechanics visible (input: offer details → output: urgency + guarantee blocks)
   If there's a deadline, show it — a countdown or a plain date line ("Offer ends Sunday, 11:59pm") near every CTA, not buried in the FAQ. If there's a guarantee or a risk-reverser (free returns, money-back, no card required for the waitlist), state it in one line directly under the primary button. Urgency without a real deadline is a lie that costs trust; if the offer genuinely has no deadline, say what's limited instead (spots, stock, early pricing).
6. Wire the conversion path (input: page body → output: working form + confirmation)
   The form asks for the minimum: one field for a waitlist (email), two at most for an order (email + one more). The submit button repeats the payoff ("Claim 30% off"), and the confirmation state celebrates — confetti burst, clear "you're in" message, and the next step ("Check your inbox for the code"). Test the full path on a phone: form, submit, confirmation, and the email that arrives. A landing page that drops the confirmation email has converted a visitor into a frustrated one.
7. Check the page like a sceptic (input: working page → output: verified page)
   Read the page as a visitor who doesn't trust you: is the price visible before the CTA? Is the deadline real and dated? Does every claim have proof nearby? Is the page fast on mobile (hero image compressed, confetti lightweight, no autoplay video)? Then do the 5-second test: show the page for 5 seconds and ask what the offer is. If the answer is wrong, the hero is wrong — fix the headline stack, not the decorations.

Aperçu du modèle

Confetti Marketing Landing — Starter Template

One page, one offer, one CTA repeated. Fill in every {placeholder}.

Offer

• Offer statement (verb + benefit + deadline/limit): {offer_statement}
• Price: {price} | Deadline: {deadline_date_time} | Limit: {limit_if_any}
• Guarantee / risk-reverser: {guarantee, e.g. "30-day money-back, no questions"}

Confetti rules

• Confetti colours: {colour_1}, {colour_2}, {colour_3}
• Hero: {burst_description} | CTA trail: {trail_description}
• Confirmation: {confirmation_burst}
• Pricing / FAQ: {sparse_or_none — keep numbers readable}

Hero

• Headline (option A): {headline_a}
• Headline (option B): {headline_b}

Le pack de compétence lui-même (SKILL.md + modèle) est rédigé en anglais.

Acheter le pack complet — $4.99 Pro — les 511 compétences