Skip to content

Aetheria-Labs1/storefront-skills / skills/plan-page

plan-page

Verified

Plan one storefront page from strategy through final copy, section order, proof, offers, template direction, responsive layout, and production asset requirements. Stops at an approved execution-ready specification.

references/planning-rules.md

View on GitHub
# Page Planning Rules

Use these rules while producing the plan. Brand guidance may specialize them;
merchant rules and verified legal constraints always win.

## Consumer Decisions

Classify the primary visitor mode:

- `confirm`: validate a product already chosen;
- `compare`: distinguish variants, products, or alternatives;
- `explore`: learn the category or mechanism;
- `complete`: assemble a bundle, routine, look, or room;
- `replenish`: reorder or subscribe with minimal friction.

Write the three to five questions that block the desired action. Order sections
so each question is answered once. Put risk, proof, compatibility, delivery,
returns, and price close to the decision they affect.

Use at most three behavioural patterns, each tied to evidence in the brief,
catalog, reviews, analytics, or persona context. Do not add carousels,
recommendations, quizzes, urgency, or sticky controls without a decision job.

## Copy

- Finalize all customer-facing copy in the plan.
- Use one clear promise and one primary CTA verb.
- Headlines state a concrete product, problem, outcome, or choice.
- CTA labels name the actual action and destination.
- Use shopper language from verified reviews without fabricating quotations.
- Keep claims within catalog facts, merchant evidence, and public sources.
- Give FAQs complete, direct answers.
- Avoid placeholder copy, generic superlatives, stacked slogans, and repeated
  sections that say the same thing.
- Keep locale, spelling, currency, units, and policy language consistent with
  the selected market.

For supplied campaign traffic, preserve its product, variant, noun phrase,
promise, offer, CTA verb, tone, audience, and visual cue. The page may narrow
or substantiate a promise; it may not silently enlarge it.

## Proof and Claims

- Reviews require a live review source, exact text, attribution, and date.
- Ratings and counts use one source and one as-of date across the page.
- Customer imagery and UGC require usage rights.
- Results and before/after content require genuine matched evidence, consent,
  timeframe, and typicality context.
- Press, awards, certifications, payment marks, and partner logos require an
  official source.
- Study or expert claims identify the source, scope, date, and limitations.
- Unsupported claims receive safe final copy or are removed.
- Missing reviews are not replaced with invented testimonials, stars, counts,
  or synthetic customers.

## Offers

For selling pages, before choosing sections or finalizing copy, follow
`references/offers/offer-strategy.md` and complete the value-strategy fields in
Page strategy. This applies to full-price selling pages as well as promotions.
Consider useful value improvements before discounts and preserve fixed merchant
offers and campaign promises. Alternative terms remain proposals until confirmed.
Retain existing selection and promotional tier-badge rules.

Record exact price, compare-at basis, discount, code or automatic mechanic,
eligibility, region, start/end, gift, shipping threshold, stock basis,
subscription cadence, cancellation, pre-order delivery, guarantee, and return
terms as applicable.

Urgency appears only with a real dated deadline or live inventory source.
Savings arithmetic must reproduce from ledgered prices. Never infer a free
gift, discount, delivery promise, scarcity statement, or guarantee.

## Visual Direction

- Use the selected theme tokens and brand typography character.
- Define one visual thesis, one background system, and one bold moment.
- Prefer a clear grid, deliberate asymmetry, or editorial composition over
  repeated generic cards.
- Keep text legible without relying on image-generated typography.
- Reserve quiet zones for HTML copy.
- Treat mobile as a recomposed hierarchy, not a shrunken desktop.
- Specify motion only when it explains state, sequence, or emphasis.
- Product identity, proof, official marks, and customer evidence stay real.

## Asset Requirements

Each planned slot states:

- the consumer decision it supports;
- exact product/variant identity when applicable;
- `real-only`, `editable-real`, or `generation-permitted`;
- mobile aspect, crop, focal point, and minimum pixel target first;
- larger-screen aspect, crop, minimum pixel target, and whether it derives
  from the same master;
- subject, composition, focal point, quiet zone, palette, and set continuity;
- evidence, rights, or provenance required.

Planning may identify catalog product media, but `/plan-assets` owns library
search, inspection, selection, import, upload, generation, persistence,
credits, and final binding.

## Template Choice

Sections and final copy come first. Search page kits by type, vertical, mood,
and objective. A selected kit may guide layout but may not delete required
consumer decisions or alter claims and offer terms. Search individual
sections only for planned jobs. Use a custom direction when no fit exists.

## Research and Uncertainty

- Ask the user for merchant-controlled choices, private facts, campaign
  intent, rights, approvals, and conflicting evidence.
- Use authoritative web research for public policy, certification, occasion,
  regulatory, market, or factual questions when the answer is unclear.
- Record source and access date.
- Mark material uncertainty `PLAN_BLOCKED`.
- Keep lesser uncertainty in `## Open decisions` with an owner and effect.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall