Aetheria-Labs1/storefront-skills / skills/optimize
optimize
FlaggedScore an existing Lexsis page against the same page-type, design, proof, offer, asset and copy rules used to build pages, propose improvements as a strict optimization plan with real replacement copy and asset decisions, wait for approval, then apply the approved changes with version protection and hosted QA.
references/vertical-supplements.md
View on GitHub# Supplements decisions
Choose the page contract through `references/page-types/_index.md`. This
reference retains vertical-specific decision inputs, not section ordering,
static island recipes, offer policy, or another visual system.
## Product decisions
### Label facts
Use the actual ingredient quantities, serving size, directions and warnings. Distinguish amount per serving from amount per container.
### Evidence
Separate ingredient research, formulation evidence and evidence about the sold product. A study of an ingredient does not automatically substantiate a product outcome.
### Suitability
Show relevant restrictions and intended users from the verified label or merchant evidence. Never invent a clinical promise or omit a material limitation to shorten the pitch.
### Image decisions
Prioritize label readability, packaging identity, serving scale and real product detail. Research diagrams illustrate a supported explanation; they do not become proof by appearing scientific.
### Purchase options
Bind pack size, quantity tiers and selling plans to catalogue data. Explain duration and commitments from the actual serving and plan information.
### Proof context
Use the proof owners for certification, test reports, reviews and before/after claims. Do not treat badges, white coats or numbers as interchangeable trust decoration.
## Apply through the owners
Use `references/assets/imagery-by-vertical.md` for imagery policy,
`references/workflows/_how-to-read.md` for execution, and
`references/consumer-behavior-cro.md` for relationship-based merchandising.
The selected type owns proof placement; `references/proof/` and
`references/offers/` own eligibility and terms. House styling comes only from
`references/design-rules.md`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |