Skip to content

Guide · Agent skill

How to use the Brand Landing Page Designer agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Brand Landing Page Designer is an agent skill for single-purpose product landing pages. Once installed, your coding agent runs a short brand interview before generating anything, then uses the Stitch design service to produce screens you can review and refine. This guide explains what the skill does, how to install it, how to trigger it, and what it needs to run, so you can get from a product with no visual direction to a deployable HTML bundle.

Brand Landing Page Designerwshobson/agents · MIT

Quick start

  1. 1Download and unzip the skill. Get the ZIP from this page and unzip it. Place the folder in ~/.claude/skills/ or in your project's .claude/skills/ folder.
  2. 2Prepare Stitch. Install the Stitch SDK and generate an API key from your Stitch dashboard. Export the key as an environment variable or add it to a .env file.
  3. 3Make the request. Ask the agent in plain language for a landing page and say you have no visual direction yet.
  4. 4Answer the brand interview. Respond to the questions about your product, brand feel, and visual preferences. Short answers are fine.
  5. 5Review the generated screens. Look at the Stitch screens the agent shows you and give specific feedback so it can iterate.
  6. 6Deploy the bundle. Take the packaged HTML bundle and follow the DEPLOY.md file in it.

What is an agent skill and what does this one make the agent do?

An agent skill is a folder containing a SKILL.md instruction file and optional reference files and scripts. When a skill is installed, the agent reads it and follows its workflow for matching requests. This skill, named brand-landingpage, changes how the agent approaches a landing page request: instead of producing a generic template, it first asks about your product, the feeling your brand should convey, and your colors, fonts and shapes.

After the interview, the agent uses the Stitch design service to generate landing page screens, shows them to you for feedback, iterates, and packages a deployment-ready HTML bundle that includes a DEPLOY.md file. Project state is saved in a local metadata file (.stitch/metadata.json), so work can resume later.

  • Brand interview covering the product, brand feel, and visual preferences
  • Screen generation and iteration through Stitch, with feedback rounds
  • Deployment-ready HTML bundle with a DEPLOY.md file
  • Saved project state so an unfinished page can be resumed

Install the skill from the downloaded ZIP

Download the ZIP from this page and unzip it. To make the skill available across all your projects, place the unzipped folder in ~/.claude/skills/. To limit it to one project, place it in that project's .claude/skills/ folder instead.

If you use the Claude apps, you can upload the skill instead. Open Settings, go to Capabilities, then Skills, and upload the skill there.

  • Personal (all projects): ~/.claude/skills/
  • Single project: .claude/skills/ inside the project folder
  • Claude apps: Settings → Capabilities → Skills, then upload

Set up Stitch before the first run

The skill depends on the Stitch SDK and a Stitch API key. The skill's own setup phase checks that the SDK is installed (globally by default, or through the project's package manager if you are inside a project) and that the API key environment variable is set. If the key is missing, you generate one from your Stitch dashboard and export it in your shell or add it to a .env file. The skill makes one minimal SDK call to confirm authentication.

Never paste your key into the chat. The skill is written to avoid displaying or echoing the key.

  • Stitch SDK, installed globally or in the project
  • Stitch API key stored as an environment variable, from your Stitch dashboard
  • Shell or .env file access to store the key
  • Stitch MCP tools in the agent runtime (optional, but the skill references them)

Trigger the skill with a natural request

You do not need a special command. Ask for a landing page, homepage, or marketing page in plain language, and say that you have no established visual direction. The skill's description tells the agent to use it in that situation.

If you already have a design mockup, design tokens, or need a dashboard, app UI, multi-page app or documentation site, the skill says to use frontend-design instead, so phrase your request accordingly.

  • "Design a landing page for my side project. I don't have any brand colors yet."
  • "Build a homepage for my API service. I want it to feel calm and modern."
  • "Create a marketing page for my waitlist. Walk me through the brand questions first."

What the interview asks

The interview is designed to be short. The agent asks about your project name, what it does, who it is for, and the action visitors should take. It then asks for three brand adjectives, a light or dark preference, and visual preferences for colors, fonts, and shapes. The skill's guidance says it asks no more than 10 questions in total, one at a time.

If you dump a README or product description, the agent should pull answers from it and skip those questions. Short answers are fine.

  • Product: name, what it does, target users, desired call to action
  • Brand feel: three adjectives, light or dark, optional admired site
  • Visual: colors or color feeling, modern or traditional fonts, sharp or rounded shapes

Handling images and logos

Do not plan to upload a logo or screenshot for Stitch to use. The skill notes that Stitch does not accept image uploads via API. If you attach an image, the agent asks you to describe it in your own words, saves the original file in .stitch/user-assets/, and reflects the described style in the design. You then swap the original image into the final HTML yourself with a standard img element.

What people use it for

  • Launching a side project or SaaS product that has no brand colors or fonts yet
  • Creating a single-purpose waitlist or product signup page quickly
  • Giving a small team a brand-first starting point instead of a random template
  • Producing a deployable HTML landing page for a non-designer founder

Frequently asked questions

Is the Brand Landing Page Designer skill free?

The skill is published under the MIT licence, as listed on this page. Stitch is a separate service that requires its own API key from your Stitch dashboard, and this page does not state Stitch pricing.

What do I need to run the brand-landingpage skill?

You need the Stitch SDK installed globally or in your project, a Stitch API key set as an environment variable, and shell or .env file access to store it. The skill also runs scripts and uses the network, and optionally uses Stitch MCP tools in the agent runtime.

Where do I install the skill?

Unzip the downloaded ZIP into ~/.claude/skills/ for all projects, or into a project's .claude/skills/ folder for one project. In the Claude apps you can instead upload it under Settings, Capabilities, Skills.

Can I use this skill for a dashboard or multi-page website?

No. The skill's scope is single-purpose landing pages and product marketing sites. For dashboards, app UIs, multi-page apps, documentation sites, or work with existing design tokens or mockups, the skill directs the agent to use frontend-design instead.

Can I upload my logo to the skill?

Not directly. Stitch does not accept image uploads via API, so you describe the image's style to the agent, and the original file is saved for you to add to the final HTML with an img element.

How do I resume a landing page I started earlier?

Project state is saved in .stitch/metadata.json. If that file exists when the skill starts, the agent resumes from the saved state instead of re-interviewing you.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you are launching a product or side project, have no visual direction yet, and want a brand-first process that ends in a deployable HTML bundle. Pick frontend-design if you already have a mockup or design tokens, or a different tool if you need a dashboard, app UI, multi-page site, or logo uploads.

Download the skill