Product COMMUNITY

Website Builder (Landing Page Component System)

Generates complete landing pages from a component library and deploys them as a WordPress draft.

Level ●●● Advanced
Saves 4 to 8h per landing page
Version v2.0
Updated 2026-06-11
Available in: claude-code

Who it is for

Marketing teams, performance marketers, small agencies

Use cases

  • Set up a new campaign landing page using your existing corporate design.

Say this to activate the skill

""Build a landing page for this offer""""Use our components and create a WordPress draft""

Install

mkdir -p ~/.claude/skills/website-builder && curl -fsSL https://collectivebrain.de/en/skills/website-builder/SKILL.md -o ~/.claude/skills/website-builder/SKILL.md

The command drops this page's SKILL.md straight into the right directory. No terminal? Download the file below and upload it in Claude.ai under Settings, Capabilities. Need help with setup? How to install skills →

SKILL.md

---
name: website-builder
description: Generates campaign landing pages from the component library and saves them as a WordPress draft. Activate on "Build a landing page for this offer".
---

This skill assembles a conversion-focused landing page from an existing component library and creates it as a WordPress draft.

## When this skill activates
- The user asks for a new landing page for an offer, campaign, or product in the existing corporate design.
- An existing page serves as the base for a variant (new audience, new offer, A/B test).
- Content should be built from a component library into a WordPress draft.

## Workflow
1. Clarify the brief: offer, target audience, the single conversion goal (form, call, purchase), traffic source. If anything is missing, ask instead of guessing.
2. Inventory the component library: list blocks (hero, benefit grid, testimonial, FAQ, CTA, form). Sources: theme, block patterns, REST (`/wp/v2/blocks`).
3. Define the architecture. Default: hero with value proposition plus primary CTA, social proof, 3 to 5 benefits (outcomes, not feature lists), step-by-step process, FAQ, final CTA.
4. Write the copy: the headline states a concrete outcome in under 12 words. CTAs are verb phrases ("Book your call", not "Submit"). For ad traffic, match the ad message closely.
5. Use library blocks only. If a block is missing, report it and propose an alternative from the existing set instead of inventing new markup.
6. Create the draft: REST API (`POST /wp/v2/pages`, `status: "draft"`) or WP-CLI. Set slug, SEO title, meta description, featured image. Never publish directly.
7. Generate the preview link and self-review: mobile view, image loading, form action.
8. Hand over with a checklist: preview link, open placeholders, recommended tracking events (CTA click, form submit).

## Output format
- WordPress draft with slug, SEO title, and meta description
- Preview link plus a short doc: components in order, with reasoning
- List of open items (missing images, approvals, tracking)

## Quality rules
- Exactly one conversion goal per page; every CTA triggers the same action.
- The headline names a concrete outcome, never filler like "Welcome".
- No markup outside the library; report gaps, do not improvise.
- Create the page as a draft only; publish after approval.
- Every image has alt text; every page has exactly one H1.
- Forms ask only for fields required for the next step.
- Mobile check before handover: hero and first CTA visible without scrolling.

Share this skill

About this skill

Website Builder (Landing Page Component System) comes from Community and is part of a community plugin.

Sister brand for AI automation & workflow building: WhiteFox Automations · strategy & consulting stay with Collective Brain, built solutions come from WhiteFox.