Files
TechNomadCodeandClaude Opus 5.5 cb7956e66a Fix six workflow breaks found while running the AI App Starter
Lessons from running the starter on promptquick.ai for three weeks:

- Email: idempotency keys are unique per environment, since staging and
  production can share one provider account and their job IDs overlap.
- Background jobs: the scheduler's own run history is cleaned on a
  schedule, so it can't creep toward a free database plan's limit.
- Ship a .gitattributes with LF line endings and the common binary
  types named, so the generated-file drift checks pass on Windows;
  SETUP.md and the README list it.
- Build: a risky slice is marked done but keeps its acceptance criteria
  until its independent review is settled; the Now block notes the
  pending review.
- Set up: the owner's steps are click by click, in a working order,
  name the exact site and environment, and say when a redeploy is needed.
- Set up: AGENTS.md stays under about 100 lines, not counting blocks
  tools add themselves; the starter's own text already left little room
  under 80.

- READMEs: the staging and production pipeline is tested on a live
  site, and the review covers sign-in, payments, database changes and
  live data, as the starter does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 09:34:14 +02:00
..

My app

This project was started with the AI App Starter. Open your AI coding agent in this folder and ask what's next?

During stage 3 the agent replaces this file with your app's own README: quick start, commands and environments.