Aetheria-Labs1/storefront-skills / skills/audit
audit
VerifiedRead-only conversion audit of a whole storefront page. Scores above-the-fold, offer strength, proof, copy, design, mobile and funnel data against the build rules and returns ranked fixes. Never edits; hand approved fixes to /optimize.
references/resource-templates.md
View on GitHub# Resource templates
A resource template is an ordinary Lexsis page (source, CSS, islands) that
renders for many products or many collections. The store serves it at:
- `/a/lp/products/<handle>` and `/a/lp/collections/<handle>` (app proxy);
- `<custom domain>/products/<handle>` and `<custom domain>/collections/<handle>`.
The URL's handle decides which product or collection the page binds to.
Title, canonical URL, meta description and Product or CollectionPage JSON-LD
come from that resource automatically; do not hand-write them per product.
## When to build a template
Build a template, not one page per product, when:
- the layout should apply store-wide or to a whole group: every PDP, every
product in a collection, tag, type or vendor, or every collection page;
- the merchant wants one design maintained in one place as the catalog
changes;
- the layout may be A/B tested later (a route can point at an experiment
whose variants are template pages).
Build a dedicated page when one product or one collection needs its own
story, offer, proof or copy that would be wrong on its siblings (a launch,
a hero SKU with its own ad traffic). A dedicated published page whose handle
equals the resource handle always wins over a template for that URL.
The plan records the scope as `product template`, `collection template` or
a single page, plus the sample handles used for preview.
## Build it
1. Plan and design the page as usual for its type (the pdp or
collection-landing page-type contract).
Copy must read true for every resource the route will cover: no single
product's claim, review quote or offer in shared template text unless it
is bound to the resource.
2. Pass `resource_type: "product"` or `"collection"` (and optionally
`preview_resource_handle`) to `lexsis_pages.compile` and
`lexsis_page_create.create`. To mark an existing draft, use
`lexsis_drafts.set_resource_template` with
`{ page_id, resource_type, preview_resource_handle }`;
`resource_type: null` unmarks it.
3. Bind content to the resource; never hardcode one:
- product islands (BuyBox, ProductGallery, StickyBar, QuickAdd and the
rest) bind to the routed product when `productId` / `product` is
omitted;
- CollectionGrid and CollectionSwipe take `"collection": "$resource"`
(or omit `collection`);
- page text and media bind with the card-template attributes on any
element: `data-lx-product`, `data-lx-product-src`,
`data-lx-product-href`, `data-lx-product-alt`, `data-lx-product-if`,
`data-lx-product-unless`, and the paths `id`, `handle`, `url`, `title`,
`type`, `vendor`, `description`, `price`, `compareAt`, `available`,
`images.N.url`, `images.N.alt`, `metafields.<ns>.<key>`, or
`tag:<tag>` in conditions. They work on product and collection
templates (`title`, `description`, `handle`, `url`,
`images.0.url` resolve to the collection on a collection template).
4. Compile. `resource_template_hardcoded` warns on an island pinned to one
resource; remove the pin unless that island is intentionally fixed (a
cross-sell of one accessory).
## Reviews on product pages
- On a product template, `ReviewList` and `ReviewCarousel` take
`"productIds": "$resource"`; the renderer binds the routed product's id.
A hardcoded `productIds` on a product template warns
`resource_template_hardcoded`. On a single PDP, pass that product's id
in `productIds`.
- On `ReviewList`, omit `averageRating` and `totalReviews`: the star summary
comes from that product's reviews.
- Most products have few or no reviews. What they show instead is a page
setting, not an island prop, so the merchant can change it in the app
(Page templates, "When a product has no reviews"). Never hardcode
`fallbackCollectionId` or `fallbackScope` in props.
- `store` (the default when unset): all of the store's reviews.
- `collection`: one review collection. List them with
`lexsis_catalog.review_collections`; only `active` collections render.
- `none`: the reviews section hides when the product has none.
Ask the user which one they want (default `store`). Set it with
`lexsis_drafts.set_review_fallback`
`{ page_id, type: "store" | "collection" | "none", collection_id? }`,
or pass `review_fallback: { type, collection_id? }` to
`lexsis_page_create.create`.
- ReviewList renders no headings or labels for the fallback. Author every
heading ("Customer reviews", "Loved by <brand> customers", sublines) as
page HTML and toggle it with page CSS on the island root's
`data-reviews-source="product" | "fallback" | "none"`:
```css
.rv-head[data-for] { display: none; }
[data-section-id="reviews"]:has([data-reviews-source="product"]) .rv-head[data-for="product"] { display: block; }
[data-section-id="reviews"]:has([data-reviews-source="fallback"]) .rv-head[data-for="fallback"] { display: block; }
[data-section-id="reviews"]:has([data-reviews-source="none"]) { display: none; }
```
Fallback reviews show no star summary, so store reviews never read as
the product's rating; keep the fallback heading free of a rating too.
- Once loaded, ReviewList also fires a `window` `lx:reviews:state` event
with `{ source: "product" | "fallback" | "none", total, average }` for
section JS, e.g. hiding a buy-box review-stars anchor when the product
has no reviews of its own.
## Preview against sample handles
Preview at `<renderer>/v/<template slug>?preview=1&resource=product:<handle>`
or `resource=collection:<handle>`. `preview_resource_handle` sets the
default. Review two or three different handles chosen to stress the layout:
the longest title, the product with the most variants or images, one with
few images or no reviews, one sold out; for collections, the largest and a
small or filter-poor collection. The hosted design review's template
checks apply to each.
## Publish, then route
Routes skip unpublished or deleted pages, so publish the template first
through `/publish`. Routing moves live traffic and is a live operation:
show the user the exact route and get explicit approval before
`lexsis_live_ops.resource_route_upsert` with
`{ resource_type, match_kind, match_value, priority, page_id | experiment_id, status }`.
| `match_kind` | `match_value` | Applies to |
|---|---|---|
| `default` | empty | every product or every collection without a better match |
| `handle` | one product or collection handle | that one URL (an override) |
| `collection` | collection handle | products in that collection |
| `tag` | tag | products with that tag |
| `product_type` | product type | products of that type |
| `vendor` | vendor | products from that vendor |
`collection`, `tag`, `product_type` and `vendor` rules match products only;
collection templates route with `default` and `handle`. Routes are unique
per store, resource type, kind and value; upserting the same key updates it.
`status: "paused"` keeps a route without serving it.
`lexsis_live_ops.resource_route_delete` with `{ route_id }` removes one.
## Precedence
For a requested handle, the first match wins:
1. a published, non-template page whose handle equals the resource handle;
2. a `handle` route;
3. rule routes (`collection`, `tag`, `product_type`, `vendor`) by
`priority`, lower number first (default 100), then the oldest route;
4. the `default` route;
5. nothing: the URL returns 404.
## Verify
1. `lexsis_pages.resource_routes` lists every route with kind, value,
priority, target and status.
2. `lexsis_pages.resolve_resource` with `{ resource_type, handle }` is a dry
run: it returns the page or experiment that would serve the handle and
why (`page`, `handle`, `rule` or `default`), or that the URL would 404.
3. Resolve the sample handles plus one handle each rule should not catch,
before and after the upsert, and open the live URL for at least one.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |