agentleFS
divyanshu-iitiandivyanshu-iitian/agent-website-design-skills/landing-page-craft/SKILL.md

landing-page-craft

Skill2 starsChanged 4 months agoMITView on GitHub

Design, implement, or improve a distinctive, conversion-focused landing page or marketing website. Use for homepages, product pages, launch pages, portfolios, pricing pages, waitlists, campaign pages, and other flows that must explain an offer, establish trust, and guide a measurable next action.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    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:

    Write a one-line conversion brief:

    line 13
  2. Distinctive:

    Write concrete copy before tuning layout.

    line 26
  3. Distinctive:

    Place proof and risk-reversal near the decisions they support.

    line 29
  4. Distinctive:

    Verify the complete action path on mobile and desktop, including keyboard use, form validation, destinations, and tracking hooks when …

    line 30
  5. Distinctive:

    Keep one primary action per decision point.

    line 35
  6. Distinctive:

    Use real content and realistic lengths early enough to expose layout problems.

    line 36
  7. Distinctive:

    Avoid section-count theater, repeated feature-card grids, fake testimonials, fake scarcity, and unsupported superlatives.

    line 37
  8. Distinctive:

    Do not hide material price, renewal, privacy, eligibility, or cancellation information.

    line 38
  9. Distinctive:

    Keep important content available without requiring decorative animation.

    line 39
  10. Distinctive:

    Treat performance, accessibility, and responsive behavior as conversion features.

    line 40
  11. Distinctive:

    Implemented page: - when code changes are requested.

    line 50
  12. Distinctive:

    Read references/conversion-flow.md when choosing page structure, proof placement, CTA language, and risk-reversal.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Landing Page Craft

Build a page around a real decision, not a stack of fashionable sections. Make the offer understandable, believable, and actionable before adding polish.

Workflow

  1. Inspect existing brand, product, audience, traffic source, content, analytics requirements, and technical constraints.
  2. Write a one-line conversion brief:
    • audience;
    • situation or intent;
    • offer and concrete outcome;
    • primary action;
    • biggest objection.
  3. Inventory available proof: product UI, examples, customer evidence, metrics, founder expertise, policies, integrations, security, or process. Never fabricate proof.
  4. Choose a page argument. Sequence only the sections needed to move the audience from recognition to confidence to action.
  5. Design the first viewport to answer:
    • What is this?
    • Is it for me?
    • What changes if it works?
    • What should I do next?
  6. Write concrete copy before tuning layout. Make headings informative, CTAs destination-aware, and claims proportional to evidence.
  7. Select a visual direction that belongs to the offer. Use product UI, real work, relevant imagery, data, or interaction as proof - not generic atmosphere.
  8. Implement semantic, responsive, performant UI in the project's existing stack. Include important loading, error, form, and success states.
  9. Place proof and risk-reversal near the decisions they support. Do not dump every trust signal into one logo wall.
  10. Verify the complete action path on mobile and desktop, including keyboard use, form validation, destinations, and tracking hooks when present.

Page Rules

  • The H1 should communicate the offer or outcome; it does not have to repeat the brand name.
  • Keep one primary action per decision point. Secondary actions should reduce uncertainty.
  • Use real content and realistic lengths early enough to expose layout problems.
  • Avoid section-count theater, repeated feature-card grids, fake testimonials, fake scarcity, and unsupported superlatives.
  • Do not hide material price, renewal, privacy, eligibility, or cancellation information.
  • Keep important content available without requiring decorative animation.
  • Treat performance, accessibility, and responsive behavior as conversion features.

Delivery Contract

Provide or implement:

  1. Conversion brief - audience, offer, action, objection.
  2. Page argument - ordered sections and the question each answers.
  3. Evidence map - claim -> nearby proof.
  4. CTA map - label -> destination -> success behavior.
  5. Implemented page - when code changes are requested.
  6. Verification - mobile/desktop screenshots or inspection, keyboard path, form states, and link checks.

Reference

Read references/conversion-flow.md when choosing page structure, proof placement, CTA language, and risk-reversal.

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.