Skill-Details
landing
Directly generates polished single-file landing pages.
Vor Nutzung prüfen
Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.
SKILL.md
Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.
--- name: landing description: "Generates a premium single-page HTML landing page with 3D CSS animations, GSAP scroll effects, and mouse-parallax depth. Forcing intake (product + elevator pitch, audience register, brand overrides, tone) locks down positioning before any copy or markup is written, so the page reflects the actual product rather than generic boilerplate. Use whenever the user says 'landing for X', 'create a landing page', 'build a landing page', 'make a landing page for X', 'I need a web page for Y', or provides product/service details and wants a polished website. Also triggers on 'promotional page', 'product page', 'one-pager', 'web presence', 'sales page'. Outputs a single self-contained HTML file (Claude Code) or HTML artifact (Claude.ai). Supports configurable brand colors via CSS custom property overrides." license: MIT metadata: source_spec: "megaprompts/04-landing-megaprompt.md" build_pattern: "Path B (direct conversion)" distinct_from: "product-team/skills/landing-page-generator (different output format + optimization target)" version: 1.0.0 --- # Landing — Premium HTML Landing Page Generator > **Distinct from `product-team/skills/landing-page-generator/`.** That skill outputs Next.js TSX components optimized for conversion / lead-gen. THIS skill outputs a single self-contained `.html` file optimized for premium visual experience with GSAP animations. Pick by use case. Generate a polished, self-contained `.html` landing page from a text prompt or brief. The output is ONE HTML file: all CSS inline in `<style>`, all JS inline in `<script>`, only external dependencies being Google Fonts + GSAP via CDN. The page is visually distinctive, animated, and production-quality. ## Invocation Triggers - "create a landing page" - "build a landing page" - "make a landing page for X" - "I need a web page for Y" - "promotional page" - "product page" - "one-pager" - "web presence" - "sales page" - "landing for X" ## Delivery Mode In **Claude Code CLI**, write the file to disk at the specified path. In **Claude.ai web**, create an HTML artifact with the same content. ## Phase 0: Grill-Me Intake (4 forcing questions, one at a time) Dependency-ordered. Each question carries explicit "why I'm asking". Stop condition: max 4. ### Q1 (root) — Product / Service > **What's the product or service? Give me the name + a 1–2 sentence elevator pitch — what does it do, and who's it for?** > > *Why I'm asking:* The headline, subtext, and feature copy all derive from this. "App for productivity" produces generic boilerplate; "Async standup tool for remote engineering teams who hate Zoom" produces a landing page that converts. **Refuse mush.** If user gives just a name with no pitch, push back once: "What does it do? Who's it for?" If still no pitch after push-back, deliver with explicit "generic positioning" caveat. ### Q2 (depends on Q1) — Audience Register > **Who's the audience? Pick one:** > > 1. **Technical buyers** (engineers, ops, security) > 2. **Business buyers** (PMs, execs, ops leaders) > 3. **Consumers** (general public, hobbyists) > 4. **Internal** (employees, partners — not for public sale) > > *Why I'm asking:* Audience dictates copy register, jargon level, social-proof choices, and CTA framing. Technical buyers want specifics; consumers want benefits; internal pages can skip persuasion. Forcing choice. ### Q3 (always) — Brand Overrides > **Brand colors / fonts to override the default (dark navy + teal + Inter)? Provide as: primary HEX, accent HEX, optional bg HEX. Or say "default" if you want the polished default.** > > *Why I'm asking:* The default is intentionally beautiful, but matching your brand makes the page feel native to your existing site. Even just a primary color override goes a long way. Accept "default" or partial overrides (e.g., just primary). If only primary provided, derive accent algorithmically (lighten / darken). ### Q4 (depends on Q1) — Tone > **Tone — pick one:** > > 1. **Vollständige Quelle auf GitHub lesen (öffnet externe Seite)