template-page-generator▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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).
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, 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
How to use template-page-generator on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add template-page-generator
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches template-page-generator from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate template-page-generator. Access the skill through slash commands (e.g., /template-page-generator) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★64 reviews- ★★★★★Nia Jain· Dec 20, 2024
template-page-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aarav Wang· Dec 20, 2024
We added template-page-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Omar Haddad· Dec 16, 2024
template-page-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Maya Harris· Dec 12, 2024
Keeps context tight: template-page-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Shikha Mishra· Dec 8, 2024
Keeps context tight: template-page-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Mia Haddad· Dec 8, 2024
Registry listing for template-page-generator matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Aanya Verma· Nov 27, 2024
Useful defaults in template-page-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ishan Wang· Nov 11, 2024
Solid pick for teams standardizing on skills: template-page-generator is focused, and the summary matches what you get after install.
- ★★★★★Maya Flores· Nov 11, 2024
template-page-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Maya Torres· Nov 7, 2024
I recommend template-page-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 64