Brand Landingpage
Run a structured brand-and-purpose interview before your agent generates a landing page so the page reflects real product positioning instead of a generic template.
Overview
Brand Landingpage is an agent skill most often used in Validate (also Build frontend) that runs a capped, phased brand-discovery interview before generating a product landing page.
Install
npx skills add https://github.com/wshobson/agents --skill brand-landingpageWhat is this skill?
- Interview philosophy caps the flow at a maximum of 10 questions so technical founders do not abandon the process.
- Phase A (Product & Purpose) and follow-on phases gather naming, audience, and primary CTA in conversational order—not a
- Translates design vocabulary (visual hierarchy, color temperature, typographic contrast) for developer audiences who alr
- Extracts answers from volunteered README or product dumps and skips redundant questions.
- Gently pushes back when users try to skip the interview (“just generate something”) because the interview is framed as t
- Maximum of 10 questions across all interview phases
- Phase A: Product & Purpose as the first structured block
Adoption & trust: 25.4k installs on skills.sh; 36.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are ready to ship a landing page but only have a README or a vague idea, so any generated page looks like a generic template.
Who is it for?
Indie developers who want a fast, structured discovery pass before AI-generated landing pages or marketing sites.
Skip if: Teams that already have an approved brand book, final copy deck, and signed-off designs—skip straight to implementation.
When should I use this skill?
Before generating or redesigning a product landing page when brand, audience, or CTA details are missing or only implied in a README.
What do I get? / Deliverables
You leave with explicit product purpose, audience, CTA, and brand-direction answers your agent can turn into on-brand landing copy and structure.
- Completed brand-discovery answers across phased interview
- Inputs for landing copy, CTA, and visual-direction generation
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Validate because the skill’s primary value is scoping messaging, audience, and CTA intent before any landing page is built or shipped. Landing subphase matches the artifact: a conversion-focused page whose copy, hierarchy, and brand cues must be decided up front.
Where it fits
Run the Product & Purpose questions to lock project name spelling, audience, and primary CTA before any HTML is drafted.
Clarify what action the page should drive when the landing surface doubles as pricing or signup positioning.
Reuse captured hex, typography, and hierarchy preferences when implementing or regenerating hero and feature sections.
Align launch posts and short links with the same brand story the interview documented.
How it compares
Use instead of one-shot “build me a landing page” prompts when messaging and brand constraints still live only in your head.
Common Questions / FAQ
Who is brand-landingpage for?
Solo and indie builders using Claude Code, Cursor, or Codex who can ship code but want help articulating brand and landing-page intent before generation.
When should I use brand-landingpage?
In Validate when scoping a new landing or waitlist page; in Build when rewriting hero copy or visual direction; anytime you catch yourself saying “just generate something” without brand answers.
Is brand-landingpage safe to install?
It is a conversational workflow skill with no inherent shell or network requirements in the framework itself—review the Security Audits panel on this Prism page before installing from any source.
SKILL.md
READMESKILL.md - Brand Landingpage
# Brand Discovery Interview Framework ## Interview Philosophy - Ask a maximum of 10 questions across all phases. Developers will lose patience faster than most -- they want to ship. - The user is technically literate. You can say "CTA," "hex value," "HTML," or "deploy." What needs translating is design language: "visual hierarchy," "brand identity," "color temperature," "typographic contrast." - If the user volunteers information unprompted (e.g., dumps a README or product description), extract answers from it and skip those questions. - When the user seems uncertain about design preferences, offer 2-3 concrete examples to choose from rather than waiting for them to articulate from scratch. - Treat the interview as a conversation, not a form. Acknowledge answers before moving on. - One question at a time. Never stack multiple questions in a single message. - Respect short answers. Developers tend to be terse. If the answer covers the question, move on. - **The user will try to skip this.** They'll say "just generate something" or "here's my README, figure it out." Push back gently. The interview is the skill's primary value -- without it, you're producing a generic template they could get from any page builder. --- ## Phase A: Product & Purpose **Goal:** Understand what the product does, who it's for, and what action the landing page should drive. ### Core Questions (ask in order, skip any already answered) 1. "What's your project called?" - Extract exact spelling, capitalization, and any tagline they mention. 2. "Give me the elevator pitch -- what does it do and why should someone care?" - If too technical: "Imagine explaining this to someone who might use it but isn't a developer. What problem does it solve for them?" - If overly broad: "If you had to pick the one thing that makes this worth checking out, what is it?" 3. "Who are your target users? Developers? Designers? Non-technical teams? Everyone?" - If they say "developers": "What kind -- frontend, backend, DevOps, data? What stack or ecosystem?" - If they say "everyone": "Who's shown the most interest so far, or who would you pitch to first?" - If they have no users yet: "Who did you build this for originally? Whose problem were you solving?" 4. "What's the primary action you want a visitor to take? For example: sign up, start a free trial, join the waitlist, book a demo, star the repo, or try a live demo." - If they list multiple: "Which one matters most right now -- the one you'd put on the biggest button?" - Map their answer to button text internally (e.g., "try it out" --> "Try It Free"). ### What to Extract From Phase A | Field | Example | |-------|---------| | Project name (exact spelling) | "Railtrack" | | Elevator pitch (1-2 sentences) | "Open-source deployment pipeline that catches breaking changes before they hit production" | | Target users | "Backend engineers working with Kubernetes, mostly at mid-size companies" | | Primary CTA | "Start free trial" --> button text "Start Free Trial" | | Bonus (if volunteered) | Repo URL, existing docs, tech stack, pricing model | ### Transition Rule Move to Phase B when you have: project name + elevator pitch + target users + primary CTA. These four are non-negotiable. If the user tries to skip ahead ("just generate something, it's a CLI tool for managing databases"): - Extract what you can from their statement. - Ask only the essential gaps (CTA + brand feel at minimum -- 2 questions). - Default everything else with reasonable choices and tell them what you defaulted: "I'm going with a clean, modern look with a dark theme since this is a dev tool. We can adjust after you see it." --- ## Phase B: Brand Feel **Goal:** Understand the emotional impression the brand should make and whether it leans light or dark. ### Core Questions 1. "Pick 3 words that describe how your product should come across to visitors." - Offer a menu if they hesitate: > Some options: bold, clean, mi