landing-page-architect

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).

Zur Installation springen

Repository: Spectaculous-Code/raamattu-nyt
Letzte Quellaktivität: 13. Juli 2026 um 04:26
Erkannte Sprache von SKILL.md: Englisch
Sterne: 0
Forks: 0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/Spectaculous-Code/raamattu-nyt --skill landing-page-architect

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer

7 Dateien

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

docs-updater

Keeps documentation synchronized with code: API/architecture docs, README, CLAUDE.md, the AI index manifest (Docs/ai-index/manifest.yml — domains, task_playbooks, generated catalogues), ASCII flow diagrams, feature/system explanations, and reporting changes to the Obsidian vault. Use when (1) updating or generating docs, (2) updating the AI index / manifest ("ai index", "päivitä manifesti", "add domain/task playbook", "regenerate catalog"), (3) drawing ASCII flow/workflow diagrams ("piirrä kaavio"), (4) explaining how something works ("miten toimii", "selitä arkkitehtuuri"), or (5) reporting to Obsidian ("vault", "raportoi obsidianiin").

2026-08-11

topic-manager

Manage biblical topics in Raamattu Nyt. Use for creating/editing topics + Finnish translations, topic relations (related/opposite/broader/narrower), validating FI translations & pronunciations (Voikko/Omorfi), reviewing qa_status='unchecked', bulk translation updates, aliases/synonyms, fixing mistranslated FI topic names, and the taxonomy tree (parent_id hierarchy, roots, orphans, cycles, re-parenting after merges). ALSO the structured topic schema (`structured_schema`): type templates, claims + sources, the async generation queue (/ohjaamo/topics/generation), draft review, and the Matthew Henry claim-verification pass — plus the PLANNED verse schema generated from Matthew Henry (design lives in Obsidian, not yet in code). ALSO the source corpora behind topic content — which reference work feeds which column, where the local files live (`Docs/data/`), and how to expand ISBE coverage without re-scraping. Triggers: aihe, topic, teema, taksonomia, hierarkia, alias, merge/yhdistäminen, aiheskeema, jae-skeema, str

2026-08-11

verse-topic-tagger

Analyse a Bible verse's topic areas and link verses to topics in Raamattu Nyt (bible_schema.topical_references — the jae↔aihe link table). Use for: (1) tagging a single verse/passage — given a reference, find/assign its topics and insert topical_references; (2) per-book/chapter COVERAGE scans for under-tagged verses; (3) junk/QA CLEANUP of bad references (over-wide range refs, cluster bleed, wrong scope); (4) SOURCE-based rematch from easton_articles / smiths_articles to topical_references. Triggers: "tägää jae", "liitä jae aiheeseen", "jakeen aihealueet", "analysoi jakeen aiheet", "aihekattavuus", "topical_references", "roskaviite", "junk ref", "cluster bleed", "coverage gap", "Easton/Smith rematch", "verse topic tagging". Also owns (5) the VERSE SCHEMA (jae-skeema) — Matthew Henry turned into a structured Finnish exposition per outline point, and the verification of its claims against the bounded English source; triggers: "jae-skeema", "jakeiden skeema", "Matthew Henry", "rakenteinen suomennos", "structured

2026-08-11

Alle aus diesem Repository ansehen

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.

name

landing-page-architect

description