Nate's Adventures PubGen experiments, app pages, and weird little wins.
Copy Instructions For Another Chat

You are working on an app launcher project that is deployed from GitHub to Vercel.

Use the project folder, Git remote, and deployment URL from the current chat or terminal. Do not assume or hard-code a local path, Vercel project, or production URL.

Expected GitHub repo for Nate's Adventures:
https://github.com/pubgen-ai/natesadventures.git

Verify the repo before editing:

- First run git rev-parse --show-toplevel.
- If the current folder is not a Git repo, do not stop yet. Locate an existing checkout for the expected repo or clone it, then cd into that repo.
- To locate an existing checkout, search likely workspace folders for a Git remote containing pubgen-ai/natesadventures.
- If no checkout exists and GitHub access is available, clone https://github.com/pubgen-ai/natesadventures.git into an appropriate workspace folder and cd into it.
- After cd into the candidate repo, run git remote -v.
- The push remote should point to github.com/pubgen-ai/natesadventures.
- If no matching checkout can be found or cloned, stop and report the exact missing repo access/path.
- If the remote exists but does not match, stop and report the mismatch instead of pushing.

Goal:

Add or update one complete app inside the launcher, commit it to the GitHub repo, deploy it with the existing workflow, and verify that the production URL works.

First, discover the project shape:

1. Run:
   pwd
   git remote -v
   git status --short
   rg -n "const apps = \\[" .

2. Read the project README and package scripts.

3. Find the launcher file and the app registry before editing. In this project the launcher is usually the page with a JavaScript array named apps.

Expected structure:

- apps/ is where individual apps belong.
- Each app gets exactly one folder inside apps/.
- The app's main page should usually be apps/{app-slug}/index.html.
- App assets, CSS, JS, data, runtime files, and helper scripts stay inside apps/{app-slug}/ unless a root API route or config entry is truly required.
- The launcher registry gets one app card pointing to the app folder.

Scope rules:

- Do not put new app files in the repo root.
- Do not put new app files inside the launcher folder.
- Do not mix a new app into an existing app folder unless the user explicitly says it belongs there.
- Do not change, delete, or rename existing app folders, previews, tests, API routes, Vercel config, package scripts, or launcher cards unless the current task requires it.
- Do not replace a working app with a placeholder, map page, iframe shell, or "coming soon" page. The deployed app must actually run.
- Do not leave references to file://, localhost, a private local folder, or an uncommitted source checkout.
- Do not commit secrets, .env files, .vercel state, node_modules, scratch screenshots, test output, or unrelated generated files.

To add a new app:

1. Choose a lowercase hyphenated slug:
   apps/my-new-app/

2. Put the complete app in that folder:
   apps/my-new-app/index.html
   apps/my-new-app/assets/
   apps/my-new-app/scripts/
   apps/my-new-app/data/

3. If the app needs server/API behavior, add the smallest root API adapter or config change required by the existing deployment pattern. Keep shared API changes narrow and document why they are needed.

4. Create or capture a real preview image of the running app:
   apps/my-new-app/assets/preview.png

5. Add a clear link in the app back to the launcher:
   href="/"
   label like "All Adventures" or "Back to launcher"

6. Update the launcher app registry with exactly one new app object.

Visual launcher requirements:

- The new app must appear as a visible card in the launcher.
- The launcher card must show the app title, description, tags, and preview image.
- Clicking the launcher card must open /apps/my-new-app/.
- The app page must include a visible "All Adventures" or "Back to launcher" link near the top of the page.
- That link must point to "/" and return to the launcher.
- Verify both directions in the browser: launcher to app, then app back to launcher.

Use this card pattern:

{
  title: "My New App",
  description: "Short plain-English explanation of what the app does.",
  href: "/apps/my-new-app/",
  image: "/apps/my-new-app/assets/preview.png",
  status: "live",
  statusLabel: "App",
  featured: false,
  tags: ["Useful tag", "Another tag"],
  included: [
    {
      title: "Main Page",
      description: "The main page for this app.",
      href: "/apps/my-new-app/"
    }
  ]
}

Card rules:

- The app card represents the app.
- Inner pages are listed under included; they are not separate app cards.
- Do not label inner pages as Live, Demo, Prototype, or Queued.
- href values should be deployment-safe site paths, usually beginning with /apps/...
- image must point to a committed image that loads from the deployed site.

Verification before commit:

1. Run the launcher regression test if it exists:
   npm run test:launcher

2. Run any app-specific tests or smoke scripts that exist.

3. Start the local dev server using the repo's existing script, usually:
   npm run dev

4. In the browser, verify:
   - the launcher opens
   - the new card appears
   - the card opens the app
   - the preview image loads
   - the app's CSS/JS/assets load without 404s
   - the app's main workflow works enough to prove it is not a placeholder
   - the app has a working link back to the launcher

Commit and push:

1. Review:
   git status --short
   git diff --stat
   git diff

2. Stage only intentional files. Prefer explicit paths, for example:
   git add apps/my-new-app "Adventures App/index.html"

   Also stage package files, root API files, or Vercel config only if the app truly needs them.

3. Commit with a clear message and push to the current branch/remote.

Deploy and prove:

1. Use the project's existing deploy workflow. Do not invent a new deployment path.

2. Verify the deployed launcher and deployed app URL, not just local files.

3. Capture or report proof:
   - commit hash
   - pushed branch
   - deployed launcher URL
   - deployed app URL
   - verification commands run
   - any tests skipped and the exact reason

Stop and report the exact blocker if GitHub push, Vercel deploy, login, 2FA, missing secrets, payment, or captcha is required. Do not claim the app is added until it is committed, pushed, deployed, and verified.
Nate's Adventures

A launch board for complete apps and useful pages worth keeping close. Related pages stay bundled inside their app, so the next projects can drop in without mixing their pieces together.
0 Total apps
0 Ready apps
0 Pages