Aetheria-Labs1/storefront-skills / skills/plan-page
plan-page
VerifiedPlan 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.3 KB |
| agents/openai.yaml | config | 514 B |
| references/offers/offer-stacking.md | markdown | 3.5 KB |
| references/offers/offer-strategy.md | markdown | 9.6 KB |
| references/page-type-guide.md | markdown | 5.7 KB |
| references/plan-page.md | markdown | 9.7 KB |
| references/planning-rules.md | markdown | 5.3 KB |
| references/quiz-authoring.md | markdown | 14.5 KB |
| references/resource-templates.md | markdown | 7.7 KB |
references/offers/offer-strategy.md
View on GitHub# Offer Value Strategy
Explain why this audience should want the offer and consider it worth its
price before choosing page sections. An offer includes the product, outcome,
purchase terms, and supporting experience; a full-price product still needs
a value argument when its promotional offer type is `none`.
Use this method for selling pages, including acquisition pages that lead to
a product rather than directly to checkout. For informational or support
pages, record which strategy fields are not applicable and why. Do not force
a bundle, discount, mechanism story, or commercial pitch onto every page.
This method adapts merchant-supplied practitioner guidance about charging
more. Its tactics are hypotheses, not established outcomes for this store;
the article's revenue anecdotes are not evidence for a forecast or claim.
## 1. Find the customer desire
Read the current products, reviews, audience context, supplied campaign,
support notes, and available analytics first. Use review search for pains,
desired outcomes, alternatives tried, purchase objections, and use context.
Public category discussions can fill language or motivation gaps, even when
the store has reviews; they are not evidence that this product works.
Record the source, date, product or audience, and exact customer language.
Separate observed statements from inferred motivations. Connect a functional
benefit to the emotional outcome only when the evidence supports it, such as
confidence, belonging, relief, convenience, or feeling prepared. Do not force
every purchase into attractiveness, status, safety, or a biological explanation.
If no deeper desire is supported, use the concrete outcome the evidence shows.
For gifts, distinguish what the buyer wants from what the recipient needs.
## 2. Define the outcome and differentiation
Name the outcome, who wants it, and the alternatives they consider. Find a
defensible reason to choose this offer: a better-fitting use case or audience,
useful combination, process, ingredient, material, provenance, or substantiated
product advantage. Explain relevant trade-offs without manufacturing a winner.
Where category research is needed, inspect competing promises and customer
skepticism. Ad volume alone does not establish a market-sophistication stage.
Do not call a product unique, superior, or a new category merely because its
name changed. Preserve the supplied ad's promise and any fixed merchant offer;
propose a new audience or positioning separately when it would change them.
## 3. Explain the mechanism
Distinguish the promised outcome from how the product produces it. Where it
helps the decision, explain the process in three to five plain-language steps,
connecting each relevant feature to its benefit and supporting evidence.
For a routine, explain each component's role, order, and contribution.
A mechanism may be understandable without being unique. If no differentiated
mechanism is substantiated, say so and use a truthful product explanation.
Do not invent science, compatibility, clinical results, or failed-alternative
claims. Renaming or bundling products does not establish scientific novelty.
Technical names without a shopper benefit do not earn a mechanism section.
## 4. Build the minimum complete solution
Ask what else the shopper needs to achieve the outcome. Consider complementary
products, usage guidance, services, community access, or digital bonuses only
when they remove a relevant obstacle. Record each component's job, compatibility
where needed, availability, delivery or access method, and confirmed terms.
A named routine or kit should explain the outcome, not imply guaranteed results.
Distinguish a complementary bundle from multiples of one SKU. Quantity tiers
need a credible usage or replenishment reason. Keep a single product when it
already solves the job; do not add low-value items to inflate perceived savings.
New products, services, bonuses, or fulfillment arrangements remain proposals
until confirmed. Digital products can have production, licensing, fulfillment,
and support costs; never assume they have zero cost or 100 percent margin.
## 5. Make value and price understandable
Before proposing a discount, consider better usefulness, convenience, guidance,
proof, or risk reduction. A discount can still fit an evidenced price objection
or an existing campaign. Do not change merchant-controlled prices or promises
as a side effect of page planning.
Show what is included, who it suits, and why each part matters. Anchor against
genuine component selling prices or an otherwise verified comparison basis;
never invent a "worth" figure for a bonus. Use transparent total, unit, or
cost-per-use figures only when their inputs are verified. Consider two or
three meaningful options when comparison helps; one option is also valid.
Preserve existing rules against preselecting multipacks, paid add-ons, or
subscriptions. Retain the existing promotional tier-badge and ribbon rules;
this method grants no exception for "MOST POPULAR" or "BEST VALUE" treatments.
Record known product, gift, shipping, fulfillment, and other variable costs
from merchant evidence when assessing economics. A higher AOV does not by
itself establish higher profit. Unknown costs limit profitability conclusions;
they do not block a valid existing offer. Unconfirmed commercial alternatives
belong in Open decisions and never in final customer-facing copy.
Tie the visual direction and asset jobs to the price position: show actual
materials, construction, included items, packaging, or use context that makes
the value understandable. Preserve real product identity. Polished imagery
does not substitute for evidence or justify a promised conversion lift.
## 6. Map proof and objections to the page
Identify the largest objections and the evidence or policy that answers each.
Place sourced customer proof, demonstrations, expert evidence, and genuine
guarantee terms beside the relevant claim or purchase decision. Give major
objections a distinct section when needed rather than burying them all in FAQs.
Use urgency only for a verified deadline or live availability.
After selecting the page type, map the argument to section IDs, final copy,
proof and offer rows, and asset requirements. For campaign traffic, carry the
supported promise and mechanism from the supplied ad through the page and
purchase explanation. Respect existing disclosure and comparison rules.
These are rationale fields, not seven mandatory page sections; merge repeated
decision jobs and preserve the appropriate narrative for the visitor's awareness.
## 7. Plan a test and review signals
Choose one uncertainty to test: positioning, mechanism explanation, composition,
presentation, or actual price. Record the control, intended difference, audience,
primary metric, guardrails, and stopping rule or measurement gaps. A price
increase is a hypothesis, not an automatic next step after a redesign.
For price or offer economics, default to revenue per visitor (`rpv`) with
conversion (`cvr`) and AOV as supporting measures. Review contribution margin,
refunds, or retention when merchant data makes them available; these are not
assumed native experiment metrics. Do not stop at the first CVR decline or
declare victory from AOV alone. Use the experiment's supported statistical
decision and disclose gaps before any recommendation to expand the offer.
An actual price test requires confirmed commerce configuration that honors
each arm's terms from page through cart and checkout. Page copy cannot set
the payable price. If that support is absent, leave the price test as a proposal
and do not build or activate misleading challenger pages. A presentation-only
test must keep payable terms unchanged and be described accordingly.
For existing offers, compare equivalent traffic and periods before diagnosing
fatigue. Check source/device mix, stock, seasonality, tracking, and purchase
friction first. Use sustained deterioration and new customer or competitor
evidence to propose one new angle, audience, component, or explanation.
Record the baseline and review trigger when data exists; otherwise state the
measurement gap. No fixed expiry date or automatic offer rotation is implied.
## Planning handoff
Complete these fields inside Page strategy for new or substantively replanned
selling pages. Cite evidence and planned section IDs where applicable:
| Field | Required decision |
|---|---|
| Desire and evidence | Observed customer language, sources, and any labelled inference; buyer versus recipient when relevant |
| Outcome and differentiation | Audience outcome, alternatives, reason to choose, and supported trade-offs |
| Mechanism | Plain explanation with evidence; three to five steps when useful, or a reason no distinct mechanism is claimed |
| Offer composition and component roles | Included products or services, each job, fulfillment basis, or why one product is enough |
| Value, price rationale, and economics | Confirmed price and anchor basis, value improvements considered, known costs and limits, intended visual position |
| Proof and objection mapping | Major objections, proof/policy rows, planned sections, and supporting asset jobs |
| Test hypothesis and review signals | One proposed test, metric, guardrails, feasibility, review trigger or measurement gaps |
Use "not applicable" with a reason rather than inventing inputs. Keep
unconfirmed alternatives in Open decisions; a material unresolved choice in
the selected offer blocks approval, but an optional alternative does not.
The Proof ledger, Offer ledger, and Claim gate remain the authority for what
can appear in final copy. Strategy completion authorizes neither commercial
changes nor asset spending, page creation, or live experimentation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |