System Context Skill Pack Files

Landing Website Context — Structure

The workspace arm for the landing website goal type: the sections an account's context is organised into, and how each phase consumes them. Scope resolves gates 1–4 from these sections; Design reads §1 to brand the mock; Build reads §4/§6/§7. Values come from the sources ladder — intake first, then workspace extraction (repos and published sites, read live), then the platform floor where one exists.

1 · Brand identity & voice

Slot	What it states
Identity color(s)	The brand palette and what each color is for
Conversion accent	The color reserved for the primary action, if the brand designates one
Token source of truth	The file that defines the design tokens, and the gate that enforces them
Marks / wordmark	Which brand assets exist, where, and their usage rules — a missing wordmark is stated, not assumed
Fonts	The brand faces, how they are hosted, loading rules
Voice source + rules	The canonical copy source (usually the live site) and the observable voice rules extracted from it
Theme	Light/dark posture for landing pages

Consumption: a resolved brand section is the brand-identity gate's answer — the design step produces a branded mock from it (token values, brand faces, voice-checked headings). Grayscale is the fallback for a goal whose intake carries no brand source.

2 · Offer & conversion

Slot	What it states
Primary action per traffic temperature	What warm and cold arrivals are asked to do, and when each applies
CTA label + destination	The action's wording and where it leads — ideally the destination page's own heading, so the click has no seam
Success events	What fires where when the action completes (on-page leading indicator vs the conversion itself)
Friction reducers	The risk-removal line that rides beside the action
Exclusivity	One action page-wide; competing actions the page must not carry

3 · Claims & proof

The claims registry: every claim the account's pages may make — statement, qualifier attached inline, source. Plus the not-claimable list: the claim classes with no source, stated explicitly so they become labelled placeholders rather than invented numbers. Same discipline as the acceptance bar's claims trace: unsourced = not on the page.

4 · Assets

Two tables. Available: asset, path, dimensions/weight — verified on disk, so the design step can label media slots precisely. Awaited: the named asset each placeholder waits for. An asset class that is deliberately out (e.g. a logo strip with no logos) is recorded as decided-out, not awaited.

5 · Legal & compliance

Slot	What it states
Required pages/links	The legal pages every page links, and from where
Held items	Facts only the account owner can supply — each with its owner and which phase it gates (typically go-live, never design)
Staging posture	Index/noindex policy before go-live
Consent posture	Whether pages set cookies and what that means for banners

6 · Analytics & measurement

Slot	What it states
On-page analytics	The stack, and the provisioning rule — provision before build when ids are baked in at build time
Events	The named events per action
Ad/conversion ids	Where the paid conversion fires (often the destination page, not the landing page)
Click-id continuity	How ad click ids survive the page transition

7 · Site repo & deploy

Slot	What it states
Site repo	Where pages live, one page = one file, the component/template manifests
Quality gates	The commands CI runs; what a page must pass
Hosting	The platform floor (subdomain pattern) and any account domains
Go-live	Who flips a page live; pages never set it themselves

8 · Gate ladder

Gate	Answered by	Typical residual user input
conversion-goal	§2	Only when the brief overrides the default action
audience-offer	§2 + the goal's brief	Audience specifics beyond the brief = named gap
brand-identity	§1	None once a brand source exists; grayscale on explicit override
content-media	§3 + §4	New claims need new sources
domain-hosting	§7 + platform floor	Custom domains
legal-compliance	§5 + platform floor	The held items, at go-live
analytics-tracking	§6 + platform floor	Extra trackers