Create a brand-trained Claude Skill, connect it to approved company knowledge through MCP, and turn a short campaign request into a source-grounded Webflow page with working forms, on-brand visuals, and human approval.
A reusable brand-to-Webflow system that produces campaign, event, ABM, or sales follow-up pages in about 15 minutes after the one-time foundation is complete.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
7 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
The speed does not come from writing copy faster or cloning another generic template. It comes from giving Claude a reusable brand and website operating system, then connecting that system to approved company knowledge so it can research before it writes. Webflow becomes the publishing shell, while Claude handles the source-grounded page structure and code; the marketer only resolves assets, form routing, QA, and approval.
Expected results
Reusable foundation
4-8 hours once
The initial investment creates the brand Skill, approved source access, code contract, Webflow shell, and form route that make later pages fast.
Repeat page production
15-30 minutes for a standard page
About 15 minutes is realistic when the page reuses an approved visual and form route. A new image direction, new integration, or unresolved proof adds review time.
Research quality
Source-grounded page
Claude researches the approved website and internal sources, then returns a source map instead of inventing proof or relying only on the requester's notes.
Publishing model
HTML inside the existing Webflow shell
The site's approved header and footer remain native Webflow components while the campaign-specific body is generated as scoped, embeddable code.
Automation option
Slack or Teams to marketer approval
n8n can orchestrate intake, research, generation, routing, and draft delivery while retaining a human gate before publication.
Step-by-step workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
2-4 hours once
2-4 hours once
This is a one-time foundation step, not work you repeat for every page.
Collect the reference pack
Create the Skill package
Test the Skill
A reusable Claude Skill that understands the company's brand, page patterns, copy style, code requirements, and approval rules.
Use screenshots from pages with different jobs, not ten visually identical product pages. Claude needs to see the boundaries of the design system as well as its most common pattern.
Create a reusable Claude Skill for producing on-brand, single-purpose landing pages for {{company_name}}.
REFERENCE FILES
- Brand guidelines: {{brand_guideline_files}}
- Full-page website screenshots: {{website_screenshot_files}}
- Approved copy samples: {{copy_sample_files}}
- Component and implementation rules: {{component_rules}}
- Existing page URLs to research: {{reference_urls}}
THE SKILL MUST LEARN
- Visual hierarchy, typography, spacing, grids, cards, buttons, forms, icons, and image treatment
- The company's writing style, terminology, proof style, CTA style, and prohibited claims
- Which page sections are reusable and which are campaign-specific
- The difference between event, campaign, gated offer, ABM, and sales follow-up pages
- How to generate Webflow-safe HTML, scoped CSS, and minimal JavaScript
- How to produce an asset manifest before the code
- How to cite or list the internal and website sources used for every factual claim
PACKAGE
Create:
1. `SKILL.md`
2. `/references/brand-rules.md`
3. `/references/component-rules.md`
4. `/references/copy-voice.md`
5. `/templates/page-request.md`
6. `/templates/source-map.md`
7. `/templates/asset-manifest.md`
8. `/templates/output-contract.md`
9. `/qa/pre-publish-checklist.md`
NON-NEGOTIABLE RULES
- One primary job and one primary CTA per page
- Never invent proof, customers, numbers, urgency, deadlines, or product capabilities
- Match the supplied site patterns before introducing a new pattern
- Mobile-first and accessible
- Return Webflow-embeddable code without `<html>`, `<head>`, or `<body>` tags
- Scope CSS beneath one unique wrapper class
- Name every required image and list it in the asset manifest
- Require human approval before publishing
Return the complete Skill package with file names and contents.1-2 hours once
1-2 hours once
Connect Claude to the internal sources it needs to research the page before generating it.
Choose the source
Define retrieval rules
Run a permissions test
Pro workflow preview
Previewing 2 of 10 steps
Get the remaining 8 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
A read-only, source-controlled connection between the Claude Skill and the company's approved website and internal content.
Do not connect an entire corporate drive. A smaller allowlisted knowledge set gives Claude better retrieval quality and makes governance much easier.
Create the source-access and retrieval policy for the landing-page Skill.
AVAILABLE SOURCES
- Public website: {{website_domain}}
- Google Drive or SharePoint connection: {{mcp_connection_name}}
- Approved folders or libraries: {{approved_locations}}
- Excluded locations: {{excluded_locations}}
- Source owners: {{source_owners}}
RETURN
1. Source priority order
2. Allowed content types
3. Excluded content types
4. Retrieval procedure for each page request
5. Required source-map fields
6. Conflict-handling rules
7. Stale-content rules
8. Missing-evidence behavior
9. Permission test cases
10. Quarterly access-review checklist
Rules:
- Read only
- Use only approved sources
- Never infer a factual claim when evidence is missing
- Surface conflicts for human review
- Record the source behind every proof point, product claim, date, and customer outcome.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
Produce a prospect-specific sales deck, account brief, talk track, and claim-check checklist for sales calls or follow-up.
Create a daily or weekly alert system that sends content angles, source links, recommended POVs, and draft prompts to Slack or Airtable.
Create an interactive lead magnet with scoring logic, questions, result bands, lead capture, result page copy, and follow-up workflow.