xsolla-ai-kit
Copilot instructions9 starsChanged 5 months agoMITView on GitHub
This repo contains Xsolla agent skills. You are helping a developer build or integrate Xsolla-powered game commerce features.
- Reads credentials
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/xsolla-ai-kit.mdcCursor rule
- catalog-designSkill
- description-to-shopSkill
- game-web-portalSkill
- headless-checkout-integrationSkill
- login-setupSkill
- login-stylingSkill
- merchant-setupSkill
- nocode-shop-setupSkill
- productionSkill
- quest-setupSkill
- shop-builder-assemblySkill
- shopbuilder-translateSkill
- shop-setupSkill
- webhooks-implSkill
- xla-pagesSkill
- catalog-designSkill
- description-to-shopSkill
- game-web-portalSkill
- headless-checkout-integrationSkill
- login-setupSkill
- login-stylingSkill
- merchant-setupSkill
- nocode-shop-setupSkill
- productionSkill
- quest-setupSkill
- shop-builder-assemblySkill
- shopbuilder-translateSkill
- shop-setupSkill
- webhooks-implSkill
- xla-pagesSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 7
Every workflow lives in skills/<name>/SKILL.md.
- Distinctive: line 13
Never commit a real key, token, JWT, webhook secret or session cookie.
≈ “Common” is an estimate: at least 1 in 5 of the 3,827 Copilot instructions 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.
Files
GitHub Copilot Instructions — xsolla-ai-kit
This repo contains Xsolla agent skills. You are helping a developer build or integrate Xsolla-powered game commerce features.
Context
- Every workflow lives in
skills/<name>/SKILL.md. Read the skill before acting, then only thereferences/files the current step needs. Do not invent Xsolla steps from memory. - There are two ways to build a shop. Read Shop building paths in
AGENTS.mdfirst:- In code:
shop-setup. The developer writes, deploys and reviews the shop. Skills call Xsolla REST APIs directly; payments use Headless Checkout or Pay Station. - In Shop Builder (Site Builder, no code):
nocode-shop-setup. The agent drives Shop Builder through the Xsolla CLI 1.9.4 or later. It continues indescription-to-shop,shop-builder-assembly,shopbuilder-translateorgame-web-portal.
- In code:
- Environment variables (set up by
merchant-setup):XSOLLA_MERCHANT_ID,XSOLLA_PROJECT_ID,XSOLLA_PROJECT_API_KEY. - API auth is HTTP Basic. Project-level calls use
Base64({project_id}:{api_key}); merchant-level calls useBase64({merchant_id}:{api_key}). Each skill says which one it needs. - Never commit a real key, token, JWT, webhook secret or session cookie.
Available skills
<!-- skill-table:start (generated by .github/scripts/skill_table.py; do not edit) -->| Skill | What it does and when to use it |
catalog-design | 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". |
description-to-shop | Turns a game description or store listing (App Store, Google Play, Steam) into the shop brief that shop-builder-assembly builds from. Reached through nocode-shop-setup; not an entry point. Owns intake and inference only: presets, confirmation, CLI writes and preview belong to shop-builder-assembly. |
game-web-portal | Builds or resumes an unpublished Game Web Portal for a PC or mobile game: Home, News, Rewards, Web Shop, Community and an optional Launcher, on a site made from the Multi-page web portal template. Reached through nocode-shop-setup. Use for "continue my Game Web Portal" or "add the Community section". Never publishes; that stays with the human. Not for XLA Pages on x.la; use xla-pages. |
headless-checkout-integration | Integrates Xsolla Headless Checkout — a fully customizable, client-controlled payment UI built on the @xsolla/pay-station-sdk JavaScript SDK, where payment data stays isolated in secure iframes and payments run through Xsolla without the standard Pay Station. |
login-setup | Integrates Xsolla Login (Xsolla ID, NewID): sign-up and sign-in by password, email or SMS code, social networks, Steam, Xbox, PSN, Epic, device or custom ID; Login Widget, API or SDK; JWT validation, server tokens, account linking, MFA, password reset. Use for "integrate Xsolla Login", "add sign-in", "validate a user JWT", or when a feature needs a signed-in user. |
login-styling | Styles the Xsolla Login widget (sign-in, sign-up, password reset): upload custom CSS through the API and attach it to the login project, or set colors, logo, background and social order through themeJSON. Use for "style the login", "brand the sign-in screen", "upload login CSS", "dark-mode login". Pairs with login-setup, which wires the auth flow. |
merchant-setup | Guide for a merchant or developer setting up an Xsolla Account and obtaining API credentials. Use when the user needs that account, API keys, merchant-level versus project-level keys, sandbox mode, to accept payments, to start an Xsolla integration, or to test payments. The agent cannot create the account. This skill gives the exact steps the user completes manually. |
nocode-shop-setup | Builds a shop, web shop or storefront on Xsolla's side with Shop Builder: no code, servers or deploys. Use when the user says build me a shop or "create a web shop for my game", unless the user will code it, and for "I don't want to write code". No local repo or no coding means this path. Also installs the Xsolla CLI; the user signs in. If the user will write and deploy code, open shop-setup. |
production | Takes Xsolla payments from sandbox to real money. Headless Checkout and Pay Station follow the same steps: licensing agreement, tax interview, switching off sandbox, a public HTTPS webhook, and a live payment checklist. Use for "go live", "leave sandbox", "switch my shop to production", "Merchant contract not signed", or error 0002-0004. |
quest-setup | Create, edit, list, activate, pause, delete or debug Xsolla Quest Platform quests: conditions, rewards (Web3 included) and quest events. Also the Quests block on a Shop Builder site: add, move, hide or show it, and change its heading, card count, or card titles, text, images and buttons. Use when a request names a quest, a quest card or the Quests block, e.g. "create a quest". |
shop-builder-assembly | Assembles a Shop Builder storefront from a validated shop brief: pages, layout, navigation, standard blocks, localization, catalog links, theme and copy, with mobile, PC and live-service presets. Reached through nocode-shop-setup after description-to-shop; not an entry point. Prefer it over adding single blocks. Not for a coded storefront (shop-setup). Not for XLA Pages on x.la; use xla-pages. |
shop-setup | A shop the user codes, reviews, and deploys, or Xsolla embedded in a shop the user already built. Use for "build me a shop" when the user or the agent will write the code, or "embed Xsolla in my store". A local repo makes this more likely; a shop in it, more still; Xsolla already there means this skill. If the user will not write and deploy, open nocode-shop-setup. |
shopbuilder-translate | Translates Shop Builder page copy: hero, buttons, FAQ, section titles and page SEO. Use for "translate the FAQ", "add a language to Shop Builder", "my store is only in English". Catalog and LiveOps text are out of scope. Confirms before any write. Not for building the shop or setting prices. |
webhooks-impl | Builds and checks the backend a merchant or developer runs to receive Xsolla webhooks. The payment UI only starts the flow and does not receive them. Xsolla calls that backend: user_validation when the player starts paying, and order_paid after payment so the merchant or developer grants the item. Also refunds and cancellations. Use for "implement Xsolla webhooks" or "grant items after purchase". |
xla-pages | Creates and updates XLA Pages on x.la in Shop Builder: game pages, payment provider pages and combined pages, from @xla-pages blocks bound to the XLA Pages API. Use for "create pages for x.la", "generate XLA game pages", "add a Klarna payment page on x.la", "update the PayPal page on x.la" or an XLA Pages batch file. Never publishes. For any other Shop Builder site, use nocode-shop-setup. |
<!-- skill-table:end -->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
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.

