jaygptpro/amazon-pro-skills

amz-storefront-design

>- Plan an Amazon Brand Store. designs the page structure, the navigation, the shoppable content, and the traffic plan so the Store works as a real branded destination, not a dead page. Use when a user asks about the Amazon Store, Brand Store, storefront design, store pages, shoppable images, or driving traffic to a store. Trigger phrases: "amazon store", "brand store", "storefront", "store design", "store pages", "shoppable images", "store traffic". Works with zero tools.

First seen May 24, 2026

Installation

$ npx skills add jaygptpro/amazon-pro-skills --skill amz-storefront-design

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from jaygptpro/amazon-pro-skills · top by installs.

npx skills add jaygptpro/amazon-pro-skills

Browse all from jaygptpro/amazon-pro-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 9
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0
More metadata
author
Jay GPT Pro
library
amazon-pro-skills
version
1.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,807 B
  • docs SUMMARY.md 503 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 107 installs

SKILL.md

Storefront Designer

The Amazon Brand Store is a free, multi-page brand site inside Amazon. Most brands build one, never send traffic to it, and forget it. A Store earns its keep only when it is designed as a destination and fed with traffic. This skill plans both.

When to use this

  • A brand is building its first Amazon Store.
  • A Store exists but gets no traffic and produces no sales.
  • A brand wants a landing page for Sponsored Brands ads.
  • A catalog has grown and the Store no longer reflects it.

The framework. The Store as a Destination

A Store has one job: take a shopper who is interested in the brand and move them across the catalog. Design it in three layers.

Layer 1. The home page

The first screen answers "what is this brand and why care", then routes. It needs a brand hero (one image, one promise), and clear navigation to the rest of the Store. Not a wall of every product. a hero and a set of doors.

Layer 2. The category and collection pages

One page per product family or per use case or audience. A shopper who came in for one thing browses the family. This is where the cross-sell happens. Each page is curated, not a dump of every SKU.

Layer 3. The shoppable content

Shoppable images and lifestyle content where a shopper clicks a scene and buys the products in it. This is the Store's advantage over a plain search result. use it. Featured deals modules, best-seller modules, and new-arrival modules keep the Store fresh and give returning visitors a reason to look.

The traffic plan. the part everyone skips

A beautiful Store with no traffic produces nothing. Plan the feeds:

  • Sponsored Brands ads can land on the Store instead of a product page. this is

the biggest controllable feed. Two SB creatives serve different jobs and route differently. use the right one or the Store stays dead. - Store Spotlight creative routes the click to the Store landing page (the home or a specified Store sub-page). This is the creative to use when the goal is driving Store traffic, surfacing the brand across the catalog, and cross-selling beyond the lead ASIN. - Product Collection creative routes the click to an ASIN detail page. This is the creative for direct-conversion campaigns on a specific product. it does not drive Store traffic. - Rule of thumb. If the campaign goal is "build the brand and cross-sell", Store Spotlight. If the goal is "win the unit on this specific keyword", Product Collection. Do not use Product Collection on brand or category keywords expecting Store traffic. it will not happen.

  • The brand byline on every listing links to the Store.
  • Posts and external traffic (social, email, influencers) should point at the

Store, not a single listing, so the visitor sees the whole brand.

  • A Store also gives a clean Store Insights view of which pages and sources work.

Step by step

  1. Collect inputs. The brand, the catalog and how it groups (families, use cases,

audiences), the brand promise, and the current traffic sources.

  1. Design the home page. The brand hero and the navigation. Define the doors.
  1. Design the category and collection pages. One per family or use case. Curate

each. Decide which pages also serve as Sponsored Brands landing pages.

  1. Plan the shoppable content. Which lifestyle scenes become shoppable, and which

dynamic modules (deals, best sellers, new arrivals) keep the Store fresh.

  1. Build the traffic plan. Sponsored Brands to the Store, the brand byline,

external traffic pointed at the Store. Name the primary feed.

  1. Set the review cadence. A Store is not set-and-forget. seasonal refreshes and

new-product additions.

  1. Run the quality check, then deliver.

Output format

## Store Plan. [brand]

### Home page
Brand hero: [image and promise direction]
Navigation: [the doors]

### Category and collection pages
[page] . [what it groups] . [SB landing page? y/n]
...

### Shoppable content
Shoppable scenes: ...
Dynamic modules: [deals / best sellers / new arrivals]

### Traffic plan
Primary feed: [usually Sponsored Brands]
Other feeds: [byline, external]

### Refresh cadence
[seasonal and new-product cadence]

Worked example

A coffee brand with beans, equipment, and accessories.

Home page: a brand hero on the sourcing story, and three doors. Coffee, Brewing Gear, Accessories. Category pages: one per door, curated. The Coffee page doubles as the Sponsored Brands landing page for coffee keyword campaigns, so an ad for "single origin coffee" lands on the whole coffee range, not one bag. Shoppable content: a morning-routine lifestyle scene where the shopper clicks the grinder, the beans, and the mug. Traffic plan: Sponsored Brands as the primary feed, the brand byline on every listing, and the brand's social pointed at the Store home, not at one product.

Quality check

  • The home page is a hero plus navigation, not a dump of every product.
  • Category pages are curated by family, use case, or audience.
  • At least one page is designated a Sponsored Brands landing page.
  • Shoppable content and dynamic modules are planned, not just static grids.
  • A traffic plan exists and names the primary feed. a Store without traffic is dead.
  • A refresh cadence is set.

Common mistakes

  • Build it and forget it. A Store with no traffic plan produces nothing.
  • A product dump. Every SKU on one page with no curation and no story.
  • No Sponsored Brands landing. Running brand ads to a product page instead of the

Store, wasting the Store's whole reason to exist.

  • Static and stale. No dynamic modules, no seasonal refresh, so returning

visitors see the same page forever.

  • Pointing external traffic at one listing. Sending social and email to a single

product instead of the brand destination.


Built by Jay GPT Pro

Part of Amazon Pro Skills. Production-grade skills for serious Amazon sellers. Free and open. Built by Jay Margaliot.

I share a new AI play for Amazon sellers every week, free, in my WhatsApp group. Join here: https://chat.whatsapp.com/ILX65p1yWcaIG3c9WGHpTY