How do I install the Build Deploy skill?

Run npx skillmds@latest add nirholas/build-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Build Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Build Deploy?

nirholas (@nirholas) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build Deploy by nirholas — Agent Skill

Name: Build Deploy
Author: nirholas

Build Deploy

Build, deploy, and configure the 3D viewer app. Use when: running dev server, building for production, deploying to Vercel, configuring CORS, editing vercel.json routes, managing static assets, or troubleshooting build issues.

nirholas acc61fa 3.5 KB Updated Sep 17, 2026

File contents

Build & Deploy

When to Use

Starting development server or troubleshooting it
Building for production
Deploying to Vercel
Configuring CORS, routes, or caching
Managing static assets in public/
Fixing build errors or dependency issues

Commands

Command	Purpose
`npm install`	Install dependencies
`npm run dev`	Vite dev server on port 3000
`npm run build`	Production build → `dist/`
`npm run clean`	Remove `dist/` contents
`npm run deploy`	Build + `vercel --prod` with local config
`npm version <patch\|minor\|major>`	Bump version, auto-pushes via `postversion`

Vite Configuration

Config: vite.config.js

Two build targets switched via TARGET env var:
- TARGET=app (default) → multi-page app in dist/ (entries: index.html, features.html, embed.html, agent-home.html, agent-embed.html)
- TARGET=lib → self-contained <agent-3d> web component in dist-lib/ (ESM + UMD, three.js bundled)
JSX configured for vhtml: jsxFactory: 'vhtml', jsxFragment: '"div"'
Dev server has a vercel-rewrites middleware that mirrors Vercel routing for /login, /register, /dashboard, /studio, /widgets, /docs/widgets, /agent, /agent/:id, /agent/:id/embed
vite-plugin-pwa emits the service worker + manifest
Static assets: public/ folder copied to build output

Vercel Deployment

Config: vercel.json

Key routes:

/assets/* — Cached 1 week (max-age=604800)
/.well-known/* — Cached 1 day, serves from public/.well-known/
/robots.txt, /sitemap.xml — Served from public/
/avatars/* — Served from public/avatars/

Domain: three.ws

CORS Configuration

Config: cors.json

Allowed origins:

https://three.ws/ and subdomains
http://localhost:* / https://localhost:*
Specific partner domains

Static Assets

public/
├── avatars/     → Default 3D model files (GLB)
├── .well-known/ → Domain verification files
├── robots.txt   → Search engine directives
└── sitemap.xml  → Site map

Procedure

Local Development

npm install
npm run dev
Open http://localhost:3000

Production Deploy

npm run build — verify no build errors
npm run deploy — builds and deploys to Vercel
Verify at three.ws

Adding Static Assets

Place files in public/ (copied as-is to build output)
If they need caching rules, add a route in vercel.json
If they need CORS access, verify origins in cors.json

Troubleshooting

Port 3000 in use: Kill existing process or edit package.json dev script port
Build fails on Three.js imports: Check three version in package.json matches CDN paths in viewer.js
CORS errors: Check cors.json for allowed origins
Assets 404 after deploy: Verify route patterns in vercel.json

---name: build-deploydescription: Build, deploy, and configure the 3D viewer app. Use when: running dev server, building for production, deploying to Vercel, configuring CORS, editing vercel.json routes, managing static assets, or troubleshooting build issues.---# Build & Deploy## When to Use- Starting development server or troubleshooting it- Building for production- Deploying to Vercel- Configuring CORS, routes, or caching- Managing static assets in `public/`- Fixing build errors or dependency issues## Commands| Command | Purpose || ----------------------------------- | ------------------------------------------- || `npm install` | Install dependencies || `npm run dev` | Vite dev server on port 3000 || `npm run build` | Production build → `dist/` || `npm run clean` | Remove `dist/` contents || `npm run deploy` | Build + `vercel --prod` with local config || `npm version <patch\|minor\|major>` | Bump version, auto-pushes via `postversion` |## Vite Configuration**Config**: [`vite.config.js`](../../../vite.config.js)- Two build targets switched via `TARGET` env var: - `TARGET=app` (default) → multi-page app in `dist/` (entries: `index.html`, `features.html`, `embed.html`, `agent-home.html`, `agent-embed.html`) - `TARGET=lib` → self-contained `<agent-3d>` web component in `dist-lib/` (ESM + UMD, three.js bundled)- JSX configured for vhtml: `jsxFactory: 'vhtml'`, `jsxFragment: '"div"'`- Dev server has a `vercel-rewrites` middleware that mirrors Vercel routing for `/login`, `/register`, `/dashboard`, `/studio`, `/widgets`, `/docs/widgets`, `/agent`, `/agent/:id`, `/agent/:id/embed`- `vite-plugin-pwa` emits the service worker + manifest- Static assets: `public/` folder copied to build output## Vercel Deployment**Config**: `vercel.json`Key routes:- `/assets/*` — Cached 1 week (`max-age=604800`)- `/.well-known/*` — Cached 1 day, serves from `public/.well-known/`- `/robots.txt`, `/sitemap.xml` — Served from `public/`- `/avatars/*` — Served from `public/avatars/`**Domain**: [three.ws](https://three.ws/)## CORS Configuration**Config**: `cors.json`Allowed origins:- `https://three.ws/` and subdomains- `http://localhost:*` / `https://localhost:*`- Specific partner domains## Static Assets```public/├── avatars/ → Default 3D model files (GLB)├── .well-known/ → Domain verification files├── robots.txt → Search engine directives└── sitemap.xml → Site map```## Procedure### Local Development1. `npm install`2. `npm run dev`3. Open `http://localhost:3000`### Production Deploy1. `npm run build` — verify no build errors2. `npm run deploy` — builds and deploys to Vercel3. Verify at [three.ws](https://three.ws/)### Adding Static Assets1. Place files in `public/` (copied as-is to build output)2. If they need caching rules, add a route in `vercel.json`3. If they need CORS access, verify origins in `cors.json`## Troubleshooting- **Port 3000 in use**: Kill existing process or edit `package.json` dev script port- **Build fails on Three.js imports**: Check `three` version in `package.json` matches CDN paths in `viewer.js`- **CORS errors**: Check `cors.json` for allowed origins- **Assets 404 after deploy**: Verify route patterns in `vercel.json`

Frequently asked questions