← ClaudeAtlas

publish-sitelisted

Use when the user asks to publish, deploy, ship, launch, create a preview URL, connect a domain, or redeploy a previously recorded build.
wrg32786/aigent-design-system · ★ 4 · Web & Frontend · score 77
Install: claude install-skill wrg32786/aigent-design-system
# Publish Site Publishing is an agent-run production step. There is no separate Ship or Studio UI. ## Before publishing Inspect the actual project and confirm: - the intended public entry exists; - the user has authorized the target provider/domain; - public export contains no credentials, private keys, or private working state; - the project is in an intentional source state; - production verification is passing when the user expects a verified deployment. A screenshot, command proposal, or generated mockup is not a deployment. Completion requires a provider URL or an explicit local export path. ## Provider ladder Use the first route that fits: 1. **Local export** — no account, handoff bundle, custom host, or offline review. 2. **Netlify** — simple static preview/production deployment. 3. **Vercel** — linked preview/production project and direct domain aliasing. 4. **Cloudflare Pages** — Cloudflare-hosted static deployment and preview branches. Do not add a hosting SDK when the official CLI already provides the required operation. ## Flow ```text CHECKPOINT identify the exact source state being shipped EXPORT traverse only referenced public dependencies PREFLIGHT run Resolve against the local build when verification matters DEPLOY use the selected official provider CLI VERIFY wait for the URL and inspect production SEE prepare Vision captures when requested RECORD store URL, provider, source state, artifact, QA, and history locally ``` ## CLI