Landing page & web document builder
Assign an idea or copy and a frontend designer drafts a distinctive, on-brand landing page or interactive web document, critiques it, and hands it to you to review and ship.
Saves you ~5.3 h / run
How it works
- Trigger
- When you start the “Build web document” workflow.
- Job
- Plan a distinctive design, build the document, revise, and hand off.
- Outcome
- A polished landing page implementation ready for approval.
What it installs
Agents 2
-
Frontend Designer
Turns copy and ideas into reviewed, ship-ready web document drafts.
-
Landing page & web document builder Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Landing page & web document builder quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Build web document
Plan a distinctive design, build the document, self-critique against the guidelines, revise, and hand off.
Goals 1
-
On-brand pages ship without slop
Assigned pages become distinctive, accessible, ship-ready documents. Success looks like: Every assignment ends in an approved landing page or web document that is distinctive and subject-specific, passes the accessibility/contrast/responsive floor, and — when a repository is connected — is shipped via an approved pull request.
Skills 4
-
web-documents-builder
Build elaborate, self-contained interactive web documents with React, TypeScript, Tailwind, and component primitives, then bundle them into a single shareable HTML file. Adapted from anthropics/skills/web-documents-builder.
-
frontend-design
Make distinctive, intentional visual-design choices — palette, typography, layout, motion, and copy — that are specific to the brief and never read as templated defaults. Adapted from anthropics/skills/frontend-design.
-
web-design-guidelines
Audit UI code against Web Interface Guidelines — accessibility, keyboard/focus, contrast, motion, responsiveness, and state coverage — reporting findings as file:line. Adapted from vercel/agent-skills/web-design-guidelines.
-
react-best-practices
Write performant React/Next.js: eliminate waterfalls, trim bundle size, optimise re-renders and rendering. 8 priority categories of rules. Adapted from vercel/agent-skills/react-best-practices.
Requirements
- Connected repository — Shipping the approved page as code requires a connected repository the document lands in. The agent reads the repo's tokens and components and opens a pull request in the connected repository. Without a repo, it still delivers a self-contained, bundled document draft for review.
Setup guide
How to Build Landing Pages With an Agent
A practical guide to building reviewed landing pages from briefs, design plans, accessibility checks, and approval.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.