Skip to content

Aetheria-Labs1/storefront-skills / skills/publish

publish

Verified

Publish 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.

FileKindSize
SKILL.mdskill md3.5 KB
agents/openai.yamlconfig404 B
references/ab-testing.mdmarkdown6.3 KB
references/ad-to-page.mdmarkdown1.3 KB
references/animation-system.mdmarkdown11.1 KB
references/anti-patterns/copy-anti-patterns.mdmarkdown12.2 KB
references/anti-patterns/cro-anti-patterns.mdmarkdown17.8 KB
references/anti-patterns/dark-patterns.mdmarkdown23.9 KB
references/anti-patterns/design-anti-patterns.mdmarkdown9.3 KB
references/anti-patterns/mobile-anti-patterns.mdmarkdown9.7 KB
references/asset-prep.mdmarkdown6.9 KB
references/assets/asset-sourcing-sequence.mdmarkdown12.2 KB
references/assets/generation-policy.mdmarkdown25.9 KB
references/assets/image-jobs-by-page-type.mdmarkdown31.8 KB
references/assets/imagery-by-vertical.mdmarkdown24.8 KB
references/assets/slot-spec.mdmarkdown20.2 KB
references/assets/video-rules.mdmarkdown17.6 KB
references/authoring/css-and-styling.mdmarkdown4.0 KB
references/authoring/source-authoring.mdmarkdown9.0 KB
references/blob-shapes.mdmarkdown1018 B
references/cart-composition.mdmarkdown7.2 KB
references/cart-profile-management.mdmarkdown17.1 KB
references/consumer-behavior-cro.mdmarkdown12.7 KB
references/copy/copy-frameworks.mdmarkdown20.5 KB
references/copy/headline-and-cta-rules.mdmarkdown12.9 KB
references/copy/message-match.mdmarkdown9.2 KB
references/copy/voice-of-customer-mining.mdmarkdown10.9 KB
references/design-assets.mdmarkdown366 B
references/design-enrichment.mdmarkdown334 B
references/design-rules.mdmarkdown15.5 KB
references/generate-collection.mdmarkdown555 B
references/generation-protocol.mdmarkdown3.2 KB
references/islands/collection-grid/index.mdmarkdown5.4 KB
references/islands/collection-swipe/index.mdmarkdown4.1 KB
references/lexsis-mcp-contract.mdmarkdown14.2 KB
references/merchant-templates.mdmarkdown2.6 KB
references/module-authoring.mdmarkdown9.0 KB
references/offers/campaign-calendar.mdmarkdown21.4 KB
references/offers/funnel-stages.mdmarkdown17.6 KB
references/offers/offer-ledger.mdmarkdown5.1 KB
references/offers/offer-strategy.mdmarkdown9.6 KB
references/offers/offer-types.mdmarkdown36.6 KB
references/offers/price-presentation.mdmarkdown18.0 KB
references/offers/urgency-scarcity.mdmarkdown17.5 KB
references/page-editing.mdmarkdown9.7 KB
references/page-files.mdmarkdown2.7 KB
references/page-types/_checklist-format.mdmarkdown11.1 KB
references/page-types/_index.mdmarkdown21.9 KB
references/page-types/collection-landing.mdmarkdown21.9 KB
references/product-grid.mdmarkdown2.0 KB
references/proof/before-after-and-claims.mdmarkdown19.2 KB
references/proof/numbers-and-counts.mdmarkdown16.0 KB
references/proof/press-and-media-mentions.mdmarkdown12.5 KB
references/proof/proof-ledger.mdmarkdown8.3 KB
references/proof/reviews-sourcing.mdmarkdown24.8 KB
references/proof/trust-badges-certifications.mdmarkdown21.8 KB
references/proof/ugc-rights-and-display.mdmarkdown16.0 KB
references/publishing.mdmarkdown2.4 KB
references/qa-recipe.mdmarkdown4.3 KB
references/quiz-authoring.mdmarkdown14.5 KB
references/resource-templates.mdmarkdown7.7 KB
references/scroll-patterns.mdmarkdown1.2 KB
references/source-artifact-workflow.mdmarkdown3.7 KB
references/styling-hooks.mdmarkdown7.8 KB
references/traffic-source-google.mdmarkdown1.6 KB
references/traffic-source-meta.mdmarkdown1.5 KB
references/traffic-source-tiktok.mdmarkdown1.5 KB
references/vertical-beauty.mdmarkdown1.8 KB
references/vertical-fashion.mdmarkdown1.7 KB
references/vertical-food.mdmarkdown1.6 KB
references/vertical-home.mdmarkdown1.7 KB
references/vertical-luxury.mdmarkdown1.6 KB
references/vertical-supplements.mdmarkdown1.7 KB
references/workflow-intent.mdmarkdown2.0 KB
references/workflows/_how-to-read.mdmarkdown2.7 KB
references/workflows/copy-workflow.mdmarkdown1.5 KB
references/workflows/island-selection-workflow.mdmarkdown4.8 KB
references/workflows/section-asset-workflow.mdmarkdown5.8 KB

