Skip to content

Aetheria-Labs1/storefront-skills / skills/optimize

optimize

Flagged

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

FileKindSize
SKILL.mdskill md13.6 KB
agents/openai.yamlconfig499 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/conversion-psychology.mdmarkdown403 B
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/evidence-led-cro.mdmarkdown1.2 KB
references/generate-bundle-page.mdmarkdown303 B
references/generate-collection.mdmarkdown555 B
references/generate-editorial.mdmarkdown366 B
references/generate-homepage.mdmarkdown280 B
references/generate-landing-page.mdmarkdown335 B
references/generate-listicle.mdmarkdown295 B
references/generate-pdp.mdmarkdown312 B
references/generation-protocol.mdmarkdown3.2 KB
references/industry-cro.mdmarkdown433 B
references/island-patterns.mdmarkdown380 B
references/islands/collection-grid/index.mdmarkdown5.4 KB
references/islands/collection-swipe/index.mdmarkdown4.1 KB
references/lexsis-design-capabilities.mdmarkdown6.2 KB
references/lexsis-mcp-contract.mdmarkdown14.2 KB
references/merchant-templates.mdmarkdown2.6 KB
references/module-authoring.mdmarkdown9.0 KB
references/offers/aov-levers.mdmarkdown17.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-stacking.mdmarkdown3.5 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/ad-landing-page.mdmarkdown29.0 KB
references/page-types/advertorial.mdmarkdown28.2 KB
references/page-types/brand-story-founder.mdmarkdown20.6 KB
references/page-types/bundle-kit.mdmarkdown27.4 KB
references/page-types/collection-landing.mdmarkdown21.9 KB
references/page-types/comparison-us-vs-them.mdmarkdown24.5 KB
references/page-types/faq-support-led.mdmarkdown20.4 KB
references/page-types/gift-guide.mdmarkdown22.0 KB
references/page-types/homepage.mdmarkdown23.6 KB
references/page-types/ingredient-science.mdmarkdown28.3 KB
references/page-types/launch-waitlist-preorder.mdmarkdown28.1 KB
references/page-types/lead-capture-giveaway.mdmarkdown22.6 KB
references/page-types/listicle.mdmarkdown27.2 KB
references/page-types/lookbook-shop-the-look.mdmarkdown19.6 KB
references/page-types/offer-page.mdmarkdown25.8 KB
references/page-types/pdp-hybrid-landing.mdmarkdown31.1 KB
references/page-types/pdp.mdmarkdown32.8 KB
references/page-types/quiz-funnel.mdmarkdown26.2 KB
references/page-types/referral-loyalty-vip.mdmarkdown18.4 KB
references/page-types/restock.mdmarkdown23.3 KB
references/page-types/retargeting-warm.mdmarkdown24.9 KB
references/page-types/sale-clearance-flash.mdmarkdown25.0 KB
references/page-types/seasonal-gifting.mdmarkdown26.9 KB
references/page-types/seo-buyers-guide.mdmarkdown23.9 KB
references/page-types/subscription.mdmarkdown26.5 KB
references/page-types/thank-you-post-purchase.mdmarkdown19.7 KB
references/page-types/trial-sample.mdmarkdown24.4 KB
references/page-types/ugc-creator-collab.mdmarkdown27.5 KB
references/page-types/video-sales-page.mdmarkdown25.1 KB
references/page-types/wholesale-b2b.mdmarkdown24.2 KB
references/plan-page.mdmarkdown9.7 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/module-authoring.md

View on GitHub
# Custom Cart Module Authoring

Use one complete Lexsis source section in `composition_ops` with
`operation:"upsert"`, a stable `module_id`, and `source`. An upsert with source
replaces the whole source, including HTML, CSS and script. Omitting source
preserves it when changing placement, enabled state or `visible_when`.
Renderer-owned cart islands must not be embedded in a custom module.

## Lifecycle and state

`root` and `lifecycle.root` are the renderer's
`[data-cart-custom-module="<module_id>"]` wrapper, not the authored inner
`<section>`. `lifecycle.query(selector)` returns the first matching descendant
or null; `queryAll` returns an array. Both exclude island internals.
Use `lifecycle.on(target,event,handler)` for managed listeners. Timers, frames,
observers and `addCleanup` are managed too; unmount stops them.
`section` remains a deprecated alias of `root`. `lifecycle.setVisible(boolean)`
controls the wrapper and authored top-level section; an authored hidden root
section produces a compile warning.

The compiler rejects `window` and `document` access. Do not reach outside the
wrapper, fetch Shopify directly, write cart storage or dispatch fake response
events. Use the cart commands below.

`lifecycle.cart` is a deeply frozen CartSnapshot. Subscribe with
`lifecycle.onCart((snapshot,previous) => {...})` during initialization: the
getter throws before the store currency and prices are available. The first
callback receives `previous:null`; later callbacks run after mutation/reward
settlement, at most once per frame. The returned unsubscribe function stops
the listener early; unmount cleans it up automatically. During a mutation,
the getter reports pending status with confirmed merchandise amounts.

Read `lexsis_cart.capabilities` for `snapshot_schema`, `module_lifecycle`,
`commands`, and `conditions`. Snapshot fields:

- `status`, `itemCount`, `currency`, `subtotal`, `total`, `compareAtSubtotal`, `savings`
- `discountCodes`: code and applicability
- `lines`: identity, variant/product IDs, handle, titles, quantity, prices,
  line total, selling plan, attributes, tags, collections and reward-gift flag
- `rewards.next`: id, type, title, threshold and remaining Money, or null
- `rewards.unlocked`: id/type/title; `chosenGiftVariantId`: variant ID or null
- `context`: market, locale, pageHandle, pageType, UTM fields and customer flags

Money is `{amount:"552.00",currencyCode:"INR",minor:55200}`. Use the snapshot's
currency, never an invented default. Summary and modules use the same confirmed
selectors: subtotal is after line discounts, before shipping/tax and remaining
order discounts; savings includes those order discounts without counting line
discounts twice. Reward remaining uses paid-price eligibility, excluding gifts
from qualifying spend. Eligibility is not proof of Shopify discount application.
Tags/collections depend on available metadata; customer flags default false
without a host session provider.

## Commands and responses

Dispatch a bubbling `CustomEvent` from `root` with a unique `requestId` in
`detail`. Responses arrive on that same **wrapper** and bubble. Listen on
`root`, not only on an authored inner element. Every command emits
`:pending`, `:accepted`, `:confirmed`, then terminal `:success` or `:error`.
Errors can arrive before any intermediate phase. Filter responses by requestId.

| Event | Additional detail fields |
| --- | --- |
| `lx:cart:add-items` | `items:[{variantId,quantity,sellingPlanId?,attributes?}]`, `openCart?` |
| `lx:cart:update-line` | `lineId`, `quantity` |
| `lx:cart:remove-line` | `lineId` |
| `lx:cart:apply-code` | `code` |
| `lx:cart:remove-code` | `code` |
| `lx:cart:set-attributes` | `attributes` |
| `lx:cart:set-note` | `note` |
| `lx:cart:choose-gift` | `rewardId`, `variantId` |
| `lx:cart:swap-variant` | `lineId`, `variantId`, optional `quantity` |

Use the live capabilities for exact payload types, limits and error codes.
Reuse the same requestId only to replay the identical request; a changed payload
fails with `request_id_conflict`. A terminal replay returns the recorded outcome
without a second mutation. `partial_add`/`partial_swap` require inspecting the
current cart; do not blindly retry with a new ID. Success means settled, not
just accepted. A sample preview handles commands in memory and blocks checkout.

## Complete upsell with live state

This is a compiler-tested template. Replace the example variant GID and item
label with a verified, available catalog variant before saving. The template
does not invent a price or discount. It displays the profile's next reward,
updates after cart changes, and disables adding when the variant is present.

```html lexsis-cart-example
<!-- section: matching-item -->
<section class="upsell" data-variant-id="gid://shopify/ProductVariant/123">
  <h3>Add a matching item</h3>
  <p data-remaining hidden></p>
  <button type="button" data-lx-control="add-upsell" disabled>Add item</button>
  <p data-result role="status" aria-live="polite"></p>
  <style>
    .upsell { padding: 16px; border: 1px solid var(--lx-border-color); }
    .upsell button { min-height: 44px; padding: 8px 16px; }
    .upsell button:disabled { opacity: 0.6; }
  </style>
  <script>
    const content = lifecycle.query('[data-variant-id]');
    const button = lifecycle.query('[data-lx-control="add-upsell"]');
    const remaining = lifecycle.query('[data-remaining]');
    const result = lifecycle.query('[data-result]');
    const variantId = content.dataset.variantId;
    let requestId = null;
    let sequence = 0;
    let present = false;
    const refreshButton = () => {
      button.disabled = Boolean(requestId) || present;
      button.textContent = requestId ? 'Adding...' : present ? 'Already in cart' : 'Add item';
    };
    lifecycle.onCart((cart) => {
      present = cart.lines.some((line) => line.variantId === variantId);
      const next = cart.rewards.next;
      remaining.hidden = !next;
      remaining.textContent = next
        ? new Intl.NumberFormat(cart.context.locale || undefined, {
            style: 'currency', currency: next.remaining.currencyCode
          }).format(Number(next.remaining.amount)) + ' to go for ' + next.title
        : '';
      refreshButton();
    });
    lifecycle.on(button, 'click', () => {
      if (requestId || present) return;
      requestId = 'upsell-' + Date.now() + '-' + (++sequence);
      refreshButton();
      result.textContent = '';
      root.dispatchEvent(new CustomEvent('lx:cart:add-items', {
        bubbles: true,
        detail: { requestId, items: [{ variantId, quantity: 1 }], openCart: true }
      }));
    });
    lifecycle.on(root, 'lx:cart:add-items:pending', (event) => {
      if (event.detail.requestId === requestId) result.textContent = 'Adding item...';
    });
    lifecycle.on(root, 'lx:cart:add-items:success', (event) => {
      if (event.detail.requestId !== requestId) return;
      requestId = null;
      present = lifecycle.cart.lines.some((line) => line.variantId === variantId);
      result.textContent = 'Added to your cart';
      refreshButton();
    });
    lifecycle.on(root, 'lx:cart:add-items:error', (event) => {
      if (event.detail.requestId !== requestId) return;
      requestId = null;
      result.textContent = event.detail.message;
      refreshButton();
    });
  </script>
</section>
```

To hide this whole upsell once added, include this sibling of `source` in the
upsert, using the same verified variant GID:

```json
{
  "visible_when": {
    "op": "AND",
    "clauses": [{"field": "cart.has_variant_id", "op": "neq", "value": "gid://shopify/ProductVariant/123"}]
  }
}
```

For a trust row on nonempty carts, use `cart.item_count`, `op:"gt"`, `value:0`.
Rules apply to optional built-ins as well. Required cart lines, summary and
checkout cannot be hidden. Hidden modules use `hidden` and leave the
accessibility tree; they remain in the DOM for live visibility changes.
Disabled modules (`set_enabled:false`) are omitted from generated sections.

## Bind text and conditions without JavaScript

```html lexsis-cart-example
<!-- section: next-reward -->
<section>
  <p data-lx-if="rewards.next.remaining.minor &gt; 0">
    Only <strong data-lx-text="rewards.next.remaining"></strong> to go for
    <span data-lx-text="rewards.next.title"></span>.
  </p>
</section>
```

Money bindings format the store currency. Expressions support comparisons,
`!`, `&&`, `||`, parentheses and the documented predicates, including
`reward.unlocked('reward-id')`. They are parsed, never evaluated as JavaScript.
Unknown paths/functions fail compilation. Read the complete field/operator
inventory from capabilities; money comparisons use minor units.

## CSS scope

Compiled module CSS is wrapped in
`@scope ([data-cart-custom-module="<module_id>"])`. Author ordinary selectors;
do not add a global page selector or a second manual cart wrapper. Compiler
`:root`/`:host` token selectors are adapted to the module scope.
Scoped module CSS belongs to cart design; profile `custom_css` has precedence.
Do not depend on page CSS reaching the cart. Use `references/styling-hooks.md`
for profile-wide seams and inline-style exceptions.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall