template-page-generator
The template-page-generator skill guides design of two page types for template systems: aggregation pages (galleries or hubs where users browse and filter templates) and detail pages (individual template previews with "use" or "customize" calls-to-action). Use this skill when designing pages that let users select templates to generate their own content, such as in CMS platforms, design tools, website builders, or AI-assisted coding environments where templates serve as starting points for customization.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/template-page-generator && cp -r /tmp/template-page-generator/skills/pages/content/template-page ~/.claude/skills/template-page-generatorSKILL.md
# Pages: Template Page
Guides template page design for two distinct use cases: **(1) Programmatic SEO** — template + data = scale; **(2) User-facing templates** — users browse, select, and use templates to generate their own content (CMS, images, websites, vibe coding). See **programmatic-seo** for the scale framework. This skill covers **template aggregation pages** (gallery, hub) and **template detail pages** (individual template with "use" flow).
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
---
## Two Template Page Types
| Type | Purpose | Examples |
|------|---------|----------|
| **Template aggregation page** | Gallery, hub, category; list templates for browse and filter | Canva /templates, Figma templates, VibeCatalog /templates, uitovibe theme gallery |
| **Template detail page** | Individual template; preview, description, **"Use this template"** CTA | Single template page; user clicks to copy, customize, or open in editor |
---
## Core Function: Users Use Templates to Generate Content
Beyond SEO, template pages enable **direct use**: users select a template and generate their own content. Common patterns:
| Domain | Flow | Examples |
|--------|------|----------|
| **CMS** | Browse templates → Select → Create page/post from template | WordPress themes, Webflow templates, Notion templates |
| **Design / Images** | Browse → Preview → Customize in editor | Canva (Customize this template), Figma (Duplicate to your drafts) |
| **Website builders** | Browse → Select → Customize (colors, fonts, content) → Deploy | VibeCatalog, Lovable, Bolt.new, v0; dashboard, landing page, SaaS templates |
| **Vibe coding** | Browse UI themes → Copy style instructions → Add to AI prompt → Generate | uitovibe (copy instructions, paste into Bolt/Lovable/Cursor prompt) |
**Key CTA**: "Use this template," "Customize this template," "Copy to editor," "Get this template," "Start with this."
---
## Template Aggregation Page (Gallery / Hub)
| Section | Purpose |
|---------|---------|
| **Headline** | "Templates for [category]" or "Browse [X] templates" |
| **Filters / Categories** | By type (dashboard, landing page, resume), platform (Bolt, Lovable, Next.js), use case |
| **Template cards** | Thumbnail, name, short description, "Use" or "Preview" CTA; grid or list |
| **Search** | By keyword, tag |
| **Social proof** | "X templates," "Used by Y users," ratings |
| **CTA** | Primary action (Browse, Get started, Sign up to use) |
**Reference**: Canva organizes by 50+ design types (Docs, Presentations, Logos, Instagram Posts, etc.); Figma offers 300+ templates; VibeCatalog by project type (dashboards, landing pages). See **card** for template card structure and grid layout.
---
## Template Detail Page (Individual Template)
| Section | Purpose |
|---------|---------|
| **Hero** | Template name, one-line benefit; **primary CTA: "Use this template" / "Customize" / "Copy"** |
| **Preview** | Live preview, screenshot, or interactive demo; multiple views (desktop, mobile) |
| **Description** | What it does, who it's for, what's included |
| **Features / What's included** | Components, sections, customization options (colors, fonts, layouts) |
| **How to use** | Steps: Copy → Paste in editor / Open in [tool] → Customize |
| **Platform compatibility** | Bolt, Lovable, v0, Next.js, React, etc. |
| **FAQ** | "Can I use commercially?", "Do I get source code?", "How do I customize?" |
| **Related templates** | Internal links to similar templates |
**Vibe coding pattern** (uitovibe, VibeCatalog): Template = style instructions or full code; user copies instructions into AI prompt or downloads/clones to customize. CTA: "Copy instructions," "Add to prompt," "Get template."
---
## Template + Programmatic SEO
When templates are **generated at scale** from data (location pages, integration pages, comparison pages), use **programmatic-seo** framework:
| Section | Purpose | Data Slot |
|---------|---------|-----------|
| **Intro** | H1, intro; matches intent | `{entity_name}`, `{context}` |
| **Evidence block** | Tables, lists, verified data; avoids thin content | `{data_table}`, `{list_items}` |
| **Decision** | Recommendation, next steps | `{recommendation}` |
| **FAQ** | Schema-friendly Q&A | `{faq_items}` |
| **CTA** | Conversion | `{cta_destination}` |
See **programmatic-seo** for data, automation, pitfalls. When programmatic pages have conversion goals, apply **landing-page-generator** principles.
---
## Template + Landing Page (Conversion-Focused Programmatic)
When programmatic pages drive signup/lead capture (e.g., "[Product] for [City]" LPs), apply landing page structure to the template: Stop the scroll → Earn trust → Explain value → Remove doubt → Make the ask. See **landing-page-generator**.
---
## Common Template Patterns by Domain
| Domain | Aggregation | Detail | Use Flow |
|--------|-------------|--------|---------|
| **Design (Canva, Figma)** | Category browse, filters | Preview, "Customize" | Open in editor, drag-and-drop |
| **Vibe coding (uitovibe, VibeCatalog)** | Theme gallery, by style | Copy instructions, "Add to prompt" | Paste into Bolt/Lovable/Cursor |
| **Website (Lovable, Bolt, v0)** | By project type | Live demo, "Use template" | Clone, customize, deploy |
| **CMS** | By content type | Preview, "Create from template" | New page/post from template |
| **Programmatic SEO** | N/A (data-driven) | Output pages from template + data | Informational; CTA to product |
---
## Output Format
- **Page type** (aggregation vs detail)
- **Sections** (per type above)
- **Primary CTA** ("Use this template," "Customize," "Copy instructions")
- **User flow** (browse → preview → use → customize)
- **Programmatic alignment** (if template + data scale)
- **Schema** (ItemList for aggregation; CreativeWork, SoftWhen the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.