Make Product Viral
Use this skill to improve a product surface so people can understand it quickly,
trust it before paying, remember it after leaving, and share it without needing
to decode the whole page first.
Attribution
This skill is inspired by Marc Lou's "32 Principles of a Viral Product" post on
X: https://x.com/marclou/status/2065385672991752210
Use the source as a set of strong defaults from startup building experience, not
as universal rules. See references/source-and-caveats.md for attribution,
ethical guardrails, and adaptation notes.
Core Lens
A viral product is not just a product with social sharing. It has a simple
promise, visible product proof, low cognitive load, a clear buying path, and a
memorable reason to talk about it.
Optimize in this order:
- Can people understand it in seconds?
- Can they see or try the product before reading a long explanation?
- Is the desired outcome concrete, emotional, and memorable?
- Is there one obvious next action?
- Is trust visible before the user is asked to pay?
- Is the page easy to share, including its final impression and social preview?
Resource Routing
Load only the files needed for the task:
| Need |
Read |
| Full audit sequence for a product, landing page, pricing page, launch page, free tool, app-store surface, or OG image |
workflows/audit-product-surface.md |
| Attribution, caveats, and ethical guardrails |
references/source-and-caveats.md |
Fast Workflow
- Write the product in one clear sentence before making lower-level changes.
- Check whether the first viewport can sell alone: what it is, who it is for,
the result, why to believe it, and what happens on click.
- Move visible product proof before long explanatory copy.
- Remove mixed-message sections so each screen or section carries one idea.
- Make the primary CTA specific to the next action.
- Check trust, pricing clarity, and paywall fit before recommending launch
traffic.
- Review the social preview and final impression as shareable artifacts.
Output Format
When using this skill, respond with:
- Viral diagnosis: the main reason this is or is not likely to spread.
- Highest-leverage fixes: 3 to 7 changes, ordered by impact.
- Hero rewrite: headline, subhead, CTA, and proof or demo suggestion.
- Shareability pass: OG image, footer or final impression, and one-line
description.
- Pricing or paywall note: only if relevant.
- Validation plan: what to check before launch.
Keep recommendations concrete. Prefer replacement copy, section order, product
proof, pricing structure, and specific UI/content changes over abstract advice.
Source: hashgraph-online/awesome-codex-plugins → plugins/LVTD-LLC/skills/skills/make-product-viral/SKILL.md
1---2name: make-product-viral3description: Make a product, landing page, pricing page, launch page, free tool, or social preview easier to understand, buy, remember, and share using Marc Lou-inspired viral product patterns.4---567# Make Product Viral89Use this skill to improve a product surface so people can understand it quickly,10trust it before paying, remember it after leaving, and share it without needing11to decode the whole page first.1213## Attribution1415This skill is inspired by Marc Lou's "32 Principles of a Viral Product" post on16X: https://x.com/marclou/status/20653856729917522101718Use the source as a set of strong defaults from startup building experience, not19as universal rules. See `references/source-and-caveats.md` for attribution,20ethical guardrails, and adaptation notes.2122## Core Lens2324A viral product is not just a product with social sharing. It has a simple25promise, visible product proof, low cognitive load, a clear buying path, and a26memorable reason to talk about it.2728Optimize in this order:29301. Can people understand it in seconds?312. Can they see or try the product before reading a long explanation?323. Is the desired outcome concrete, emotional, and memorable?334. Is there one obvious next action?345. Is trust visible before the user is asked to pay?356. Is the page easy to share, including its final impression and social preview?3637## Resource Routing3839Load only the files needed for the task:4041| Need | Read |42| --- | --- |43| Full audit sequence for a product, landing page, pricing page, launch page, free tool, app-store surface, or OG image | `workflows/audit-product-surface.md` |44| Attribution, caveats, and ethical guardrails | `references/source-and-caveats.md` |4546## Fast Workflow47481. Write the product in one clear sentence before making lower-level changes.492. Check whether the first viewport can sell alone: what it is, who it is for,50 the result, why to believe it, and what happens on click.513. Move visible product proof before long explanatory copy.524. Remove mixed-message sections so each screen or section carries one idea.535. Make the primary CTA specific to the next action.546. Check trust, pricing clarity, and paywall fit before recommending launch55 traffic.567. Review the social preview and final impression as shareable artifacts.5758## Output Format5960When using this skill, respond with:61621. **Viral diagnosis:** the main reason this is or is not likely to spread.632. **Highest-leverage fixes:** 3 to 7 changes, ordered by impact.643. **Hero rewrite:** headline, subhead, CTA, and proof or demo suggestion.654. **Shareability pass:** OG image, footer or final impression, and one-line66 description.675. **Pricing or paywall note:** only if relevant.686. **Validation plan:** what to check before launch.6970Keep recommendations concrete. Prefer replacement copy, section order, product71proof, pricing structure, and specific UI/content changes over abstract advice.7273---7475**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/make-product-viral/SKILL.md`
thedixitjain