Skip to content

Commit ae66db9

Browse files
committed
Make recipe copy and demo outcomes truthful
1 parent 0117b0a commit ae66db9

162 files changed

Lines changed: 842 additions & 1496 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎recipes/2048/meta.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"slug": "2048",
55
"vertical": "Tools, apps & games",
66
"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.",
88
"order": 300,
99
"live_url": "https://2048.view.fast/",
1010
"setup_questions": [

‎recipes/2048/prompt.md‎

Lines changed: 7 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -32,28 +32,12 @@ Build me a **fully playable 2048 sliding-tile puzzle game** as a vanilla-JS app
3232
<script src="https://spacefast.com/badge.js" data-example="2048"></script>
3333
```
3434

35-
**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:**
3636

3737
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:
39-
```bash
40-
PUBLISH_ROOT=./site
41-
publish_files=()
42-
while IFS= read -r -d "" file; do
43-
relative=${file#"$PUBLISH_ROOT"/}
44-
publish_files+=(-F "files=@$file;filename=$relative")
45-
done < <(find "$PUBLISH_ROOT" -type f -print0)
46-
curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
47-
```
48-
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:
50-
```bash
51-
SPACEFAST_SPACE_ID=<saved-space-id>
52-
SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
53-
curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
54-
-F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
55-
"https://api.spacefast.com/v1/publish?wait=1"
56-
```
57-
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/).

‎recipes/app/meta.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"slug": "app",
55
"vertical": "Tools, apps & games",
66
"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.",
88
"order": 300,
99
"live_url": "https://app.view.fast/",
1010
"setup_questions": [

‎recipes/app/prompt.md‎

Lines changed: 6 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -64,28 +64,12 @@ browser (no backend, no accounts, all state in `localStorage`).
6464
<script src="https://spacefast.com/badge.js" data-example="app"></script>
6565
```
6666

67-
**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:**
6868

6969
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:
71-
```bash
72-
PUBLISH_ROOT=./dist
73-
publish_files=()
74-
while IFS= read -r -d "" file; do
75-
relative=${file#"$PUBLISH_ROOT"/}
76-
publish_files+=(-F "files=@$file;filename=$relative")
77-
done < <(find "$PUBLISH_ROOT" -type f -print0)
78-
curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
79-
```
80-
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:
82-
```bash
83-
SPACEFAST_SPACE_ID=<saved-space-id>
84-
SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
85-
curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
86-
-F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
87-
"https://api.spacefast.com/v1/publish?wait=1"
88-
```
89-
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.
9074

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/).

‎recipes/arcade/meta.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"slug": "arcade",
55
"vertical": "Local & small business",
66
"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.",
88
"order": 4,
99
"live_url": "https://arcade.view.fast/",
1010
"setup_questions": [

‎recipes/arcade/prompt.md‎

Lines changed: 9 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,14 @@ Build me a **website for my retro arcade bar, with a playable mini-game as the h
1414
- **On tap** — a rotating draft-beer list (name, brewery, style, ABV, price) plus a few house cocktails.
1515
- **Events** — a week of tournament nights and happy-hour specials with prizes.
1616
- **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.
1818
- A footer with social links and the address.
1919

2020
**Design & content notes:**
2121

2222
- 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.
2323
- 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.
2525
- 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.
2626
- No build step: a single `index.html` plus `styles.css`, `game.js`, and a tiny `ui.js`. Persist the high score in `localStorage`.
2727
- 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
3232
<script src="https://spacefast.com/badge.js" data-example="arcade"></script>
3333
```
3434

35-
**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:**
3636

3737
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:
39-
```bash
40-
PUBLISH_ROOT=./site
41-
publish_files=()
42-
while IFS= read -r -d "" file; do
43-
relative=${file#"$PUBLISH_ROOT"/}
44-
publish_files+=(-F "files=@$file;filename=$relative")
45-
done < <(find "$PUBLISH_ROOT" -type f -print0)
46-
curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
47-
```
48-
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:
50-
```bash
51-
SPACEFAST_SPACE_ID=<saved-space-id>
52-
SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
53-
curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
54-
-F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
55-
"https://api.spacefast.com/v1/publish?wait=1"
56-
```
57-
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/).

‎recipes/arcade/site/index.html‎

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,12 @@
1818
<link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 32 32'%3E%3Crect width='32' height='32' rx='6' fill='%230a0014'/%3E%3Ctext x='16' y='23' font-size='18' text-anchor='middle' fill='%23ff2db8' font-family='monospace'%3E%E2%96%B6%3C/text%3E%3C/svg%3E" />
1919
</head>
2020
<body>
21+
<aside
22+
aria-label="Example site"
23+
style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
24+
>
25+
Example site with fictional content. Forms are previews.
26+
</aside>
2127
<a class="skip-link" href="#main">Skip to content</a>
2228

2329
<header class="site-header">
@@ -415,6 +421,8 @@ <h2 class="section__title">Book the back room</h2>
415421
</ul>
416422
</div>
417423

424+
<p data-demo-note="true">Demo form. Nothing is sent or booked.</p>
425+
418426
<form class="book-form" id="bookForm" novalidate>
419427
<div class="field">
420428
<label for="bf-name">Your name</label>
@@ -438,9 +446,9 @@ <h2 class="section__title">Book the back room</h2>
438446
<label for="bf-notes">What's the occasion?</label>
439447
<textarea id="bf-notes" name="notes" rows="3" placeholder="Mike's 30th — wants a Galaga tournament"></textarea>
440448
</div>
441-
<button class="btn btn--primary btn--block" type="submit">Request a date</button>
449+
<button class="btn btn--primary btn--block" type="submit">Preview</button>
442450
<p class="book-form__success" id="bookSuccess" role="status" hidden>
443-
Got it — thanks! We'll email you within a day to lock in the room. 🕹️
451+
Preview complete. Nothing was sent.
444452
</p>
445453
</form>
446454
</div>

‎recipes/arcade/site/ui.js‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,10 +29,8 @@
2929
form.reportValidity();
3030
return;
3131
}
32-
var name = (form.elements.name && form.elements.name.value || "").trim();
3332
success.hidden = false;
34-
success.textContent = (name ? "Thanks, " + name + "! " : "Got it — thanks! ") +
35-
"We'll email you within a day to lock in the back room. 🕹️";
33+
success.textContent = 'Preview complete. Nothing was sent.';
3634
form.querySelectorAll("input, textarea, button").forEach(function (el) {
3735
if (el.type !== "submit") el.value = el.defaultValue || "";
3836
});

‎recipes/astro-zero/meta.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
"vertical": "Developers & integrations",
66
"tech": "Astro + Spacefast Zero",
77
"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.",
99
"order": 320,
1010
"live_url": "https://astro-zero.view.fast/",
1111
"setup_questions": [

‎recipes/astro-zero/prompt.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,4 +87,4 @@ sf publish dist --wait
8787

8888
Then check it live: load a post, leave a comment in a second browser window, and
8989
watch it appear in the first without a reload. Give me the live URL, the claim
90-
URL, and remind me to claim within 6 hours.
90+
URL, and tell me the claim deadline returned in the receipt and remind me to claim the Space to keep it.

0 commit comments

Comments
 (0)