Convert Close
Build the Cascade Close: Stack → Vision → Math → Safety Net → Door, with P.S.
Install
npx skills add FerroxLabs/wayland --skill convert-close -g -a claude-code -y- Repository
- FerroxLabs/wayland616
- Category
- Design
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Build the Cascade Close: Stack → Vision → Math → Safety Net → Door, with P.S. and P.P.S. that close again from new angles. Catches every type of buyer (vision-driven, logic-driven, risk-averse, action-ready) by closing from multiple sides. Use when writing the closing block of a sales page, VSL, long-form email, OTO page, or any conversion point where the reader is being asked to act. Not for opening hooks (use convert-open) and not for offer design itself (use funnels-offer for value structuring).
Convert Close - The Cascade Close
"The close isn't a single moment. It's a cascade - multiple closes flowing one after another, each designed to catch a different type of buyer. You're not closing once and hoping. You're closing from every possible angle until there's nothing left to object to." - The Donahoe Method, Framework 5
This skill writes the full Cascade Close: five core layers (Stack → Vision → Math → Safety Net → Door) plus P.S. and P.P.S. that close again from fresh angles.
By the time the reader reaches the bottom of the page, every type of buyer - vision-driven, logic-driven, risk-averse, ready-to-act - has been spoken to in the language they need.
When to Use
Trigger phrases: "write me a close", "donahoe close", "cascade close", "stack vision math safety net door", "close my sales page", "write the CTA section", "guarantee copy", "P.S. close", /convert close <product>.
Use for any conversion point: sales pages, VSLs, OTO pages, long-form launch emails, webinar pitch segments, upsell pages, checkout pages.
Do NOT use for:
- Writing the opening hook (use
convert-open) - Designing the offer's value structure (use
funnels-offer- bonuses, tiers, price-points) - Writing a single button label (this is the full close architecture; the button is one element of the Door)
- Auditing existing closes (use
convert-audit)
