agentleFS
Sign inStart free
jhonatan-oliveiradevjhonatan-oliveiradev/agent-skills/skills/building-conversion-product-pages/SKILL.md

building-conversion-product-pages

Skill1 starsChanged 3 months agoMITView on GitHub

Use when designing or improving a landing page, product page, digital-product storefront, pricing page, or marketing flow where visitor comprehension and conversion are primary goals.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep CTA language concrete and consistent.

    line 17
  2. Distinctive:

    Verify mobile conversion flow, sticky elements, checkout handoff, keyboard behavior, and analytics hooks if present.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Building Conversion Product Pages

Principle

Conversion follows clarity, relevance, trust, and reduced decision friction. Visual polish supports those goals; it does not replace them.

Sequence

  1. Define the visitor, their problem, desired outcome, and the single primary action.
  2. Make the hero answer: what is this, who is it for, why should I care, what do I do next?
  3. Show the product early. Prefer screenshots, previews, demos, sample outputs, or concrete artifacts over abstract decoration.
  4. Structure proof from strongest to weakest: demonstrable capabilities, examples, transparent process, credible social proof only when real.
  5. Handle objections near the decision point: requirements, delivery, compatibility, license, updates, refund/support terms where applicable.
  6. Keep CTA language concrete and consistent.
  7. For pricing, reduce comparison complexity and explain meaningful differences rather than filling a feature matrix.
  8. Verify mobile conversion flow, sticky elements, checkout handoff, keyboard behavior, and analytics hooks if present.

Avoid

  • fake urgency;
  • fake testimonials or customer logos;
  • generic AI copy such as exaggerated transformation claims;
  • repeated CTAs with different labels for the same action;
  • long decorative sections before the product is understood;
  • visual novelty that obscures price or purchase path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free