Shadcn + Vite landing pages that convert (with Iconify)
Quick start
- Identify the single primary conversion action (the one CTA that matters).
- Draft the page using the anatomy below.
- Nail above-the-fold first (title, subheadline, visual, proof, CTA).
- Use below-the-fold to remove doubt (features, proof, FAQ, repeat CTA).
- Implement in shadcn + Tailwind with a distinctive, intentional aesthetic.
If the user provides an existing page, run the same checklist as an audit and propose specific fixes and A/B tests.
Default stack and rules
Default stack:
- React + Vite + TypeScript
- Tailwind CSS (prefer v4)
- shadcn/ui components (added via CLI, then customized)
- Iconify icons (no lucide-react)
Rules:
- One primary CTA, one secondary CTA max above the fold.
- One icon family (or at most two) per page.
- Use shadcn components for accessibility and consistency, but do not let them dictate a generic layout.
For project setup commands (Vite + Tailwind + shadcn), see references/shadcn-vite-setup.md.
Core landing page anatomy
Use this default order unless the user has a strong reason to deviate:
- Navigation (minimal, de-emphasize links that compete with the primary CTA)
- Hero (value + approach + visual)
- Social proof (logos, testimonials, numbers)
- Primary CTA block (repeat CTA if hero is dense)
- Features (value proof, outcomes, differentiators)
- CTA repeated 1 to 2 times (after key persuasion moments)
- Footer (secondary links, legal, contact)
See references/landing-page-anatomy.md for the full checklists and annotated examples.
Above-the-fold checklist
Treat 'above the fold' as the content visible before scrolling on common viewports.
- Define the value you offer (title)
- Detail your approach (subheadline)
- Help the user envision it (visual)
- Establish credibility (social proof)
- Simplify the next step (call to action)
Implementation rules:
- Make the primary CTA unmissable.
- Make the visual concrete (product UI, before/after, outcome preview), not decorative.
- Reduce friction with microcopy (no credit card, 60 seconds, cancel anytime).
Below-the-fold persuasion sequence
- Show clear value (features)
- Motivate to action (social proof)
- Clarify questions (FAQ)
- Repeat your call to action (CTA)
Add sections only if they remove doubt (pricing, security, comparisons, case studies, integrations).
Output patterns to produce
Choose the lightest deliverable that satisfies the user's request.
A) New landing page
Provide:
- Page goal, audience, offer, and primary CTA
- Section-by-section outline mapped to the anatomy
- Hero copy options (3 variations) and CTA microcopy
- Proof plan (what to show and where)
- Implementation: production-grade React code (shadcn + Tailwind + Iconify)
B) Landing page audit
Provide:
- A short diagnosis: what is the page asking the user to do and is it obvious
- Issues and fixes grouped by: Above-the-fold, Below-the-fold, CTA, Proof, Copy, Design/UX, Performance
- 5 to 10 prioritized recommendations (impact vs effort)
- 3 A/B test ideas with clear hypotheses
Shadcn component mapping
Prefer these building blocks:
- Navigation:
Button, Sheet (mobile menu), Separator
- Hero:
Button, Badge, Card (for a framed visual), Input (only if email capture is the CTA)
- Social proof:
Card, Avatar (testimonials), Badge (press or awards)
- Features:
Card, Tabs (only if comparison is critical)
- FAQ:
Accordion
- Final CTA:
Card, Button
Add only the components you actually use.
Icons (Iconify only)
Default icon source: https://icon-sets.iconify.design/
Selection rules:
- Pick one icon set prefix and stay consistent (example:
lucide:* for a clean outline style).
- Use icons to clarify hierarchy, not to decorate.
- Accessibility: decorative icons should be
aria-hidden="true"; meaningful icons should have text nearby.
React usage:
npm i @iconify/react
import { Icon } from '@iconify/react'
export function IconBullet() {
return (
<span className="inline-flex items-center gap-2">
<Icon icon="lucide:check" aria-hidden="true" className="size-4" />
<span>Cancel anytime</span>
</span>
)
}
Notes:
@iconify/react loads icon data on demand by default. Use an offline approach only if the user requires zero network dependence.
- Do not add
lucide-react unless the user explicitly requests it.
Optional: create an AppIcon wrapper for consistent sizing and accessibility. See references/iconify.md.
Design execution (distinctive, non-generic)
Before writing code, decide:
- Purpose: what problem does this page solve and for whom
- Tone: commit to a bold direction (editorial, brutalist, luxury minimal, retro utilitarian, playful, etc.)
- Constraints: performance, accessibility, brand rules
- Differentiation: one memorable detail (layout twist, signature motion moment, unique motif)
Then execute with craft.
Typography
- Choose characterful fonts. Avoid generic defaults.
- Pair one display face (headlines) with a readable body face.
Color and theme
- Use a cohesive palette with 1 to 2 dominant colors and sharp accents.
- Prefer CSS variables (shadcn theme tokens) so the design stays consistent.
Motion
- Use motion as guidance, not decoration: staged reveals, CTA emphasis, proof highlights.
- Prefer a few high-impact moments over many micro animations.
Spatial composition
- Use deliberate hierarchy and whitespace.
- Break the grid only when it improves clarity.
For quick presets, see references/aesthetic-directions.md.
Implementation requirements
- Use semantic HTML and accessible components (labels, focus states, reduced motion support).
- Mobile-first responsive layout.
- Optimize perceived performance: avoid heavy hero media, lazy-load below-the-fold images.
- Keep the primary CTA consistent (label, destination, and promise).
Included starter asset
If the user asks for a starter page scaffold, use:
assets/vite-shadcn-iconify-landing/src/pages/LandingPage.tsx
This is a sectioned template that matches the anatomy and uses shadcn + Iconify.
Reference files
references/shadcn-vite-setup.md: install and configure shadcn/ui for Vite (Tailwind, aliases, CLI)
references/iconify.md: Iconify rules + an AppIcon wrapper component
references/section-templates.md: copy-paste section templates (Navbar, Hero, Proof, Features, FAQ, CTA, Footer)
references/landing-page-anatomy.md: anatomy, above/below-the-fold checklists, annotated examples
references/copy-templates.md: hero formulas, CTA microcopy, FAQ templates
references/aesthetic-directions.md: bold aesthetic presets to pick from quickly
1---
2name: redesign-my-landingpage
3description: Build, critique, and iterate high-converting marketing or product landing pages using React + Vite + TypeScript + Tailwind and shadcn/ui components, with all icons sourced from Iconify. Use when the user asks for a landing page, sales page, signup page, CRO improvements, above-the-fold vs below-the-fold structure, hero + CTA copy, section order, or wants production-ready shadcn + Vite code.
4metadata:
5 source: https://skillmd.com/skills/gabrielmoreira/redesign-my-landingpage
6---
7
8# Shadcn + Vite landing pages that convert (with Iconify)
9
10## Quick start
11
121. Identify the single primary conversion action (the one CTA that matters).
132. Draft the page using the anatomy below.
143. Nail above-the-fold first (title, subheadline, visual, proof, CTA).
154. Use below-the-fold to remove doubt (features, proof, FAQ, repeat CTA).
165. Implement in shadcn + Tailwind with a distinctive, intentional aesthetic.
17
18If the user provides an existing page, run the same checklist as an audit and propose specific fixes and A/B tests.
19
20## Default stack and rules
21
22Default stack:
23- React + Vite + TypeScript
24- Tailwind CSS (prefer v4)
25- shadcn/ui components (added via CLI, then customized)
26- Iconify icons (no lucide-react)
27
28Rules:
29- One primary CTA, one secondary CTA max above the fold.
30- One icon family (or at most two) per page.
31- Use shadcn components for accessibility and consistency, but do not let them dictate a generic layout.
32
33For project setup commands (Vite + Tailwind + shadcn), see `references/shadcn-vite-setup.md`.
34
35## Core landing page anatomy
36
37Use this default order unless the user has a strong reason to deviate:
38
391. Navigation (minimal, de-emphasize links that compete with the primary CTA)
402. Hero (value + approach + visual)
413. Social proof (logos, testimonials, numbers)
424. Primary CTA block (repeat CTA if hero is dense)
435. Features (value proof, outcomes, differentiators)
446. CTA repeated 1 to 2 times (after key persuasion moments)
457. Footer (secondary links, legal, contact)
46
47See `references/landing-page-anatomy.md` for the full checklists and annotated examples.
48
49## Above-the-fold checklist
50
51Treat 'above the fold' as the content visible before scrolling on common viewports.
52
531. Define the value you offer (title)
542. Detail your approach (subheadline)
553. Help the user envision it (visual)
564. Establish credibility (social proof)
575. Simplify the next step (call to action)
58
59Implementation rules:
60- Make the primary CTA unmissable.
61- Make the visual concrete (product UI, before/after, outcome preview), not decorative.
62- Reduce friction with microcopy (no credit card, 60 seconds, cancel anytime).
63
64## Below-the-fold persuasion sequence
65
661. Show clear value (features)
672. Motivate to action (social proof)
683. Clarify questions (FAQ)
694. Repeat your call to action (CTA)
70
71Add sections only if they remove doubt (pricing, security, comparisons, case studies, integrations).
72
73## Output patterns to produce
74
75Choose the lightest deliverable that satisfies the user's request.
76
77### A) New landing page
78
79Provide:
80- Page goal, audience, offer, and primary CTA
81- Section-by-section outline mapped to the anatomy
82- Hero copy options (3 variations) and CTA microcopy
83- Proof plan (what to show and where)
84- Implementation: production-grade React code (shadcn + Tailwind + Iconify)
85
86### B) Landing page audit
87
88Provide:
89- A short diagnosis: what is the page asking the user to do and is it obvious
90- Issues and fixes grouped by: Above-the-fold, Below-the-fold, CTA, Proof, Copy, Design/UX, Performance
91- 5 to 10 prioritized recommendations (impact vs effort)
92- 3 A/B test ideas with clear hypotheses
93
94## Shadcn component mapping
95
96Prefer these building blocks:
97- Navigation: `Button`, `Sheet` (mobile menu), `Separator`
98- Hero: `Button`, `Badge`, `Card` (for a framed visual), `Input` (only if email capture is the CTA)
99- Social proof: `Card`, `Avatar` (testimonials), `Badge` (press or awards)
100- Features: `Card`, `Tabs` (only if comparison is critical)
101- FAQ: `Accordion`
102- Final CTA: `Card`, `Button`
103
104Add only the components you actually use.
105
106## Icons (Iconify only)
107
108Default icon source: https://icon-sets.iconify.design/
109
110Selection rules:
111- Pick one icon set prefix and stay consistent (example: `lucide:*` for a clean outline style).
112- Use icons to clarify hierarchy, not to decorate.
113- Accessibility: decorative icons should be `aria-hidden="true"`; meaningful icons should have text nearby.
114
115React usage:
116
117```bash
118npm i @iconify/react
119```
120
121```tsx
122import { Icon } from '@iconify/react'
123
124export function IconBullet() {
125 return (
126 <span className="inline-flex items-center gap-2">
127 <Icon icon="lucide:check" aria-hidden="true" className="size-4" />
128 <span>Cancel anytime</span>
129 </span>
130 )
131}
132```
133
134Notes:
135- `@iconify/react` loads icon data on demand by default. Use an offline approach only if the user requires zero network dependence.
136- Do not add `lucide-react` unless the user explicitly requests it.
137
138Optional: create an `AppIcon` wrapper for consistent sizing and accessibility. See `references/iconify.md`.
139
140## Design execution (distinctive, non-generic)
141
142Before writing code, decide:
143- Purpose: what problem does this page solve and for whom
144- Tone: commit to a bold direction (editorial, brutalist, luxury minimal, retro utilitarian, playful, etc.)
145- Constraints: performance, accessibility, brand rules
146- Differentiation: one memorable detail (layout twist, signature motion moment, unique motif)
147
148Then execute with craft.
149
150Typography
151- Choose characterful fonts. Avoid generic defaults.
152- Pair one display face (headlines) with a readable body face.
153
154Color and theme
155- Use a cohesive palette with 1 to 2 dominant colors and sharp accents.
156- Prefer CSS variables (shadcn theme tokens) so the design stays consistent.
157
158Motion
159- Use motion as guidance, not decoration: staged reveals, CTA emphasis, proof highlights.
160- Prefer a few high-impact moments over many micro animations.
161
162Spatial composition
163- Use deliberate hierarchy and whitespace.
164- Break the grid only when it improves clarity.
165
166For quick presets, see `references/aesthetic-directions.md`.
167
168## Implementation requirements
169
170- Use semantic HTML and accessible components (labels, focus states, reduced motion support).
171- Mobile-first responsive layout.
172- Optimize perceived performance: avoid heavy hero media, lazy-load below-the-fold images.
173- Keep the primary CTA consistent (label, destination, and promise).
174
175## Included starter asset
176
177If the user asks for a starter page scaffold, use:
178- `assets/vite-shadcn-iconify-landing/src/pages/LandingPage.tsx`
179
180This is a sectioned template that matches the anatomy and uses shadcn + Iconify.
181
182## Reference files
183
184- `references/shadcn-vite-setup.md`: install and configure shadcn/ui for Vite (Tailwind, aliases, CLI)
185- `references/iconify.md`: Iconify rules + an `AppIcon` wrapper component
186- `references/section-templates.md`: copy-paste section templates (Navbar, Hero, Proof, Features, FAQ, CTA, Footer)
187- `references/landing-page-anatomy.md`: anatomy, above/below-the-fold checklists, annotated examples
188- `references/copy-templates.md`: hero formulas, CTA microcopy, FAQ templates
189- `references/aesthetic-directions.md`: bold aesthetic presets to pick from quickly