juicyjuicy 0.3.0 → 0.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -2
- package/dist/index.js +1956 -212
- package/dist/skill/SKILL.md +42 -16
- package/dist/skill/reference/cloud-saves.md +123 -0
- package/dist/skill/reference/engines.md +1 -1
- package/dist/skill/reference/manifest.md +2 -2
- package/dist/skill/reference/troubleshooting.md +6 -4
- package/package.json +3 -5
package/README.md
CHANGED
|
@@ -6,18 +6,24 @@ In your AI coding agent (Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI,
|
|
|
6
6
|
|
|
7
7
|
> Run npx juicyjuicy setup, then publish this game to JuicyJuicy
|
|
8
8
|
|
|
9
|
-
`setup` installs the JuicyJuicy skill for the agents on your machine (in `~/.agents/skills`, plus `~/.claude/skills` and Antigravity's folders when you have them) and logs you in (approve in the browser). After that, just say *"publish this game to JuicyJuicy"*. Or do it yourself:
|
|
9
|
+
`setup` installs the JuicyJuicy skill for the agents on your machine (in `~/.agents/skills`, plus `~/.claude/skills` and Antigravity's folders when you have them) and logs you in (approve in the browser). It replaces only copies of the skill it wrote; a copy you changed or linked stays unless you pass `--force` (a changed copy is backed up to `~/.juicyjuicy/skill-backups`). After that, just say *"publish this game to JuicyJuicy"*. Or do it yourself:
|
|
10
10
|
|
|
11
11
|
```bash
|
|
12
12
|
npx juicyjuicy publish # upload and print the link (first time: logs in, writes juicy.json)
|
|
13
13
|
npx juicyjuicy init # create or edit juicy.json
|
|
14
14
|
npx juicyjuicy check # validate without uploading
|
|
15
15
|
npx juicyjuicy list # your games and their versions
|
|
16
|
+
npx juicyjuicy publish --draft # upload without making it live
|
|
17
|
+
npx juicyjuicy rollback # make an earlier version or a draft live
|
|
16
18
|
npx juicyjuicy open # open the game page
|
|
17
19
|
```
|
|
18
20
|
|
|
19
21
|
Every command takes `--json` (one JSON object per line, the last one is the result) and `--yes` (never prompt). Exit codes: `0` ok, `1` fix the game or `juicy.json`, `2` log in, `3` network or server.
|
|
20
22
|
|
|
21
|
-
|
|
23
|
+
No `thumbnail` in `juicy.json`? `publish` takes a screenshot of your game with the Chrome, Edge, Chromium or Brave on your machine (headless, at the game's `aspectRatio`) and uses that; a page that stays one colour counts as no screenshot. Turn it off with `--no-auto-thumbnail`; if it can't, the game's tile shows its title on a gradient.
|
|
24
|
+
|
|
25
|
+
Environment: `JUICY_TOKEN` (a token from juicyjuicy.games/settings/tokens, for CI), `JUICY_API_URL` (another server, e.g. `http://localhost:3000`; https only, plain http only for localhost) and `JUICY_BROWSER` (the browser for the screenshot, if it isn't found).
|
|
26
|
+
|
|
27
|
+
In a sandbox that reaches only allowed domains (Claude Cowork, claude.ai), allow `juicyjuicy.games` and `*.r2.cloudflarestorage.com` and use a `JUICY_TOKEN`; otherwise the CLI stops with `NETWORK_BLOCKED` and names the blocked host.
|
|
22
28
|
|
|
23
29
|
Full guide: https://juicyjuicy.games/docs/publish
|