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-luxury.md
View on GitHub# Luxury 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
### Provenance
Let the real maker, origin, material and process provide differentiation. Separate verified heritage from evocative brand copy.
### Craftsmanship
Use observable details and the actual process to explain value. A product close-up must reveal something the shopper can evaluate.
### Image decisions
Prioritize material detail, finish, scale and the intended use context. The visual direction follows the product rather than a default dark background or oversized serif.
### Service
Personalization, concierge, repair, care and appointment services are useful only when the merchant actually offers them. Match the CTA to the available service.
### Commerce
Keep price, variant decisions and purchase terms readable. Understatement does not justify hiding essential information or disguising the primary action.
### Restraint
Use the house spacing, typography and motion authority. Do not turn luxury into its own rule set permitting low contrast, decorative transitions or invented exclusivity.
## 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 |