6 step workflow
Build a small website from scratch
Plan requirements, generate code, test, and publish carefully.
Workflow progress
Check off steps as you finish them. Progress stays in this browser.
Step 1
Write a feature brief
Why use it
AI can turn a vague idea into scoped requirements.
Prompt
Turn this website idea into a one-page brief with pages, data, SEO, and privacy needs.
Input example
A landing page for a local service
Output example
Implementation brief
What to watch
Keep the first release small and separate required features from later ideas.
Design the pages and content structure
Why use it
A clear information hierarchy reduces rework before coding begins.
Prompt
Create a mobile-first page outline for this brief with headings, calls to action, trust content, navigation, and empty or error states.
Input example
Approved implementation brief
Output example
A page-by-page content and component outline.
What to watch
Do not use fake testimonials, counters, logos, or urgency messages in the design.
Build the accessible frontend
Why use it
Repository-aware coding tools help implement small, reviewable changes in context.
Prompt
Implement this page outline using the existing stack and design tokens. Preserve semantic HTML, keyboard access, responsive layout, and reduced motion.
Input example
Repository, component outline, and acceptance criteria
Output example
Reviewable components and pages that run locally.
What to watch
Review generated code and never place secrets in browser bundles.
Add metadata, privacy, and error states
Why use it
Production readiness requires more than the happy-path page.
Prompt
Audit the site for title, description, canonical, social metadata, robots, sitemap, privacy disclosure, form errors, empty states, and 404 behavior.
Input example
Working local site
Output example
A completed production-readiness checklist and fixes.
What to watch
Only claim privacy or security properties that the implementation actually provides.
Step 5
Test core flows
Why use it
Automated and manual checks catch regressions across browsers and screen sizes.
Prompt
Create focused tests for navigation, forms, keyboard use, mobile layout, metadata, and the main conversion path. Fix failures before deployment.
Input example
Acceptance criteria and working site
Output example
Passing checks plus a short manual QA record.
What to watch
Do not treat a successful build as proof that user flows work.
Step 6
Deploy and verify production
Why use it
Production URLs, redirects, environment variables, and caching can differ from local behavior.
Prompt
Prepare a deployment checklist covering environment variables, custom domain, HTTPS, redirects, robots, sitemap, analytics privacy, rollback, and post-deploy smoke tests.
Input example
Passing build and hosting configuration
Output example
Verified production deployment with rollback notes.
What to watch
Verify the live domain after deployment and keep a known-good rollback artifact.