You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ae66db9
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: recipes/2048/meta.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
"slug": "2048",
5
5
"vertical": "Tools, apps & games",
6
6
"tech": "Vanilla JS",
7
-
"summary": "The classic 2048 sliding-tile puzzle — arrow-key and swipe controls, smooth merge animations, score and persistent best score, and a win/lose overlay with restart and undo.",
7
+
"summary": "Play 2048 with keyboard or swipe controls. Keep your best score in the browser.",
**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
35
+
**When the site is ready, publish it to Spacefast:**
36
36
37
37
1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
38
-
2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
49
-
4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
58
-
59
-
**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
38
+
2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
39
+
3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
40
+
4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
41
+
5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
42
+
43
+
If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
Copy file name to clipboardExpand all lines: recipes/app/meta.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
"slug": "app",
5
5
"vertical": "Tools, apps & games",
6
6
"tech": "Vite + React",
7
-
"summary": "A multi-view task app prototype — a draggable kanban board, a sortable list view, and a task detail drawer with subtasks, comments, filters, and search, all saved on your device.",
7
+
"summary": "Organize tasks on a kanban board or list. This prototype saves changes on your device.",
**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
67
+
**When the site is ready, publish it to Spacefast:**
68
68
69
69
1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
70
-
2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
81
-
4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
70
+
2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
71
+
3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
72
+
4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
73
+
5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
90
74
91
-
**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait`does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) ·[claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
75
+
If the `sf` CLI is already installed, `sf publish ./dist --wait`follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and[claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
Copy file name to clipboardExpand all lines: recipes/arcade/meta.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
"slug": "arcade",
5
5
"vertical": "Local & small business",
6
6
"tech": "HTML5 canvas game",
7
-
"summary": "A neon barcade site whose hero is a playable retro brick-breaker game, wrapped around a real cabinets list, draft beer menu, events, and hours.",
7
+
"summary": "Build a barcade site with a playable brick-breaker, a games list, and opening hours.",
Copy file name to clipboardExpand all lines: recipes/arcade/prompt.md
+9-25Lines changed: 9 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,14 @@ Build me a **website for my retro arcade bar, with a playable mini-game as the h
14
14
-**On tap** — a rotating draft-beer list (name, brewery, style, ABV, price) plus a few house cocktails.
15
15
-**Events** — a week of tournament nights and happy-hour specials with prizes.
16
16
-**Visit** — address, a weekly hours table, age policy, and a map/photo with a link out to Google Maps.
17
-
-**Book a party** — a private-event request form (name, email, date, guest count, notes) that shows a friendly success message on submit.
17
+
-A private-event request form with name, email, date, guest count, and notes. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
18
18
- A footer with social links and the address.
19
19
20
20
**Design & content notes:**
21
21
22
22
- Neon-and-CRT mood: near-black/deep-violet background, hot-pink + cyan + lime accents, a pixel display font (e.g. "Press Start 2P") for headings and a clean sans (e.g. "Space Grotesk") for body. Add subtle scanlines and glow, plus a scrolling marquee strip — but keep text high-contrast and readable.
23
23
- Make the game genuinely fun: smooth 60fps loop with delta timing, the ball's bounce angle depends on where it hits the paddle, the paddle shrinks and the ball speeds up on later waves, and a launch-on-Space/tap mechanic.
24
-
- Use realistic content based on my answers — never "lorem ipsum". Invent believable brewery names, prices, tournament prizes, and hours.
24
+
- Use my confirmed brewery list, prices, prizes, and hours. Omit missing business facts or label the entire site as a fictional demo.
25
25
- Use real images. Pull free photos that fit, e.g. `https://picsum.photos/seed/retro-arcade-1/1200/800` (vary the seed) or Pexels, and add descriptive `alt` text.
26
26
- No build step: a single `index.html` plus `styles.css`, `game.js`, and a tiny `ui.js`. Persist the high score in `localStorage`.
27
27
- Keep it accessible (semantic HTML, labelled form fields, keyboard support, good contrast, a skip link, and `prefers-reduced-motion` respected).
@@ -32,28 +32,12 @@ Build me a **website for my retro arcade bar, with a playable mini-game as the h
**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
35
+
**When the site is ready, publish it to Spacefast:**
36
36
37
37
1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
38
-
2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
49
-
4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
58
-
59
-
**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
38
+
2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
39
+
3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
40
+
4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
41
+
5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
42
+
43
+
If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
Copy file name to clipboardExpand all lines: recipes/astro-zero/meta.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
"vertical": "Developers & integrations",
6
6
"tech": "Astro + Spacefast Zero",
7
7
"runtime": "zero",
8
-
"summary": "A prerendered Astro blog whose every post carries realtime comments and emoji reactions from a Spacefast Zero capsule, published as one space.",
8
+
"summary": "Publish an Astro blog with live comments and reactions powered by Spacefast Zero.",
0 commit comments