agentsclimarketplace

Template page generator

Skill bg-szy/TOP-SKILLS/skills/superskills/template-page-generator

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.From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill template-page-generator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

7.1 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it

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

TypePurposeExamples
Template aggregation pageGallery, hub, category; list templates for browse and filterCanva /templates, Figma templates, VibeCatalog /templates, uitovibe theme gallery
Template detail pageIndividual template; preview, description, "Use this template" CTASingle 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:

DomainFlowExamples
CMSBrowse templates → Select → Create page/post from templateWordPress themes, Webflow templates, Notion templates
Design / ImagesBrowse → Preview → Customize in editorCanva (Customize this template), Figma (Duplicate to your drafts)
Website buildersBrowse → Select → Customize (colors, fonts, content) → DeployVibeCatalog, Lovable, Bolt.new, v0; dashboard, landing page, SaaS templates
Vibe codingBrowse UI themes → Copy style instructions → Add to AI prompt → Generateuitovibe (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)

SectionPurpose
Headline"Templates for [category]" or "Browse [X] templates"
Filters / CategoriesBy type (dashboard, landing page, resume), platform (Bolt, Lovable, Next.js), use case
Template cardsThumbnail, name, short description, "Use" or "Preview" CTA; grid or list
SearchBy keyword, tag
Social proof"X templates," "Used by Y users," ratings
CTAPrimary 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)

SectionPurpose
HeroTemplate name, one-line benefit; primary CTA: "Use this template" / "Customize" / "Copy"
PreviewLive preview, screenshot, or interactive demo; multiple views (desktop, mobile)
DescriptionWhat it does, who it's for, what's included
Features / What's includedComponents, sections, customization options (colors, fonts, layouts)
How to useSteps: Copy → Paste in editor / Open in [tool] → Customize
Platform compatibilityBolt, Lovable, v0, Next.js, React, etc.
FAQ"Can I use commercially?", "Do I get source code?", "How do I customize?"
Related templatesInternal 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:

SectionPurposeData Slot
IntroH1, intro; matches intent{entity_name}, {context}
Evidence blockTables, lists, verified data; avoids thin content{data_table}, {list_items}
DecisionRecommendation, next steps{recommendation}
FAQSchema-friendly Q&A{faq_items}
CTAConversion{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

DomainAggregationDetailUse Flow
Design (Canva, Figma)Category browse, filtersPreview, "Customize"Open in editor, drag-and-drop
Vibe coding (uitovibe, VibeCatalog)Theme gallery, by styleCopy instructions, "Add to prompt"Paste into Bolt/Lovable/Cursor
Website (Lovable, Bolt, v0)By project typeLive demo, "Use template"Clone, customize, deploy
CMSBy content typePreview, "Create from template"New page/post from template
Programmatic SEON/A (data-driven)Output pages from template + dataInformational; 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, SoftwareApplication for detail)

Related Skills

  • card: Template card structure; thumbnail, name, description, CTA; grid layout
  • grid: Template grid layout; responsive columns
  • programmatic-seo: Template + data = scale; use cases, data requirements, pitfalls
  • landing-page-generator: Conversion structure; programmatic landing pages
  • tools-page-generator: Tool pages at scale; toolkit hub
  • alternatives-page-generator: Alternatives/comparison at scale
  • category-page-generator: Category structure; similar to template aggregation
  • schema-markup: ItemList, CreativeWork, SoftwareApplication
  • url-structure: /templates, /templates/[slug] hierarchy

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most design frontend skills give in ~1.6k tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,758. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.