Communitygithub.com

LiamVisionary/hivemindos

Audit, write, or redesign product landing pages with a sharp conversion and shareability lens. Use when working on landing pages, launch pages, hero sections, pricing sections, CTAs, testimonials, OG/social preview images, product positioning, paywall strategy, headline memorability, or "make this product/page more viral" requests.

¿Qué es hivemindos?

hivemindos is a Claude Code agent skill that audit, write, or redesign product landing pages with a sharp conversion and shareability lens. Use when working on landing pages, launch pages, hero sections, pricing sections, CTAs, testimonials, OG/social preview images, product positioning, paywall strategy, headline memorability, or "make this product/page more viral" requests.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/LiamVisionary/hivemindos/tree/HEAD/packaged-skills/optional/gtm/hivemindos/viral-product-landing-page

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Viral Product Landing Page

Overview

Use this skill to make a product page easier to understand, remember, buy, and share. Treat the principles as a high-pressure critique lens, not universal law: preserve product reality, legal accuracy, accessibility, and brand trust.

Workflow

  1. Identify the page job in one sentence: who is arriving, what desire or pain brought them here, and what action should happen next.
  2. Inspect the first screen before anything else. If the hero alone cannot explain the product, show the product, create desire, and drive one concrete action, fix the hero first.
  3. Rewrite copy in simple, specific language. Prefer numbers, outcomes, customer wording, and lived specificity over adjectives, abstractions, or generic competitor-safe claims.
  4. Reduce decision load. Use one primary CTA, obvious pricing, a small palette, and a small number of pricing choices.
  5. Add proof before traffic. Use testimonials, comparison, customer language, founder presence, demos, or visible usage evidence.
  6. Design for sharing. Treat the final section and OG image as conversion surfaces: the ending should be memorable, and the share preview should be click-worthy.
  7. Separate decisive fixes from experiments. Some rules are strong defaults; pricing model, free plans, and paywalls depend on market, distribution, product cost, and buyer trust.

Critique Checklist

Hero

  • Show the product before explaining it when a demo, screenshot, interactive sample, or concrete output would communicate faster than prose.
  • Make the headline understandable to a fifth grader and memorable the next day.
  • Sell a human desire: more time, money, health, status, clarity, safety, or less pain.
  • Use emotional specificity when it fits the brand. The page should make people feel something, not just parse features.
  • Make the product explainable in under 10 words.

Copy

  • Replace adjectives with numbers or vivid claims: "save 4 hours every week" beats "fast."
  • Cut weak qualifiers such as "most," "many," and "rarely" unless the evidence requires uncertainty.
  • Steal wording from customers, support threads, reviews, sales calls, and beta feedback.
  • Write lines only this product or founder could write. If a competitor can paste the sentence onto their page, sharpen it.
  • Reveal one idea per screen or section.

Offer And Pricing

  • Make pricing easy to find and impossible to miss.
  • Use three choices at most when tiering helps: good, better, best.
  • Consider one-time pricing when subscriptions add unnecessary resistance.
  • Consider a hard paywall or paid-first validation when the goal is proof of willingness to pay.
  • Be careful with free plans. Free can be a distribution strategy, but it can also increase support cost, infrastructure cost, and roadmap distortion.
  • If the product is more expensive than competitors, justify the premium clearly instead of hiding it.

CTA

  • Use one primary CTA per decision surface.
  • Make the CTA say what happens next: "Analyze My Website" beats "Get Started."
  • Ask for payment before asking for unnecessary data when validation or purchase intent is the central goal.
  • Let people try or see the best part before buying when the product experience itself sells the offer.

Trust And Shareability

  • Add testimonials, user quotes, founder video, proof cards, or visible customer evidence before sending serious traffic.
  • Compare against competitors around the features buyers actually care about.
  • Use a name made of words people can remember and repeat.
  • Ride a real market wave when one exists, but tie it to a concrete product outcome.
  • End with a share-worthy footer or closing idea, since many visitors will not buy but may remember or share.
  • Treat the OG image like a YouTube thumbnail: clear subject, high contrast, obvious promise, and enough intrigue to earn the click.

Output Format

When critiquing, answer with:

  1. The page's one-line product promise.
  2. The top 3 conversion leaks, ordered by severity.
  3. Concrete replacement copy for hero headline, subhead, CTA, pricing label, or footer when relevant.
  4. One OG/social preview recommendation.
  5. Experiments to test, clearly labeled, especially around pricing, free plan removal, subscriptions, or hard paywalls.

When building or editing a page, implement the strongest applicable fixes directly, then verify the first screen, CTA clarity, pricing visibility, mobile layout, and metadata/OG preview if the project exposes them.

Reference

For the full source checklist distilled into categories, read references/viral-product-principles.md when doing a deep audit or generating a before/after teardown.

Individual skills in this repo

This repo contains 2 individual skills — each has its own dedicated page.

Skills relacionados