agentleFS
saleorsaleor/saleor-dashboard/.claude/skills/saleor-dashboard-cloud-extensions/SKILL.md

saleor-dashboard-cloud-extensions

Skill1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub

Saleor Cloud extensions: the private submodule at src/cloud-extensions/src and its public contract in src/cloud-extensions/index.ts. Use when setting it up, changing extension code or the contract, or bumping the submodule pointer.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 5 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 33 mentionsJul 2026: 3 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the saleor/saleor-dashboard repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about saleor/saleor-dashboard

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run pnpm cloud:setup. It needs read access to the private repo (Saleor team only).

    line 19
  2. Very specific:

    After changing extension messages, run pnpm extract-messages:cloud.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Saleor Cloud extensions

The private saleor/dashboard-cloud-extensions repository is a submodule at src/cloud-extensions/src. It is Dashboard source: same lint, types, tests and conventions as the rest of src/. The public src/cloud-extensions/index.ts holds the contract and loads it. The decision and its reasons are in docs/adr/0002-cloud-features-in-dashboard.md; extension internals are in the private repo's AGENTS.md.

Setup

Run pnpm cloud:setup. It needs read access to the private repo (Saleor team only); without it the extensions render nothing. Each git worktree needs its own setup. pnpm dev prints the checked-out commit and branch and warns when the checkout is stale, differs from the pinned commit, or is dirty.

Changing extension code

  1. In src/cloud-extensions/src, create a branch from origin/main, commit there, push, and open a PR in the private repo.
  2. In the Dashboard, stage the new pointer (git add src/cloud-extensions/src) and commit it on the Dashboard branch.
  3. Link the two PRs to each other in their descriptions.
  4. Merge the private PR first. The private repo allows merge commits only, so the pinned commit stays valid. Dashboard CI stays red until the pinned commit is on the private main.
  5. Merge the Dashboard PR.

To take the latest private main without code changes, run pnpm cloud:update and commit the pointer.

Changing the contract

Edit both sides in one change: CloudExtensions and its lazy export in src/cloud-extensions/index.ts, and the matching member of the CloudExtensions default export in src/cloud-extensions/src/index.ts. Add the new export to testUtils/__mocks__/cloudExtensions.ts too. Run check-types:src with the submodule checked out.

Messages

After changing extension messages, run pnpm extract-messages:cloud. It writes src/cloud-extensions/src/locale/defaultMessages.json. Extensions ship English only.

Keeping private code private

Everything outside src/cloud-extensions/src is public: commits, PR descriptions, ADRs, changesets and code comments in the Dashboard describe extensions only by their public contract. Extension code, internal endpoints and auth details stay in the private repo. Dashboard modules imported only by the extensions carry a @public JSDoc tag, so knip keeps them when the submodule is absent.

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.