When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.
Guides product listing and category page content for e-commerce. For individual product detail pages, structure varies by platform.
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product catalog and positioning.
Identify:
| Element | Purpose | |---------|---------| | Category title | Clear H1; target keyword | | Description | SEO copy; benefits of category | | Filters | Price, size, brand, etc. | | Product cards | Image, name, price, CTA | | Pagination | Crawlable; rel prev/next |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/products · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/products"
cp -r "skills/pages/marketing/products" ".claude/skills/products"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.