Use the StoreFront CLI with Cursor, Copilot and other shell agents
Any agent that can run shell commands can run uc-storefront. init has dedicated targets only for Claude Code, Codex, Gemini CLI and Hermes Agent. Status: Works with caveats.
Which folder each agent reads
Each vendor documents where its agent looks for project skills. init --target codex writes .agents/skills/, and --target claude writes .claude/skills/.
| Agent | Project skill folders it documents | Target to use |
|---|---|---|
| Cursor (editor) | .agents/skills/ and .cursor/skills/, plus .claude/skills/ for compatibility. No setting needed | codex |
| OpenCode | .opencode/skills/, .claude/skills/ and .agents/skills/ | codex or claude |
| GitHub Copilot CLI and the Copilot coding agent (CLI, coding agent) | .github/skills/, .claude/skills/ and .agents/skills/ | codex or claude |
| GitHub Copilot in VS Code | .github/skills/ is the only project folder its default agent documents | See below |
Cursor CLI (cursor-agent) | Confirmed by UltraCart to read .agents/skills/ once you trust the folder; in print mode (-p), pass --trust | codex |
UltraCart has run the Cursor CLI against the skill; the others are from each vendor's documentation, so check that yours lists it (below).
Copilot in VS Code: if the agent does not list build-ultracart-storefronts, copy the skill folder into .github/skills/ (cp -R .agents/skills/build-ultracart-storefronts .github/skills/), or use the Copilot CLI in the same folder. A copy you make yourself is not updated by skills install; copy it again after you upgrade the CLI.
Prerequisites
- Node.js 24 or newer, with npm (
node -v). - An agent that can run shell commands in your project folder.
- An UltraCart account whose user has StoreFront access.
Install the CLI and the skill
Installing both workspace copies covers every agent in the table:
npm install -g @ultracart/storefront-cli@beta
uc-storefront --version
uc-storefront init my-storefront --target codex --target claude --no-input
cd my-storefront
uc-storefront skills status
--target codex writes .agents/skills/build-ultracart-storefronts/, and --target claude writes .claude/skills/build-ultracart-storefronts/.
Check whether the agent sees the skill
- Open the workspace folder (the one with
ultracart.json) as the project in your agent. - Check the agent's trust setting for the folder. Some agents load project skills only from a trusted folder.
- Ask the agent to list its skills and look for
build-ultracart-storefronts.
If the agent does not list it, it can still read the skill as a file. Ask it to read .agents/skills/build-ultracart-storefronts/SKILL.md before it works on your store, and to follow the references that file points to. skills status confirms the files are there; it cannot tell whether your agent loaded them.
Sign in
On a desktop, the sign-in goes into the operating system's keychain. Run uc-storefront auth login --profile my-store yourself in a terminal, or let the agent use the two-step flow if its command tool shows output only when a command exits:
uc-storefront profile create my-store
uc-storefront auth login --profile my-store --no-wait
uc-storefront auth login --profile my-store --continue --wait
uc-storefront profile bind my-store
The first command prints a URL and a code and exits at once; you approve in your own browser. The second waits up to 45 seconds and exits 0 once signed in, or 3 while still waiting, so the agent runs it again until it exits 0.
If the agent runs in a cloud container rather than on your computer, uc-storefront auth status shows credential store: encrypted-file, and you need a credential key first. See Hosted agents, containers and CI.
Google Antigravity
Google Antigravity (the CLI, IDE and app) reads .agents/skills/ and has its own page: Use the StoreFront CLI with Google Antigravity.
Next steps
- Connect your store: profiles, binding and how long a sign-in lasts
- Safety and human approval: read before the first live change
- What it can do: the areas your agent can work on with the skill