references/workflows/section-asset-workflow.md

View on GitHub
# Section asset workflow

This is the single `/plan-assets` execution procedure for sourcing,
missing-slot handling, and visual fit. Type files provide jobs, tags, crops and budgets; policy
lives in `references/assets/asset-sourcing-sequence.md`,
`references/assets/generation-policy.md`, `references/assets/slot-spec.md`,
`references/assets/video-rules.md` and the relevant proof ledger.

## 1. Acquisition and missing-slot handling

1. Read the type's section job and budget. Decide whether imagery is needed;
   a native disclosure or factual table does not need a decorative image.
2. Inventory real catalogue media, the merchant's selections, and existing
   library assets before planning new media. Assign each candidate its actual
   job, product/variant, dimensions and rights evidence.
3. Follow the source eligibility order in
   `references/assets/asset-sourcing-sequence.md`. Use the type's search tags
   and queries. A missing tag is not proof that the library is empty.
4. Run the fit review in section 2 before binding a candidate. Retain rejection
   reasons so the same unsuitable image is not proposed repeatedly.
5. For a remaining slot, consult `references/assets/generation-policy.md`.
   That file owns ALLOW / ASK / NEVER, credit approval, identity protection,
   prompts and generation records. Do not infer permission from a page type.
6. Tell the merchant what is missing: section, job, aspect, count and why it
   matters. Offer **upload**, **generate** only where that policy permits it,
   or **skip/merge** with an explanation of what the page loses. Group gaps
   into one useful message, not a question for each section.
7. A required production slot remains unresolved until a verified source is
   bound. Do not silently remove a required section or substitute a
   placeholder. A section adjustment returns to `/plan-page`.
8. Skip or merge a section only on the merchant's decision. A generation ban
   is not permission to invent media, substitute irrelevant stock, or hide
   the missing job behind a decorative band.

### Import, upload and selection

- `lexsis_asset_library.search` returns read-only search evidence: the terms
  and filters used, matching assets, result count, and pagination state. Do not
  wait after search.
- `lexsis_asset_select.select` opens the interactive picker when the merchant
  should choose among fit-reviewed candidates. Pass the relevant search terms
  and filters, wait for the user's selection message, and map its order to the
  named slots. It may be called directly, although searching first is the
  normal agent workflow.
- `lexsis_asset_import.import` persists an available URL, image base64 with
  MIME type, or conversation attachments. Supply exactly one source.
- `lexsis_asset_upload.upload` opens the local-file UI. Scope it to the
  selected workspace/theme and wait for the user's uploaded-asset message.
  Without inline UI, ask for a URL or conversation attachment and import it.
  Opening a panel is not an upload. The exact argument contract is in
  `references/lexsis-mcp-contract.md`.

### Search efficiently

Use the current search schema. Tags such as `hero`, `lifestyle`,
`product-shot`, `social-proof` and `logo` are conventions, not a closed enum.
Try semantic queries for missing jobs and filename lookup for a supplied
filename. Where supported, OCR search helps identify baked-in overlays and
similarity search around a verified seed helps maintain a coherent set.
Result geometry screens candidates before the visual review; metadata never
replaces inspection. Keep the selected workspace and theme binding explicit.

## 2. View and fit review

Nothing is used sight unseen. Do not accept the closest existing asset merely
because it is available. Open each candidate with `lexsis_assets.view`;
if the host cannot display it, inspect the returned permanent URL with the
available image viewer. Judge the asset **in its intended section**:

| Check | Required decision |
|---|---|
| Identity and job | Correct product/variant; the image actually demonstrates the assigned job |
| Crop | Desktop and mobile crops preserve the subject and required detail |
| Text placement | Copy has an appropriate quiet region, or moves outside the image; A7 still governs contrast |
| Set consistency | View adjacent/grid candidates together; they should read as one shoot rather than unrelated finds |
| Palette | The image works with the plan's visual direction without falsifying product appearance |
| Resolution | Detail survives at the actual mobile and desktop rendered sizes |
| Source integrity | Rights are recorded; no misleading overlay, watermark or competitor branding; genuine product labels remain readable where the job requires them |

A near-uniform preview can be a failed preview. Inspect the original URL
before rejecting the asset or spending credits on a replacement. Apply this
same review after generation; payment is not evidence of suitability. A
rejected generation returns to the policy's bounded repair/fallback route.

## 3. Asset budget and record

The type's budget records supplied jobs, missing jobs and type-specific
alternatives. It does not redefine source permissions. Assign each slot a
source decision, rights basis, final asset or Shopify media id, and status.
Use the binding and production tables defined by `/plan-assets`; generation
records follow the generation-policy owner. Mark rejected or unresolved jobs
accurately.

Example merchant message: "The kit has a packaging image but no image of
all included items. Supply one overhead kit photo, or choose to omit the
optional unboxing section; the included-items job is still pending."

## 4. Write to the resolved job

After the media decision, execute `references/workflows/copy-workflow.md`.
Do not invent benefit imagery or pad the copy because a requested image is
missing. A deliberately text-only section follows its type contract.
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: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall