agentleFS
xsollaxsolla/xsolla-ai-kit/.cursor/skills/catalog-design/SKILL.md

catalog-design

Skill9 starsChanged 5 months agoMITView on GitHub

Sets up an Xsolla catalog: virtual items, virtual currency and its packages, bundles, game keys, item groups, regional prices and LiveOps offers, plus the client purchase flow (buy by SKU or cart, buy for virtual currency, order status). Use for "set up my Xsolla catalog", "create virtual items", "sell game keys", "regional prices".

  • Reads credentials

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the developer wants to:

    line 28
  2. Distinctive:

    Create virtual items, virtual currency, VC packages, bundles, or item groups

    line 30
  3. Distinctive:

    Add limited-time offers, purchase limits, promotions, offer chains, daily rewards or a reward system — "limited-time offer", "purchase …

    line 33
  4. Very specific:

    Choose the archetype and set up the catalog (Admin API): Ask which of the two the game needs (or both): in-game items (typical mobile/F2P) …

    line 66
  5. Very specific:

    Implement purchase: Default to fast purchase by SKU: client-side Create order with specified item (user JWT) → returns order_id + payment …

    line 96
  6. Very specific:

    A permanent unlock sold as a consumable: Check what each product means, not only its name and price.

    line 122
  7. Distinctive:

    Game keys + Pay Station Embed/iframe: Not supported — sell keys via a new window or direct link.

    line 135

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Status

This skill is a draft authored by the catalog SME (@p.sanachev, Tech Lead, IGS-Left).

Detailed material lives in references/:

  • references/items.md — virtual items, VC, packages, bundles, groups (Admin API)
  • references/game-keys.md — key packages, platforms, entitlement
  • references/pricing.md — local prices, regional restrictions
  • references/liveops.md — limits, time-limited offers, promotions, chains, reward system
  • references/catalog-client.md — client catalog calls
  • references/purchase-and-tracking.md — purchase flows, order confirmation

When to use

Use this skill when the developer wants to:

  • Create virtual items, virtual currency, VC packages, bundles, or item groups
  • Sell a game or DLC via game keys (Steam, Epic, PlayStation, DRM-free, …)
  • Set local prices per country or restrict sales by region
  • Add limited-time offers, purchase limits, promotions, offer chains, daily rewards or a reward system — "limited-time offer", "purchase limit", "first purchase bonus", "offer chain", "daily rewards", "reward system", "promo codes"
  • Build the store catalog UI on the client (game or website)
  • Implement purchase: fast purchase by SKU, cart, purchase for VC, free items
  • Confirm purchases: webhooks on the server or order tracking on the client

Out of scope: player inventory, server-side cart, refund handling, payment UI configuration (→ headless-checkout-integration), webhook handler code (→ webhooks-impl).

Prerequisites

export XSOLLA_MERCHANT_ID=<your merchant ID>
export XSOLLA_PROJECT_ID=<your project ID>
export XSOLLA_PROJECT_API_KEY=<your API key>
  • An Xsolla project (run merchant-setup first — it sets up these variables).
  • Check what the project already has. A new project can come with a demo catalog: a virtual currency, packs, items, a bundle and groups whose SKUs or IDs start with demo. List the catalog first; if demo entries exist, ask whether to keep, hide or replace them before adding anything.
  • Xsolla MCP (strongly recommended). Connect the official Xsolla MCP server (https://developers.xsolla.com/get-started/ai-assistants/). Before calling any Admin API, verify the current request schema with the search_xsolla_sources tool — this skill links the right operations, but field-level schemas must come from live docs, not from this file. If the MCP is unavailable, fetch the linked developers.xsolla.com pages, and say in your reply that the schemas came from the docs pages, not the MCP.

Steps

  1. Choose the archetype and set up the catalog (Admin API). Ask which of the two the game needs (or both): in-game items (typical mobile/F2P) — groups → virtual currency → virtual items → VC packages → bundles, see references/items.md; or game sales via keys — a key package per platform → upload keys, see references/game-keys.md. Admin calls use basic auth (XSOLLA_MERCHANT_ID:XSOLLA_PROJECT_API_KEY); verify each request body via the Xsolla MCP first.
  2. Propose a complete shop, not a price list. For in-game items, propose by default what gives players reasons to buy and to return: bundles and a starter pack, a first-purchase bonus, time-limited offers, per-player limits, an offer chain, daily rewards, a reward system and promo codes — a coherent set for the game, not all of them. Explain each in plain words and ask for every missing commercial value in one message; create nothing before the developer's yes. See references/liveops.md. On the Shop Builder path, nocode-shop-setup asks those values in its one batch and shows the proposal with the site plan, so a single yes covers both; don't ask for a separate one.
  3. Set up pricing. Recommend regional prices in local currencies for key markets via the prices array; keep the currency list and default currency identical across all items. For game keys, optionally add regional sale restrictions (regions → regions array) — depends on the game. See references/pricing.md.
  4. Build the catalog on the client (Catalog API). Render the store from client-side Catalog calls for the specific item types you sell (Get virtual items list, Get virtual currency list, Get list of bundles, Get games list), called from the client without a country parameter — country, prices, and regional availability resolve from the user's IP. Never use Admin calls for the storefront. See references/catalog-client.md.
  5. Implement purchase. Default to fast purchase by SKU: client-side Create order with specified item (user JWT) → returns order_id + payment token → open Pay Station with the token. Cart, purchase for VC, free items, and game-key specifics: references/purchase-and-tracking.md. The payment step itself belongs to the headless-checkout-integration skill.
  6. Confirm the purchase. Server (recommended): handle order_paid / order_canceled webhooks — implement with the webhooks-impl skill. Client (no server): WebSocket order status + short-polling Get order fallback. See references/purchase-and-tracking.md.
  7. Verify end-to-end. In sandbox ("sandbox": true, test cards): fetch the catalog via a Catalog call, buy an item, confirm the order reaches done, and the confirmation path (webhook or socket) fired.

Common pitfalls

  • Order creation from the server. Client payment calls resolve country → currency → payment methods from the caller's IP. Call them from the client; don't pass currency/country. (Server-side token generation is a separate API that requires country.value or X-User-Ip — prefer X-User-Ip for greenfield shops; see payment-country.)
  • Admin API on the storefront. Admin calls are rate-limited and not for user traffic; catalogs are built from Catalog-subsection calls, per item type.
  • Update wipes fields. Admin update calls replace, not merge: GET the item first and send back everything you want to keep (e.g. omit limits → limits deleted).
  • A permanent unlock sold as a consumable. Check what each product means, not only its name and price. A one-time unlock such as No Ads is non_consumable, the docs' own example, with limits.per_user total 1 so it can't be bought twice.
  • Inconsistent currencies break the catalog. Different currency sets or default currencies across items cause fallback prices or price: null on the storefront.
  • Bundles missing from a read-back. Listing a group's items doesn't return its bundles: read bundles back with the bundle list (Get list of bundles, or the CLI's bundles-by-group command) before deciding one is missing or hidden.
  • Products without pictures. Give every item, pack and bundle its own image, from the game's art the developer approved. List the products still without one in the handoff.
  • Wrong webhook set. Accounts registered after 2025-01-22 get combined order_paid/order_canceled; older accounts also receive separate payment/refund and must process them all.
  • Game keys + Pay Station Embed/iframe. Not supported — sell keys via a new window or direct link. With reglocks assigned, keys upload only via the Upload codes API.

Agent test

Prompt: "Configure my Xsolla catalog with items and pricing, then wire up purchase and order confirmation. It's a mobile F2P game with gems (virtual currency), gem packs, boosters, and a starter bundle."

Live run on sandbox project 173042 (2026-06-11): the agent discovered and applied this skill (+ webhooks-impl for confirmation context), verified schemas via the Xsolla MCP as mandated, and executed the real flow — created 3 groups, virtual currency, a consumable booster priced in VC, 2 VC packages, and a per-user-limited starter bundle (all 201); read everything back via typed client Catalog calls without country (IP-resolved USD prices, 200); created a server-side sandbox order + payment token (201, not paid); then deleted every created entity (204, verified empty). Steps requiring a user JWT (fast purchase, VC purchase, Get order/WebSocket) were planned and documented as blocked: no Login on the fixture project. ✅

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.