# Design Landing Pages With Clear Copy and Visual Rules

Landing pages lose focus when copy, layout, and visual choices lack a shared plan. This skill guides audience intake, page structure, conversion copy, and consistent styling.

## Install

```bash
npx skillstore add elayadesign/landing-page-design
```

## Metadata

- Status: approved
- Slug: elayadesign-landing-page-design
- Skillstore revision: r1
- Version status: missing
- Tree hash: f9c0e2bea326282d1306722894796c5e222cc87e1b13ad0feceab09b724806f0
- Author: elayadesign
- GitHub username: elayadesign
- License: MIT
- Repository: https://github.com/elayadesign/ai-design-skills/tree/4fdcdd52f15eda09da1257c303c860c13e0c879f/skills/landing-page-design
- Ref: 2c485e1cbc11d256cf22e3598034544d1af1b118
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/elayadesign-landing-page-design
- Manifest: https://skillstore.pages.dev/api/skills/elayadesign-landing-page-design/manifest

## Capabilities

- Gather the offer, audience, conversion goal, objections, proof, and brand constraints through a structured intake.
- Recommend one of four page layouts and organize sections around a single primary action.
- Draft hero copy, benefit bullets, three process steps, and six to twelve FAQ answers.
- Specify named typography styles, spacing tokens, corner radii, icon choices, and animation behavior.
- Recommend indexing choices, page titles, meta descriptions, and question and answer content.
- Guide section by section implementation with interaction states, reduced motion support, and a 390px mobile checklist.

## Use Cases

- Plan a product launch page: Define the audience, offer, signup action, and page outline before drafting launch copy.
- Align campaign messaging: Match an advertising promise to hero copy, benefits, supporting proof, and a consistent primary action.
- Implement a consistent page: Translate an approved outline into reusable text styles, spacing tokens, interaction states, and responsive sections.

## Prompt Templates

### Start with a page brief

```
Help plan a landing page for [product] aimed at [audience]. The primary action is [action]. Ask for missing details in one batch.
```

### Draft the page content

```
Draft an outline, hero copy, benefits, three process steps, and six FAQ answers for [offer]. Use only the supplied proof: [verified facts].
```

### Choose layout and search treatment

```
Recommend a layout for [offer] receiving [traffic source] traffic. Explain the choice, indexing recommendation, title, and meta description. Address these objections: [objections].
```

### Build and review sections

```
Implement the approved outline in [stack], section by section. Define reusable visual tokens. Include interaction states and reduced motion behavior. Check the 390px layout.
```

## Limitations

- The skill provides instructions, not bundled scripts, components, or a deployment service.
- It cannot guarantee conversion improvements, search rankings, or accessibility compliance.
- Real prices, statistics, testimonials, and customer logos require user input or verified sources.
- Its prescribed fonts, tokens, icons, and motion patterns may conflict with an existing design system.

## Best Practices

- Provide one audience, one offer, one primary action, and verified proof before drafting.
- Approve the outline and copy before building each section.
- Check keyboard focus, reduced motion behavior, and the 390px layout before release.

## Anti Patterns

- Do not invent testimonials, customer logos, prices, or performance statistics for a real product.
- Do not place competing primary actions above the fold.
- Do not rebuild the entire page for every section change.

## Security Audit

- Audited at: 2026-10-31T14:11:30.354\+00:00
- Summary: All 71 static findings are false positives: Markdown backticks, reference links, and ordinary page design prose. No evidence found of command execution, system reconnaissance, data exfiltration, or prompt injection in the reviewed file. The file provides design guidance and contains no executable scripts.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0