claude-landing-composer — Claude Code skill: setup and guide
claude-landing-composer builds custom Next.js landing pages with Tailwind v4 and Motion animations. Useful when you need ready-to-ship marketing sections without typical AI templates.
MIT 178 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill claude-landing-composer -a claude-codeWhat claude-landing-composer does
The skill builds landing pages step by step, covering layout and animated components. The default stack relies on Next.js App Router, TypeScript, Tailwind CSS v4, and the Motion library. The workflow bans generic AI tropes: no default purple gradients and no emoji icons. Lucide or Heroicons handle the visual markers.
Development follows five phases: planning against design tokens, coding components, drafting concise copy, validating builds, and running a design critique pass. Animations like counters and staggered reveals always respect prefers-reduced-motion.
The skill expects an existing Next.js project with Tailwind and Motion configured. It tests the build on the local dev server before finishing, so running it in an empty directory without dependencies will break the process.
What it helps with
- build marketing sections using Next.js App Router and Tailwind v4
- wire entry and scroll animations with Motion and prefers-reduced-motion support
- structure hero, pricing, and objection-handling components with Lucide icons
- verify landing page markup via local build checks before shipping
Example prompts for the agent
- Build a product landing page in Next.js using Tailwind v4 and Motion components
- Create an asymmetric hero section and pricing table using our design system tokens
- Review and rewrite landing page copy to remove marketing filler and add objection handling
How to install claude-landing-composer
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-landing-composer -a claude-code2Manually: put the files in place
~/.claude/skills/claude-landing-composer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/claude-landing-composer/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-landing-composer -a codex2Manually: put the files in place
.agents/skills/claude-landing-composer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-landing-composer -a cursor2Manually: put the files in place
.cursor/skills/claude-landing-composer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills claude-landing-composer2Manually: put the files in place
.github/skills/claude-landing-composer/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-landing-composer -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path claude-landing-composerManually: put the files in place
.devin/skills/claude-landing-composer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-landing-composer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about claude-landing-composer
How to install claude-landing-composer in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill claude-landing-composer -a claude-code in your terminal. This downloads the skill to ~/.claude/skills/claude-landing-composer/SKILL.md.
What tech stack does this skill generate?
It targets Next.js App Router, TypeScript, Tailwind CSS v4, and Motion, with vector icons sourced from Lucide or Heroicons.
What design constraints does it enforce?
It bans default purple gradients and emojis, insists on real design tokens, and requires a successful dev-server compilation pass.
Source text
SKILL.md · MIT
---
name: claude-landing-composer
description: Compose a premium, animated landing page section by section in Next.js + Tailwind + Motion (Framer Motion) — built on a real design system, with editorial copy and motion that feels human-crafted, not template-generated. Use when building or rebuilding a landing page, marketing site, or hero/feature/pricing/CTA sections that need to look production-ready and bespoke from day one.
tools: Read, Write, Bash, Glob, Grep, WebSearch, WebFetch, Agent
model: inherit
---
# Claude Landing Composer
Most AI-built landing pages are instantly recognizable: centered hero, three feature cards, a gradient, generic copy. This skill builds pages that don't read as generated — editorial layout, real design tokens, motion with intent, and copy that sounds like a person wrote it.
Build on a design system from `claude-design-system-architect` when one exists. Run the result through `claude-design-critic` before shipping.
## Step 1 — Plan the page
- **Goal & one action** — what the page must get the visitor to do.
- **Audience** — pull a buyer persona from `icp-deep-scanner` if available so the copy speaks to a real reader.
- **Sections** — choose the minimum that earns the goal (hero → proof → how/why → objection-handling → pricing → CTA). Cut anything that doesn't move the visitor forward.
- **Tokens** — load the design system. If none exists, generate one first (`claude-design-system-architect`); do not hardcode arbitrary colors/sizes.
### Stack & house rules
Next.js (App Router) + React + TypeScript + Tailwind v4 + Motion (the library formerly published as Framer Motion) — the default stack. **No purple. No emoji** — use Lucide/Heroicons. Warm/earth tones and dark surfaces welcome. Motion is expected — typewriter, animated counters, spring/stagger reveals — used with restraint.
## Step 2 — Compose section by section
Build each section as a real component using tokens. For each, decide layout, content, and motion deliberately:
- **Hero** — a sharp headline (not "Welcome to {Product}"), a sub that states the actual value, one primary CTA. Consider an asymmetric or editorial layout over the default dead-center stack.
- **Proof** — logos, a real metric, or a specific outcome — not "trusted by thousands."
- **Feature/why** — show the value in context; avoid the three-identical-cards reflex unless it genuinely fits. Vary rhythm and alignment between sections.
- **Objection handling / FAQ** — answer the real hesitation a prospect has.
- **Pricing** (if needed) — clear, confident, value-anchored.
- **CTA** — one action, restated.
**Motion:** entrance reveals on scroll, but vary them — not the identical fade-up on every block. Respect `prefers-reduced-motion`. Motion should guide the eye to what matters, not decorate everything equally.
## Step 3 — Write copy that isn't AI-flavored
- Cut the tells: "elevate", "unlock", "seamless", "in today's fast-paced world", "we're thrilled", em-dash-everything, tricolon-everything.
- Specific > generic. Confident > hedged. Short > padded.
- Match the user's voice: direct, no corporate fluff.
- Write real microcopy (buttons, empty states, captions) — not "Learn More" everywhere.
## Step 4 — Build it real
Write the components, wire the tokens, ensure it's responsive (mobile-first, real breakpoints) and accessible (semantic HTML, focus states, alt text, AA contrast). Run the dev server / build and confirm it compiles before claiming it works.
## Step 5 — Critique pass (mandatory)
Run `claude-design-critic` (or the anti-ai-frontend review) on the output to strip any remaining generated-looking patterns in both design and copy. Then deliver with the file paths and a short note on the choices made.
## The anti-generated checklist (apply before shipping)
- Layout varies between sections; not every section is a centered stack.
- Whitespace is generous and intentional, not uniform.
- One confident accent; no rainbow gradients; never default-purple.
- Headlines are specific and human; no filler value-props.
- Motion has variety and restraint; reduced-motion respected.
- Icons, never emoji. Real microcopy, never "Learn More" x5.
## Guardrails recap
Build on real tokens, never arbitrary values · responsive + accessible + AA contrast · no purple / no emoji · compile/run before claiming done · always finish with a de-AI critique pass.
© OneWave-AI · MIT · OneWave-AI/claude-skills