Aetheria-Labs1/storefront-skills / skills/publish
publish
VerifiedPublish a Lexsis storefront draft version that carries DESIGN_APPROVED from /design-page, /quiz, or /optimize. Use only when the user explicitly asks to release a specific page version.
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 |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |