Tell your AI what to build.
Then put it online.

Build and publish this as a Small Static Site v1 (small-static-site/1).

The platform accepts only an already-built static artifact. Run dependency installation and build commands locally. Never ask the platform to run source code, npm, a build script, a container, or an application process.

Choose the smallest authoring approach:
1. Default to semantic HTML, CSS, and JavaScript in site/.
2. Use React + TypeScript + Vite only for meaningful browser-side interaction and state.
3. Preserve Next.js, Vue/Vite, or Astro only when the project produces fully static dist/ output. Next must use output: "export"; Astro must use static output.

Supported framework values are exactly: plain, react-vite, next-static, vue-vite, astro-static.

Create small-site.json at the project root. It is a closed manifest: do not add keys. Use spec "small-static-site/1", a 3–48 character lowercase slug for name, basePath "/", no public build variables, and quality.accessibility "WCAG2.2-AA".

For a plain site, use build { "profile": "static-files", "source": "site", "output": "site" }. Include site/index.html and site/404.html.

For a framework site, use build { "profile": "node-static", "runtime": "nodejs-24.18.0", "packageManager": "npm-11.16.0", "install": "npm ci", "command": "npm run build", "output": "dist" }. Build locally and inspect dist/ before publishing.

Use file routing with 404.html by default. Only React/Vite or Vue/Vite may use SPA routing with fallback index.html. Self-host scripts, styles, images, and fonts. Small Site serves the finished site with style-src 'self' and does not allow 'unsafe-inline'. Put all CSS in self-hosted .css files. Never create style attributes or style elements, mutate element.style, use CSS-in-JS, or use a library that injects runtime style elements. Use CSS classes for visual states. External scripts and styles, inline event handlers, form submissions, service workers, WebAssembly, source maps, secrets, private URLs, SSR, API routes, databases, filesystem writes, background jobs, WebSockets, Dockerfiles, and executable files are prohibited.

Declare only exact public HTTPS origins genuinely needed in network.connect, images, media, fonts, or frames. Use empty arrays otherwise. The platform compiles these declarations into Content Security Policy; do not provide raw headers.

Create small-site-upload.zip with no wrapper directory. Its root must contain exactly small-site.json plus the declared site/ or dist/ output. Do not include source files, node_modules, lockfiles, caches, symlinks, nested archives, or files outside the output directory. Limits: 30 MiB ZIP, 25 MiB unpacked, 2,000 output files, and 5 MiB per file.

Before finishing:
- run the local build when applicable;
- verify index.html, routing, local links, assets, metadata, responsive layout, keyboard access, visible focus, reduced-motion behavior, and content accuracy;
- if Small Site tools are available, call small_site_check and fix every reported problem, then call small_site_publish with the project path and one stable idempotency key;
- omit siteId unless the customer explicitly selected a different existing site: the publish tool reads small-site.json, updates the owned site with the matching slug, or creates it from the manifest when absent, subject to the account's billing and active-site limit;
- otherwise produce the validated ZIP for dashboard upload and explain that it contains static output only.

Do not claim the site is published until the publish tool or dashboard returns an active deployment and stable URL.