SaaS landing page

Turn a product pitch into a page with a demo, proof, and a working signup.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# SaaS landing page

Turn a product pitch into a page with a demo, proof, and a working signup.

## Deliverable
A responsive landing page with a working primary CTA and setup instructions for the chosen signup destination.

## Stack and visual direction
- Recommended starting stack: Next.js, TypeScript and semantic CSS. Use static content where it serves the brief.
- Brutalism: Use strong type, visible structure, hard edges and limited accent color. Organize the page around obvious reading order and actions. Apply this direction to the website.

- Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [Frontend Design](https://github.com/anthropics/skills/tree/main/skills/frontend-design) (Skill) — Plan distinct typography, composition and interaction details before building UI.
  Fallback: Write a short plan for hierarchy, palette, spacing and interaction states, then review the actual screens against it.
- [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure.
  [Official setup](https://nextjs.org/docs/app/getting-started/installation).
- [Web Design Guidelines](https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines) (Skill) — Review frontend UI against usability and accessibility guidance.
  Access to the current upstream guidelines for the skill's full review. Fallback: Perform the recipe's keyboard, focus, responsive and feedback checks manually.

### Optional workflow boosters
- [Playwright CLI](https://github.com/microsoft/playwright-cli) (Skill) — Walk real browser interactions and collect screenshots or evidence for regressions.
  Node.js and supported browser binaries. Use a local build or authorized test environment. [Official setup](https://github.com/microsoft/playwright-cli#readme). Fallback: Walk the same primary journey in a local browser and record the viewport, actions and outcomes.

## Workflow
1. Identify one buyer, their pain point and the primary action. Build a product-led hero, a real walkthrough or labeled demo, credible proof from supplied material, and a signup or contact path.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] The primary and footer CTAs reach the intended destination.
- [ ] A successful signup and an invalid entry produce distinct, useful feedback.
- [ ] Claims, testimonials and logos trace to provided material or are omitted.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Check mobile navigation and every key page at narrow and desktop widths. Remove horizontal document overflow and optimize images with stable dimensions and appropriate alternatives.
- [ ] Check working buttons, links and footer destinations, clickable logo and contact paths where applicable, page titles, descriptions, favicon, a useful 404 and the current copyright year. Remove placeholder text and unused navigation.
- [ ] Verify forms with both valid and invalid submissions and useful success and error feedback.

Recipe resources

Source, setup, and compatibility details.