Builder guide
Write a brief with the project type, audience, brand, outcome, required pages, content direction, media requirements, and constraints.
Documentation
Documentation should make the platform easier to use, troubleshoot, and deploy without hiding the difference between an available feature and a future one.
Write a brief with the project type, audience, brand, outcome, required pages, content direction, media requirements, and constraints.
Follow the journey from specification and design decisions through validation, preview, ZIP creation, and delivery.
Use email, Google, GitHub, or phone flows when configured. Keep redirect URLs, confirmation settings, and provider credentials in the right environment.
Verify domains, environment variables, Supabase configuration, Stripe mode, webhooks, cache, SSL, and server logs before calling a deployment live.
State what you are building, who it serves, the pages it needs, the desired action, the visual direction, the language, and anything the system must not invent.
Open the preview. Check navigation, page content, mobile layout, image relevance, legal copy, forms, and links. A ZIP is a delivery artifact, not proof that every external service is configured.
Use the Help Center for common questions or contact the team with the route, phase, and visible error message. Never include private keys in a support request.