Landing Website Standards Skill Pack Files

Landing Website Standards

Skill scaffolding for landing website creation — the structures, roles, and gates the "SideButton Landing Website with Design" goal type and its playbooks run on. Deliberately structure-first: modules carry headers, role wiring, and gates; craft content lands later through research passes and raises confidence per file as it does.

A job loads a module plus the _roles/<role>.md playbook for its own role — never the whole pack — and is judged by the gates: the acceptance bar in best-practices and the verdict vocabularies of the design playbook's workflows.

Modules

Module	Display name	Carries	Role playbooks
best-practices	Conversion Best Practices	Conversion-structure rules held as gates; the acceptance bar references/acceptance.md (AC1–AC5); defines the goal-phase scope/decide workflows	pm · se · qa
design-ux	Design, UI and UX Practices	The design role and the three-step design playbook's contract	design · pm · se · qa
seo	SEO and Search Visibility	Planned (Phase 2): intent match, schema blocks, CWV budgets, measurement events	—

The workflow YAMLs themselves live in the shared operational catalog agents/ops/ — the one directory the default-pack sync registers workflows from, and the scope of the clear-set parity check. This pack holds their contracts, roles and gates; the tables below are the reference.

Goal Phases (Scope · Decide)

Phase	Workflow	Role	Verdicts (gate)
Scope	agent_pm_landing_scope — Align Scope Gates	pm	GATES_ALIGNED · NEEDS_INPUTS
Decide	agent_pm_landing_calls — Prepare the Calls	pm	NEEDS_DECISIONS · NO_CHANGE

These two anchor on {{goal_url}} — the portal goal, not a ticket: no issue exists at these phases, and locking the decide phase's calls is what creates the epics and tasks. The scope job publishes the type's seven gates together as its result; the calls job turns their open ends into decisions with recommended defaults.

The Design Playbook

Step	Workflow	Role	Verdicts (gate)
1	agent_pm_wireframe — Gather Wireframe Requirements	pm	REQUIREMENTS_READY · NEEDS_INPUT
2	agent_se_design_check — Check Design Dependencies	se	DEPS_CLEAR · BLOCKERS_FOUND
3	agent_design_assemble — Assemble & Publish Mock	design	MOCK_READY · NEEDS_INPUT

Ticket-anchored and chained through comments — the previous step's summary rides {{hint}}, and each prompt closes with a VERDICT line naming exactly its tokens, which is what playbook gates route on. The design step attaches the mock artifacts (wireframe-v1.svg/.html + copy-skeleton.md) and reports the AC1–AC5 self-check in its resolution message.

Gates

Gate	Where	Read by
Acceptance bar AC1–AC5	best-practices/references/acceptance.md — versioned with the skill, not the run	design self-check → QA re-check → operator approval
Step verdicts	metadata.verdicts of each workflow above	Playbook gate routing (pass / pause / rework)

Boundaries

Conversion statistics and traffic economics: marketing (marketing/landing-pages). Copy: writing. Brand identity and account facts (site repo, deploy, domains, analytics, sign-offs): the consumer's brand-context.md and the account's private system skill — never a public pack.

Loading Order

1. This file — structure and boundaries
2. brand-context.md / account system skill — identity and constraints
3. _roles/<role>.md of the module being worked
4. The module _skill.md
5. best-practices/references/acceptance.md whenever a deliverable will be judged