Folloze-Industry-Campaign-Page-Builder

Folloze Industry Campaign Page Builder

Use this skill when the page should serve a vertical, segment, persona, cohort, event audience, or campaign group. The output should be reusable across multiple accounts while still feeling specific enough to support ABM.

Fit

Use this for industry pages, one-to-few account clusters, vertical plays, persona paths, event follow-up cohorts, regional campaigns, and campaign-level pages. Use Folloze-One-To-One-Microsite-Builder when one named account owns the story.

Required Foundations

• Confirm whether the motion is broad audience-level work or a named one-to-few cluster. If an upstream route handoff is supplied, inherit it without rerunning routing.
• Run $abm-strategist only for one-to-few and named account-cluster work. For a broad vertical, persona, event, or regional motion, keep the brief audience-level.
• For a Folloze-owned experience, use $folloze-brand-kit. For an external brand, run $brand-harvester and require a zero CLI exit plus brand.json.validation.status: ok before visual design.
• Use $folloze-board-quality-core for source discipline, experience-shape selection, responsive and interaction QA, analytics, and MCP preflight.

Minimum Inputs

Gather only what is missing:

• Industry, segment, cohort, persona, or campaign group.
• Campaign goal and CTA.
• Source brand or design input.
• Public or approved content sources.
• Whether named account examples are allowed.
• Required resource, event, product, or offer modules.

Workflow

1. Define the audience boundary: who is included, who is not, and what shared pressure connects them.
2. For one-to-few or named account-cluster work, run $abm-strategist and inherit its approved brief and page structure. For broader motions, build an audience-level campaign brief: audience insight, why now, offer, proof, CTA, and source constraints.
3. Complete the brand gate before visual design: $folloze-brand-kit for Folloze-owned work or a saved, reviewed, validated $brand-harvester bundle for an external brand.
4. Choose a reusable structure: vertical narrative, cohort workflow, persona path, account-selection hub, or lifecycle/event page.
5. Build one self-contained local HTML file in the active repo.
6. Use approved industry claims and public proof. Do not invent market stats or customer logos.
7. When named account examples, named customer examples, customer logos, quantified outcomes, benchmarks, approved stats, or other approved proof points are missing, unavailable, unapproved, weak, or disallowed, load references/proof-without-logos.md before writing proof sections, resource modules, or publishing.
8. If account examples are included, keep them illustrative and public-safe.
9. QA desktop/mobile, CTA behavior, source-brand fidelity, and whether the page stays reusable across the whole audience.
10. Complete a buyer-facing QA pass across copy, links, interactions, desktop/mobile layout, placeholders, and dead controls before save, publish, or delivery.

Page Standards

• The hero should name the industry, segment, persona, or campaign group clearly.
• Copy should describe the shared business problem, not a generic product pitch.
• Use modules that help visitors self-identify: tabs, paths, filters, lifecycle states, account examples, or role-specific cards.
• If personalization is planned later, mark implementation hooks cleanly without exposing internal merge-tag mechanics to buyers.

Recommended Page Shapes

• Industry narrative: market pressure, operational challenge, solution path, proof, CTA.
• Persona path: choose your role, role-specific challenge, resources, CTA.
• Event cohort: pre-event, during-event, post-event journey or follow-up paths.
• Account cluster: shared account pattern, examples, common triggers, next action.
• Campaign hub: overview, resource modules, proof, content tracks, CTA.

QA Gates

Before final response or publish:

• The page is specific enough for the selected audience but not overfit to one account.
• One-to-few/account-cluster work has an approved $abm-strategist brief and page structure.
• The selected brand path is complete: $folloze-brand-kit for Folloze-owned work, or a durable validated $brand-harvester bundle for external-brand work.
• $folloze-board-quality-core passed for source/proof discipline, selected experience shape, desktop/mobile render, controls, analytics, accessibility, and save readiness.
• Rendered desktop and mobile views were compared with the harvested source screenshots or approved equivalent brand evidence.
• Named examples are public-safe and approved.
• No unsupported market claims, fake logos, or invented stats.
• CTAs and path choices perform real actions.
• Mobile path selection is readable and tappable.
• Buyer-facing copy, links, interactions, desktop/mobile layout, placeholders, and dead controls have been checked and any blocking issues have been fixed or explicitly reported.
• If saved through Folloze MCP, use the available Folloze MCP publishing tools and current Folloze guide. Report local source path, board ID, returned edit URL, and public URL status separately.

Final Response

Return the local file path, brief mode and approval status, brand-harvest path and review status, audience boundary, page shape, CTA, rendered QA status, and Folloze save/publish status.