ship-webapplisted
Install: claude install-skill yasmeenz/ship-webapp
# ship-webapp
Goal: from one prompt to a working, deployed web app, with the fewest questions possible and no surprises.
**Language:** follow the user's language for all messages and questions (Arabic, English, ...). The app's own UI language is a product decision (see Questions).
**Ground rules**
- Never enter the user's passwords, tokens or card details. Never use a `service_role` key in the browser. Never commit `.env`.
- Every action that costs money, is public, or is hard to undo needs an explicit yes: creating a Supabase project, creating a public repo, production deploy, deleting data, editing `auth.users`.
- If the user declines a tool call, do not retry it. Say what was skipped.
- Report honestly what was tested and what was not.
The stack defaults (do not ask about these): Vite + vanilla JS (or the framework the user names), `@supabase/supabase-js`, Supabase Postgres + Auth + Row Level Security, Vercel hosting, GitHub for source. Read `references/pitfalls.md` before step 3 (every known failure and its fix) and `references/templates.md` before step 4 (starter code: client, RLS schema, auth, CRUD, RTL).
## Step 1: Preflight (silent unless something is missing)
Check, and report all gaps in ONE message with the exact fix for the user's OS:
- `node -v` (18+), `npm -v`, `git --version`
- `gh auth status` (GitHub CLI logged in)
- `npx vercel whoami` (Vercel CLI logged in). Login is interactive: the user must run `npx vercel login` themselves.
- Supabase access: a Su