Don’t face the blank box.
Remix a starter.

Build a booking page for my dog-grooming business with a price list, opening hours, and a booking form that asks for the dog's name, size, service, and a preferred day and time

# spec.md — Service booking page (STARTER — frozen) Frozen 2026-10-24 as a starter. Remix it: the rules below are a worked example of a frozen spec, not your project's law until you adopt them. ## The goal and the rules (the spec) A one-page booking site for a small service business (the example is a dog groomer; the shape fits any appointment business). A visitor can: (1) see the services and their prices, (2) see opening hours, (3) send a booking request with their name, contact, the service, and a preferred day and time. The owner confirms bookings by hand — the page takes requests, it does not promise slots it cannot see. Acceptance: - Every service named on the page has a price next to it. - The booking form refuses to send with an empty required field and says which field, in plain words. - The page works on a phone at 390px wide with no sideways scrolling. - No invented prices, hours, or services — placeholders are labelled placeholders. ## Must never happen - No online payment in v1 (requests first; money later, deliberately). - No claim that a booking is confirmed — the page says "request sent". - No visitor data stored anywhere except the owner's inbox/form tool. ## How a new AI resumes this project This file travels with state.md. A new AI reads both, then states back (1) the goal and acceptance criteria, (2) the exact stopping point, (3) the single next action — before doing any work.

# state.md — Service booking page (STARTER) Updated 2026-10-24. The starter's stopping point: nothing is built yet; this file and spec.md are the whole project. ## Where it stands - The brief is frozen (spec.md). No code exists. - Prices, hours, and the service list in the seed are EXAMPLE values — replace them with the real business's before building. ## The next single action Run the seed sentence through /start's six questions with the real business's details, then build the smallest page that passes the spec. ## Decisions on record - Requests, not confirmed bookings (no calendar integration in v1). - One page, no accounts, no logins. ## Failed approaches — do not retry - (none yet — the starter has no build history) ## Dependencies and constraints - The owner's existing inbox or form tool receives the requests. - The page must be hostable as static files.

Make a portfolio site for a photographer with a gallery of their best work, a short about section in their own words, prices for the three kinds of shoots they offer, and one clear contact button

# spec.md — Portfolio (STARTER — frozen) Frozen 2026-10-24 as a starter. Remix it: the rules below are a worked example of a frozen spec, not your project's law until you adopt them. ## The goal and the rules (the spec) A portfolio site whose job is exactly one thing: a visitor sees the work, believes it, and can reach the owner in one tap. The gallery is the homepage — no landing-page preamble before the pictures. Acceptance: - The first screen shows actual work, not a hero slogan. - Every gallery image has a plain caption (what, where, when). - One contact action, the same on every page, reachable in one tap. - Images are the owner's own; any placeholder image is labelled as a placeholder, never presented as the owner's work. - The page loads fast on a phone connection: gallery images are sized for the web, not uploaded raw from the camera. ## Must never happen - No stock photos presented as the owner's work. - No invented clients, testimonials, or awards. - No contact form that sends to an address nobody reads. ## How a new AI resumes this project This file travels with state.md. A new AI reads both, then states back (1) the goal and acceptance criteria, (2) the exact stopping point, (3) the single next action — before doing any work.

# state.md — Portfolio (STARTER) Updated 2026-10-24. The starter's stopping point: nothing is built yet; this file and spec.md are the whole project. ## Where it stands - The brief is frozen (spec.md). No code exists. - The gallery contents, prices, and the about text are EXAMPLE slots — the owner's real work and words replace them before building. ## The next single action Run the seed sentence through /start's six questions with the owner's real details, then build the smallest site that passes the spec. ## Decisions on record - Gallery first, words second — the work is the argument. - One contact action everywhere, never a menu of five. ## Failed approaches — do not retry - (none yet — the starter has no build history) ## Dependencies and constraints - The owner supplies the images and the about text. - The site must be hostable as static files.

Build a small store site for a farm that sells jars of jam and honey, with the products and prices on one page, a note about local pickup and shipping, and buy buttons that use a checkout link for each product

# spec.md — Small store (STARTER — frozen) Frozen 2026-10-24 as a starter. Remix it: the rules below are a worked example of a frozen spec, not your project's law until you adopt them. ## The goal and the rules (the spec) A one-page storefront for a maker selling a handful of products (the example is a farm stand: jam and honey). A visitor can see every product with its price, understand pickup vs. shipping in one read, and buy through a checkout link that already exists (a payment-link service the owner already has) — this page is the shelf, not the register. Acceptance: - Every product on the page has a real price and a working buy link, or is plainly marked "sold out" / "not on the shelf yet". - Pickup and shipping terms are stated once, in plain words, above the products — not buried at checkout. - No product is shown that the owner does not actually sell. - The page works on a phone at 390px wide. ## Must never happen - No invented products, prices, or stock claims. - No cart or checkout built into the page in v1 — the owner's existing checkout links do the money part. - No "order confirmed" language anywhere on this page; confirmation belongs to the checkout service. ## How a new AI resumes this project This file travels with state.md. A new AI reads both, then states back (1) the goal and acceptance criteria, (2) the exact stopping point, (3) the single next action — before doing any work.

# state.md — Small store (STARTER) Updated 2026-10-24. The starter's stopping point: nothing is built yet; this file and spec.md are the whole project. ## Where it stands - The brief is frozen (spec.md). No code exists. - Products, prices, and pickup/shipping terms in the seed are EXAMPLE values — the owner's real shelf replaces them before building. ## The next single action Run the seed sentence through /start's six questions with the owner's real products, then build the smallest page that passes the spec. ## Decisions on record - The page is the shelf; an existing checkout-link service is the register. No cart in v1. - Terms stated once, above the products. ## Failed approaches — do not retry - (none yet — the starter has no build history) ## Dependencies and constraints - The owner has (or opens) a checkout-link service account. - The page must be hostable as static files.