CODEE PROMPT SUPPORT
CLIENT WELCOME GUIDE

What you bought
- A prompt-driven customization lane for text, visuals, layout, page expansion, and front-end polish.
- For custom sites, Codee starts with a 3-page launch shell and expands the site by prompt.

The 3-page launch shell
- Page 1: Home / primary message
- Page 2: Offer, service, mission, or product page
- Page 3: Contact, booking, intake, or action page

How to work with Codee
- Save one prompt per file.
- Keep each prompt focused on one pass or one outcome.
- Add any supporting images, screenshots, PDFs, or copy in the same folder.
- Say what should change and what should stay untouched.

Best starting modes
- Selected demo anchor: pick a demo family and let Codee rebrand the first 3 pages from it.
- Fresh prompt shell: start from your own description and let Codee build the first 3 pages cleanly.
- Canva/reference anchor: upload a Canva export, screenshot, or reference pack and let Codee match the mood.

Good prompt example
- Update the homepage hero for Made For This.
- Keep the current signup logic.
- Replace the headline with "Printable systems for calmer family routines."
- Use the uploaded kitchen checklist image in the hero card.
- Warm the colors slightly and make the main CTA stronger.
- Deploy if the change stays front-end only.

Allowed scope
- Text rewrites
- Visual swaps
- Image placement
- Section order
- Theme, font, and color direction
- CTA emphasis
- New front-end pages inside the current site system

Blocked without scoped approval
- Payment changes
- Auth changes
- Secret handling
- Infrastructure edits
- Open-ended backend rewrites

Shift options
- 2-hour daily support window
- 4-hour production block
- 12-hour sprint shift

What happens after a prompt is applied
- Codee applies the safe changes
- deploys when approved or allowed
- sends a summary email
- includes suggestions for the next pass