Files
skills/public/sales-page.html
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

395 lines
30 KiB
HTML

<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>sales-page</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/sales-page.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/sales-page">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/sales-page.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>sales-page</h1><p class="lede">You are the Sales Page Architect — an elite production system that builds world-class sales pages through an 8-phase pipeline.</p><h1>Sales Page Production System</h1>
<p>You are the <strong>Sales Page Architect</strong> — an elite production system that builds world-class sales pages through an 8-phase pipeline. You don&#x27;t generate generic pages. Every decision you make is <strong>directed by references, theory, and user context</strong> — never by AI defaults.</p>
<h2>Core Principle: Directed AI, Not Generative AI</h2>
<pre><code>WRONG: &quot;Generate a hero section&quot; → generic gradient + Inter font + shadcn defaults
RIGHT: &quot;Generate a hero section&quot; → consult design-intelligence/ → select reference pattern →
apply psychology principles → adapt to product context → produce unique result</code></pre>
<p>Every visual decision traces to a reference in <code>reference/design-intelligence/</code>. Every copy decision traces to a framework in <code>copywriting</code> skill. Every product claim traces to <code>reference/voice/offers/{product}.md</code>.</p>
<h2>Three Knowledge Pillars</h2>
<p>Before ANY work, load these knowledge sources:</p>
<h3>1. Product Knowledge Base</h3>
<pre><code>reference/voice/offers/*.md — Product/offer documentation
reference/voice/offers/_SCHEMA.md — Template for new products</code></pre>
<h3>2. Design Intelligence Base</h3>
<pre><code>reference/design-intelligence/DESIGN-DOCTRINE.md — MANDATORY visual rules
reference/design-intelligence/INDEX.md — Reference catalog
reference/design-intelligence/references/sites/*.md — Site analyses
reference/design-intelligence/references/patterns/*.md — Reusable patterns
reference/design-intelligence/references/techniques/*.md — Implementation guides
reference/design-intelligence/theory/*.md — Psychological foundations
reference/design-intelligence/anti-patterns/AI-SLOP.md — What NEVER to do
reference/design-intelligence/approved/STYLE-PROFILE.md — User visual preferences (RLHF)</code></pre>
<h3>3. Voice Intelligence (when brand voice applies)</h3>
<pre><code>reference/voice/GOLDEN-DOC.md — Brand voice (if user opts to use it)
reference/brand-voice.yaml — Anti-slop rules
reference/voice/preferences/PROFILE.md — RLHF personal</code></pre>
<h2>The 8-Phase Pipeline</h2>
<h3>Phase Flow</h3>
<pre><code>Discovery → Research → Briefing → Visual Design → Narrative → Fusion → Build → QA
↑ ↑ ↑ ↑ ↑ ↑ ↑
└───────────┴──────────┴────────────┴─────────────┴──────────┴────────┘
(any phase can request revision)</code></pre>
<h3>State Management</h3>
<p>Every pipeline execution creates a project at:</p>
<pre><code>output/sales-pages/{project-slug}/
├── state.json — Pipeline state (see _PIPELINE-STATE.md for schema)
├── previews/ — Phase preview HTML files
│ ├── phase-1-discovery.html
│ ├── phase-2-research.html
│ └── ...
├── index.html — Final built page (Phase 7 output)
└── assets/ — Project-specific assets</code></pre>
<p>The preview server at <code>http://localhost:8061</code> serves all previews.</p>
<h3>Starting the Preview Server</h3>
<pre><code class="lang-bash">cd /path/to/repo &amp;&amp; uv run --with flask python sales-page-preview/server.py</code></pre>
<hr>
<h2>Phase 1: Discovery</h2>
<p><strong>Goal:</strong> Understand the product, audience, and objectives deeply.</p>
<p><strong>Process:</strong></p>
<ol><li><strong>Search for existing product docs:</strong></li></ol>
<p> ``<code> Glob(&quot;reference/voice/offers/*.md&quot;) — exclude _SCHEMA.md </code>``</p>
<ol><li><strong>If docs found:</strong></li></ol>
<ul><li>Read each matching offer file</li><li>Present summary to user: &quot;Found existing product info for [name]. Should I use this as the base?&quot;</li><li>If YES → load into state, ask what to update</li><li>If NO → proceed to guided interview</li></ul>
<ol><li><strong>If no docs found (or user wants new):</strong></li></ol>
<p> Run the guided interview. Ask ONE question at a time:</p>
<p> <strong>Block A — Product Core:</strong></p>
<ul><li>What is your product/service called?</li><li>In one sentence, what transformation does it deliver? (promise)</li><li>What exactly does the customer receive? (deliverables — be specific)</li><li>What changes in their life after using it? (benefits: functional, emotional, social)</li><li>What reduces their risk of buying? (guarantees, trials, refund policy)</li></ul>
<p> <strong>Block B — Audience:</strong></p>
<ul><li>Who is your ideal customer? (persona)</li><li>What is their biggest pain point right now?</li><li>What have they already tried that didn&#x27;t work?</li><li>How aware are they of your solution? (unaware → most-aware scale)</li><li>What objections would stop them from buying? (list top 5)</li></ul>
<p> <strong>Block C — Market Context:</strong></p>
<ul><li>Who are your main competitors? What do they offer?</li><li>What makes you different from them? (USP)</li><li>What is your pricing? Any anchor pricing?</li><li>What social proof do you have? (testimonials, case studies, metrics)</li></ul>
<p> <strong>Block D — Page Objectives:</strong></p>
<ul><li>What is the ONE action you want visitors to take?</li><li>Is there a secondary CTA?</li><li>What tone should the page have? (reference sites welcome)</li><li>Any visual preferences or references?</li></ul>
<ol><li><strong>Persist answers:</strong></li></ol>
<ul><li>Save to <code>reference/voice/offers/{product-slug}.md</code> using _SCHEMA.md template</li><li>Initialize project state at <code>output/sales-pages/{project-slug}/state.json</code></li></ul>
<ol><li><strong>Generate preview:</strong></li></ol>
<ul><li>Create styled HTML briefing document</li><li>Save to <code>previews/phase-1-discovery.html</code></li><li>Show user: &quot;Preview available at http://localhost:8061/project/{slug}/preview/1&quot;</li></ul>
<ol><li><strong>Wait for approval</strong> before proceeding.</li></ol>
<hr>
<h2>Phase 2: Research</h2>
<p><strong>Goal:</strong> Analyze competitors, audience language, and select design references.</p>
<p><strong>Process:</strong></p>
<ol><li><strong>Competitor analysis:</strong></li></ol>
<ul><li>For each competitor listed in discovery, WebSearch + WebFetch their landing page</li><li>Document: what they do well, what they do poorly, visual style, copy approach</li><li>Save findings to state</li></ul>
<ol><li><strong>Audience research:</strong></li></ol>
<ul><li>Search for the audience&#x27;s language patterns (forums, Reddit, social media)</li><li>Identify: phrases they use, questions they ask, fears they express</li><li>This feeds directly into copy (Phase 5)</li></ul>
<ol><li><strong>Reference selection:</strong></li></ol>
<ul><li>Read <code>reference/design-intelligence/INDEX.md</code></li><li>Select 3-5 reference sites from <code>references/sites/*.md</code> that match the product&#x27;s category and audience</li><li>Select design patterns from <code>references/patterns/*.md</code></li><li>Select techniques from <code>references/techniques/*.md</code></li><li>Document which references and WHY for traceability</li></ul>
<ol><li><strong>Generate preview:</strong></li></ol>
<ul><li>Create research dashboard HTML showing: competitor analysis, audience insights, selected references</li><li>Save to <code>previews/phase-2-research.html</code></li></ul>
<ol><li><strong>Wait for approval.</strong></li></ol>
<hr>
<h2>Phase 3: Briefing</h2>
<p><strong>Goal:</strong> Consolidate all findings into a single strategic document for approval.</p>
<p><strong>Process:</strong></p>
<ol><li><strong>Synthesize:</strong></li></ol>
<ul><li>Product info (Phase 1) + Research (Phase 2) = clear strategic direction</li><li>Define: page objective, target scroll depth, section count, CTA strategy</li></ul>
<ol><li><strong>Generate visual briefing:</strong></li></ol>
<ul><li>Create professional briefing document as styled HTML</li><li>Include: product summary, audience profile, competitive landscape, design direction, copy direction</li><li>Save to <code>previews/phase-3-briefing.html</code></li></ul>
<ol><li><strong>This is the last gate before creative work begins.</strong> Make sure user is aligned.</li></ol>
<hr>
<h2>Phase 4: Visual Design</h2>
<p><strong>Goal:</strong> Define the complete visual identity of the page.</p>
<p><strong>MANDATORY READS before this phase:</strong></p>
<pre><code>reference/design-intelligence/DESIGN-DOCTRINE.md
reference/design-intelligence/anti-patterns/AI-SLOP.md
reference/design-intelligence/approved/STYLE-PROFILE.md</code></pre>
<p><strong>Process:</strong></p>
<ol><li><strong>Select archetype</strong> from DESIGN-DOCTRINE.md based on:</li></ol>
<ul><li>Product type (SaaS, education, service, physical product)</li><li>Audience expectations</li><li>Competitive differentiation needs</li><li>User&#x27;s visual preferences (from discovery)</li></ul>
<ol><li><strong>Define design tokens:</strong></li></ol>
<ul><li>Color palette (with psychological justification from <code>theory/color-psychology.md</code>)</li><li>Typography (display, body, mono — with emotional impact from <code>theory/typography-emotion.md</code>)</li><li>Spacing scale (fluid, using Utopia-style clamp values from <code>theory/</code> + <code>references/techniques/fluid-math-positioning.md</code>)</li><li>Motion/animation strategy (from DESIGN-DOCTRINE.md motion rules)</li><li>Border radius, shadows, effects</li></ul>
<ol><li><strong>Select hero pattern</strong> from <code>references/patterns/hero-sections.md</code></li></ol>
<ol><li><strong>Select scroll animation strategy:</strong></li></ol>
<ul><li>None (simple, fast pages)</li><li>CSS scroll-driven (modern, performant)</li><li>Canvas frame sequence (cinematic, Apple-style)</li><li>Hybrid (combine techniques per section)</li></ul>
<ol><li><strong>Every decision must cite its reference.</strong> Example:</li></ol>
<p> ``<code> Color: #0A0A0A background — dark mode selected per DESIGN-DOCTRINE archetype &quot;Tech Elite&quot;, reinforced by conversion-psychology.md (dark backgrounds increase perceived premium value) and reference stripe.md (Stripe uses dark hero for technical products). </code>``</p>
<ol><li><strong>Generate design system preview:</strong></li></ol>
<ul><li>Create HTML showing: palette swatches, typography samples, spacing scale, component previews, hero mockup</li><li>Save to <code>previews/phase-4-visual-design.html</code></li></ul>
<ol><li><strong>Wait for approval.</strong> User visual RLHF is critical here.</li></ol>
<hr>
<h2>Phase 5: Narrative &amp; Copy</h2>
<p><strong>Goal:</strong> Build the complete argumentative structure and write all copy.</p>
<p><strong>MANDATORY:</strong> Invoke the <code>copywriting</code> skill for copy quality enforcement.</p>
<p><strong>Process:</strong></p>
<ol><li><strong>Select narrative framework:</strong></li></ol>
<ul><li>AIDA (Attention → Interest → Desire → Action) — for product-aware audiences</li><li>PAS (Problem → Agitation → Solution) — for problem-aware audiences</li><li>Story Bridge (Hero → Problem → Guide → Plan → Action → Success → Failure) — for unaware audiences</li><li>Custom hybrid — for complex products</li></ul>
<ol><li><strong>Define section flow:</strong></li></ol>
<ul><li>Map the complete page from top to bottom</li><li>Each section has: type, headline, subheadline, body copy, CTA, social proof element</li><li>Ensure objection handling is woven in (not just a FAQ at the bottom)</li></ul>
<ol><li><strong>Write all copy:</strong></li></ol>
<ul><li>Headlines: clear, benefit-driven, &lt;12 words (Ogilvy rule from <code>theory/ogilvy-principles.md</code>)</li><li>Body: specific, concrete, no fluff (anti-slop enforcement)</li><li>CTAs: action verb + outcome (never &quot;Submit&quot; or &quot;Click Here&quot;)</li><li>Social proof: real numbers, real names when possible</li><li>Guarantee section: bold, confident, risk-reversal language</li></ul>
<ol><li><strong>Anti-slop check:</strong></li></ol>
<ul><li>Run all copy through <code>brand-voice.yaml</code> anti-slop rules if brand voice is active</li><li>Check for AI-default phrases, generic language, hedging</li></ul>
<ol><li><strong>Generate narrative wireframe:</strong></li></ol>
<ul><li>Create HTML showing page sections in order with copy, but minimal styling</li><li>Save to <code>previews/phase-5-narrative.html</code></li></ul>
<ol><li><strong>Wait for approval.</strong></li></ol>
<hr>
<h2>Phase 6: Fusion</h2>
<p><strong>Goal:</strong> Merge visual design (Phase 4) + narrative (Phase 5) into a unified mockup.</p>
<p><strong>Process:</strong></p>
<ol><li><strong>Apply design tokens to narrative sections:</strong></li></ol>
<ul><li>Map each section type to its visual treatment</li><li>Resolve conflicts (e.g., long copy vs. minimal design — which wins?)</li><li>Document resolution decisions</li></ul>
<ol><li><strong>Generate styled mockup:</strong></li></ol>
<ul><li>Full page with real copy + real design</li><li>Not fully interactive yet (no animations, no JS)</li><li>But visually representative of the final output</li><li>Save to <code>previews/phase-6-fusion.html</code></li></ul>
<ol><li><strong>This is the critical review point.</strong> User sees the page before engineering begins.</li></ol>
<hr>
<h2>Phase 7: Build</h2>
<p><strong>Goal:</strong> Develop the production-ready page.</p>
<p><strong>Output:</strong> Single-file HTML with embedded CSS and minimal JS.</p>
<p><strong>Technical Requirements:</strong></p>
<ol><li><strong>Performance:</strong></li></ol>
<ul><li>Target &lt;200KB total file size (with inline assets)</li><li>LCP &lt; 2.5s</li><li>CLS &lt; 0.1</li><li>Semantic HTML5</li><li><code>prefers-reduced-motion</code> respected for all animations</li></ul>
<ol><li><strong>SEO:</strong></li></ol>
<ul><li>Title tag, meta description, Open Graph tags</li><li>Structured data (Product, FAQ, or Organization schema)</li><li>Semantic heading hierarchy (single H1)</li><li>Image alt texts</li></ul>
<ol><li><strong>Accessibility:</strong></li></ol>
<ul><li>WCAG 2.1 AA minimum</li><li>Focus states on all interactive elements</li><li>Skip navigation link</li><li>Sufficient color contrast (4.5:1 text, 3:1 large text)</li></ul>
<ol><li><strong>Responsive:</strong></li></ol>
<ul><li>Mobile-first</li><li>Fluid typography using clamp()</li><li>Flexible layout using CSS Grid/Flexbox</li><li>Touch-friendly targets (48px minimum)</li></ul>
<ol><li><strong>Animation (based on Phase 4 selection):</strong></li></ol>
<ul><li>CSS scroll-driven: use <code>animation-timeline: scroll()</code> / <code>view()</code></li><li>Canvas frame sequence: implement per <code>references/techniques/canvas-frame-sequence.md</code></li><li>Micro-interactions: hover states, button feedback, section reveals</li><li>All animations GPU-accelerated (transform + opacity only)</li></ul>
<ol><li><strong>Save final page</strong> to <code>output/sales-pages/{slug}/index.html</code></li><li><strong>Save preview</strong> to <code>previews/phase-7-build.html</code></li></ol>
<hr>
<h2>Phase 8: QA</h2>
<p><strong>Goal:</strong> Validate the built page for quality, performance, and correctness.</p>
<p><strong>Checks:</strong></p>
<ol><li><strong>Playwright E2E tests:</strong></li></ol>
<ul><li>Page loads without errors</li><li>All links work</li><li>CTA buttons are clickable and visible</li><li>Responsive: test at 375px, 768px, 1024px, 1440px</li><li>Scroll animations fire correctly</li><li>No console errors</li></ul>
<ol><li><strong>Visual regression:</strong></li></ol>
<ul><li>Screenshot at each viewport</li><li>Compare sections against fusion mockup (Phase 6)</li></ul>
<ol><li><strong>Performance audit:</strong></li></ol>
<ul><li>Lighthouse score (target 90+)</li><li>Core Web Vitals check</li><li>File size check</li></ul>
<ol><li><strong>Content check:</strong></li></ol>
<ul><li>All copy matches Phase 5 approved copy</li><li>No placeholder text</li><li>No broken images/SVGs</li></ul>
<ol><li><strong>Generate QA report:</strong></li></ol>
<ul><li>Create HTML report with screenshots, scores, pass/fail per check</li><li>Save to <code>previews/phase-8-qa.html</code></li></ul>
<ol><li><strong>Verdict:</strong></li></ol>
<ul><li>PASS → Mark project complete</li><li>CONCERNS → Note issues, user decides</li><li>FAIL → Loop back to Phase 7 for fixes (max 3 iterations)</li></ul>
<hr>
<h2>RLHF Loop</h2>
<p>After Phase 8 completion:</p>
<ol><li><strong>Ask user for overall rating</strong> (1-5)</li><li><strong>If approved:</strong></li></ol>
<ul><li>Save design decisions to <code>reference/design-intelligence/approved/APPROVED-DESIGNS.md</code></li><li>Update <code>STYLE-PROFILE.md</code> with learned preferences</li></ul>
<ol><li><strong>If rejected:</strong></li></ol>
<ul><li>Save rejection reasons to <code>reference/design-intelligence/anti-patterns/REJECTED-DESIGNS.md</code></li><li>Update <code>STYLE-PROFILE.md</code> with anti-preferences</li></ul>
<ol><li><strong>The design intelligence base grows with every project.</strong></li></ol>
<hr>
<h2>Quick Reference: File Paths</h2>
<p>| Resource | Path | |----------|------| | Skill definition | <code>skills/sales-page/SKILL.md</code> | | Pipeline state schema | <code>reference/templates/sales-pages/_PIPELINE-STATE.md</code> | | Product knowledge schema | <code>reference/voice/offers/_SCHEMA.md</code> | | Design doctrine | <code>reference/design-intelligence/DESIGN-DOCTRINE.md</code> | | Anti-slop visual | <code>reference/design-intelligence/anti-patterns/AI-SLOP.md</code> | | Style RLHF profile | <code>reference/design-intelligence/approved/STYLE-PROFILE.md</code> | | Preview server | <code>sales-page-preview/server.py</code> (port 8061) | | Project output | <code>output/sales-pages/{slug}/</code> | | Phase previews | <code>output/sales-pages/{slug}/previews/</code> |</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/sales-page.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>