seo-growth

Router skill. Resolve topic, then Read EXACTLY ONE playbook from routes:. Never load the whole cluster — one topic, one file. [DOC]

Inputs / Outputs

• In: topic (one enum), depth (quick|deep), the growth goal + any URL/page/funnel context. Route to the narrowest topic the request names. [INFERENCE]
• Out: the single playbook's deliverable. quick → essentials; deep → apply exhaustively with verification at each step. [DOC]

Topic disambiguation [INFERENCE]

• landing-page-builder = build a new page end-to-end; landing-pages = patterns/critique for existing pages.
• seo-architecture = structure/indexing/internal links; seo-content = on-page copy/keywords; indexability-validator = audit crawl/index status.
• conversion-optimization = CRO experiments on a page; funnel-design = multi-step journey; social-proof = trust elements.

Spine

Discover → Analyze → Execute → Validate. Don't skip Validate even on quick. [DOC]

Quality gates [DOC]

Constitution v6.0.0 enforcement; evidence tags (Alfa core set, single family); script-first rule (prefer a script over manual steps). Routing + acceptance rubric and signal→topic matrix live in assets/ (see assets/README.md).

Acceptance (route is correct when)

• Exactly one playbook Read; topic matches an enum verbatim. [DOC]
• Deliverable matches the playbook's contract; gates satisfied. [DOC]

Anti-patterns / self-correction [INFERENCE]

• Reading multiple playbooks "to be safe" — pick one or ask once.
• Inventing metrics/traffic figures: tag derived numbers, never fabricate.
• Request spans 2+ topics or topic is ambiguous → ask, don't guess. Missing playbook for the resolved topic → stop and report.