Landing Website Standards Knowledge Modules

Structure decisions for pages that convert — one goal and one action, message match to the arriving traffic, the canonical narrative order, floor-level form friction, sourced claims — held as gates and recorded decisions rather than essays. The module's operational core is the acceptance bar: references/acceptance.md defines AC1–AC5, the checks every generated page is judged against, versioned with this skill and not with any run. Boundaries: conversion statistics and traffic economics stay in marketing (marketing/landing-pages); copy stays in writing; visual and interaction craft stays in design-ux. Content passes for this module (doctrine, checklists, evidence) land later and raise confidence; until then, the gate and the role playbooks are the module. The YAMLs live in the shared operational catalog agents/ops/ (where the default-pack sync registers workflows); this module defines their contract. Both anchor on the portal goal URL ({{goal_url}}) — no ticket exists at these phases. The scope job resolves the type's seven gates (user inputs → workspace context → platform floor) and publishes them together with brand-extract.md + gate-report.md; the calls job turns the gates' open ends into decision calls, every option in the open with a recommended default. Neither creates issues nor dispatches work: locking the calls is what creates the epics and tasks.

The design skill of the landing playbook: it carries the design role and defines the three-step chain that takes approved requirements to the mock the approval gate reviews (workflow YAMLs live in the shared agents/ops/ catalog, where the default-pack sync registers them). Craft content (layout patterns, type/spacing/color systems, interaction states, accessibility floors) lands later through research passes and raises confidence; the structure below is what jobs run on today. Mocks are grayscale low-fi until the brand gate approves an identity — real headlines, labelled placeholders, one primary CTA — and are judged against the acceptance bar in best-practices/references/acceptance.md plus the operational rules stated inside each workflow's prompt. Steps chain through ticket comments; the previous step's summary rides {{hint}}. The design step attaches the artifacts (wireframe-v1.svg/.html + copy-skeleton.md) and reports the AC1–AC5 self-check in its resolution message. The site repo carries the catalogs (src/templates/manifest.json, src/components/manifest.json); this module carries the contracts for using them. Selection is data-driven: the status: available set is pickable, and planned wants route through the SE step. Brand values come from the account's context (sidebutton-system/landing-website structure, brand section) — with a resolved brand source the mock is branded (token values, fonts, voice); grayscale remains the fallback for a goal whose intake carries no brand source.