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-beauty.md
View on GitHub# Beauty 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
### Suitability
Identify the skin/hair concern, routine position, texture preference and exclusions before choosing the angle. Do not present the same product as suitable for everyone.
### Variants
A shade, finish or size is a purchase decision. Preserve the exact catalogue variant and its media; keep shade names legible rather than relying on color alone.
### Product explanation
Show packaging, texture, application amount and how the product fits the routine. Ingredients and mechanisms need the merchant evidence appropriate to the actual claim.
### Image decisions
Prioritize texture, scale, shade/finish and application jobs. An identity image is not evidence of an in-use result. Use the vertical imagery owner for source eligibility.
### Proof context
Keep routine, skin/hair context and stated limitations with a review when the source carries them. Before/after media is a separate evidence decision, not an aesthetic treatment.
### Purchase concerns
Clarify quantity, expected use, shipping and returns from the merchant context. Complementary routine products must solve a stated relationship, not fill a generic recommendation row.
## 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 |