When the user wants to design template pages—aggregation (gallery/hub) or detail (individual template). Also use when the user mentions "template page," "template gallery," "template hub," "template detail page," "template marketplace," "programmatic template," "CMS templates," "design templates," "vibe coding templates," "UI templates," "template for users to use," or "template + data pages." For SEO-at-scale strategy (data-driven URL sets), use programmatic-seo.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
| 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 |
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."
| 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.
| 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."
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.
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.
| 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 |
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
日本語の概要は準備中です。原文の説明を表示しています。
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 create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
日本語の概要は準備中です。原文の説明を表示しています。