Internet Starter

Scaffold Next.js, FastAPI, or fullstack starters.

Skill metadata

Source	Bundled (installed by default)
Path	skills/software-development/internet-starter
Version	1.1.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	web, nextjs, fastapi, scaffold, starter, internet, fullstack
Related skills	plan, ship-web-service, popular-web-designs, git-local-workflow

Reference: full SKILL.md

信息

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Internet Starter

Create a minimal internet-project skeleton: Next.js (TS), FastAPI, or fullstack (apps/web + apps/api). Does not deploy. Stops at a runnable local app with a /health (or /api/health) check.

When to Use

• User asks to start a website, landing page, SaaS shell, or JSON API
• You need a clean folder with deps, README, and health endpoint
• Before wiring auth/billing/deploy (those are later skills)

Prerequisites

• Next / fullstack web: Node.js 20+ and npm
• FastAPI / fullstack api: Python 3.11+ and pip
• Prefer CLI: vibeos project new <preset> <path> (wraps this script)

How to Run

vibeos project new next ./my-app
vibeos project new fastapi ./my-api
vibeos project new fullstack ./my-saas
# or:
python3 scripts/scaffold.py next ./my-app

If the skill path is unknown, search with search_files for internet-starter/scripts/scaffold.py.

Quick Reference

Preset	Command after scaffold	Health URL	Free-port check
next	npm install && npm run dev	http://127.0.0.1:3000/api/health	vibeos project servers --free 3000
fastapi	venv + uvicorn app.main:app --reload	http://127.0.0.1:8000/health	vibeos project servers --free 8000
fullstack	run both apps (see README)	web :3000 + api :8000	both --free checks

Procedure

1. Confirm target directory is empty (or does not exist).
2. Run vibeos project new / scaffold.py for the chosen preset.
3. Install dependencies with terminal.
4. Before starting a server: vibeos project servers --free <port> — if busy, reuse the existing process (do not start a duplicate).
5. Start the dev server in the background if the user wants a live check.
6. Confirm: vibeos project servers --expect <port> --health.
7. Optional look: load popular-web-designs template tokens into the SPA.
8. Continue with skill ship-web-service for packs, browser smoke, deploy.

Pitfalls

• Do not scaffold into a non-empty directory — the script refuses.
• Do not invent a custom monorepo layout unless asked; use fullstack preset.
• Prefer read_file / patch after scaffold; do not rewrite the whole tree.
• Secrets belong in .env copied from .env.example, never committed.
• Never start a second server on a listening port.

Verification

• Health endpoint returns JSON with "status": "ok".
• vibeos project servers --expect <port> --health exits 0.
• README in the new project lists the exact run commands used.