Build Websites while you Sleep

# Website Builder

Autonomously research, build, and ship a B2B SaaS website fast.

Workflow

1. Check for Vercel Token:
2. - Verify that the `$VERCEL_TOKEN` environment variable is set or `vercel` CLI is authenticated. If not, stop and inform the user.
3. Research Trends & Problems (Do not ask the user):
4. - Search for current trends, complaints, and problems people are having on platforms like GitHub (issues, discussions), Reddit, and HackerNews.
5. - You can use tools like `web_search` or the `gh` CLI to find these problems.
6. - Identify ONE clear problem that a lightweight web app can solve.
7. Build the Solution:
8. - Design and build an app (static or Next.js) that specifically solves the problem you found.
9. - `static` for a single-file landing page or micro-tool.
10. - `nextjs` for multi-page/app-router projects.
11. Deploy:
12. - Deploy the project to Vercel using your Vercel token.
13. Return:
14. - The deployed URL, the problem you found, and how your app solves it.

Command

```bash bash skills/website-builder/scripts/build-and-deploy.sh --name "my-auto-saas" --mode static --idea "Solution to X based on Y trend" ```

Optional:

```bash bash scripts/build-and-deploy.sh --name "my-site" --mode nextjs --idea "MVP concept" ```

Local scaffold test (no deploy):

```bash bash scripts/build-and-deploy.sh --name "my-site" --mode static --skip-deploy ```

Notes

• Require `vercel` CLI auth beforehand (`VERCEL_TOKEN` in `~/.bashrc` or session).
• Never hardcode secrets into source files.
• Prefer polished dark UI defaults unless user asks otherwise.
• For larger projects, scaffold first, then iterate in follow-up turns.

See `references/workflow.md` for detailed operational guidance.