How do I get the Brain to build a creative, high-quality website?
Ask the Brain to build a new site and describe the business, audience and purpose. Codus includes a website-build workflow: introduced in 0.2.178, with explicit prerequisite reads in 0.2.179 and shared branding, search and conversion checks in 0.2.181. It is intended to produce a considered design with reviewed pages, rather than guarantee identical results from every prompt.
What to include in the request
Give the Brain the real business facts, any existing brand assets, the people the site serves and the action visitors should take. Say whether it may invent clearly labelled demonstration content and generate images. Name any budget, image-source restrictions and deployment permission. Real requirements are useful; you do not need to remove every constraint to get a distinctive result.
For example: "Build a website for my body repair business in Ipswich. Use these verified details. Explore a distinctive visual direction, generate suitable images within my budget, and label any demonstration content. Show me the reviewed site before deployment."
What the Brain and builders should do
- Read the actual design, brand, copy, research and delegation instructions before choosing the visual direction. Loading the main playbook does not automatically load its dependencies.
- Establish business facts, search intent, page routes and page briefs. Explore seven visual directions and use the concept-selection step before writing the design agreement.
- Build a shared foundation: typography, colours, components, content and images, plus the logo, favicon, icons and social share image.
- Give each quadrant its own complete brief. Each builder reads the required skills in its own context and uses the shared foundation.
- Check every page at phone, desktop, wide-screen and known user sizes, including working contact actions, headings, metadata and links. Incomplete builder reports block the merge check.
- Obtain separate independent design and search/conversion reviews before calling the site complete. Review notes and internal design instructions stay out of public pages.
The Brain should explain each stage and report missing prerequisites. If it says a required skill is missing, it should check the installed locations and bundled copy, then name the missing file; it should not invent a substitute. Core website search and branding skills do not require an optional paid SEO pack.
Images, facts and cost
The workflow asks for the strongest available model and high reasoning effort, but actual model availability and provider charges still apply. Generated images require an available image tool and the appropriate connected service. A coding-agent subscription is not proof that an image API is connected.
Demonstration content must be distinguished from verified facts. Customer reviews, qualifications and other business proof must not be fabricated. Later factual changes can go through the content and image records; a visual redesign is only needed when the change actually affects the design.
How do I know it is ready?
The Brain reports the preview, completed reviews, remaining demonstration material and any unresolved inputs. Review approval is not deployment permission. After an authorised deployment, the live site needs its own checks. Cloning an existing product and rebuilding an existing site use their respective workflows.