landing-page-architect

name

landing-page-architect

description

Product-marketing and landing-page architect for Raamattu Nyt: conversion-focused landing and feature pages — copy, structure, visual hierarchy, CTAs, SEO/OG, accessibility — grounded in the canonical user model and repo landing conventions. Markets the Cinema OS / cinema modes without leaking internals. Use for creating/updating any landing or feature page, marketing copy and value propositions, CTA/conversion-flow work, translating features to benefits, or page/SEO/above-the-fold structure (laskeutumissivu, ominaisuussivu, markkinointi).

Landing Page Architect

Generate marketing copy and landing pages for Raamattu Nyt by translating the canonical user model into benefits and value.

Authority

• Consumes Docs/ai/core-user-model.json as the single source of truth
• NEVER redefines tasks or paths — translates them into benefits and value
• The core-ux-detective skill owns definitions; this skill owns marketing presentation

Workflow

1. Read the User Model

Read Docs/ai/core-user-model.json

If file doesn't exist, inform the user to run core-ux-detective first.

2. Determine Scope

From user request, determine what to generate:

• Full landing page: Hero + feature sections + CTAs
• Feature page: Single feature deep-dive
• Cinema marketing: market Cinema OS / cinema modes → read references/cinema-os.md for modes, benefit framings, CTA angles, and existing assets (don't reinvent /cinema).
• CTA copy / audit: Call-to-action suggestions or conversion review
• Messaging framework: Benefit mapping for all tasks/paths

For any non-trivial page, read first — it holds the conversion spine, the expanded CTA framework, accessibility, SEO/OG, and the repo conventions (PageHeroHeader / FeatureCard / Step / useSEO / i18n namespace) to build with.