This is a generated static preview.
\n \n\n```\n\nThis is ideal for quick review loops because there is no repository, no DNS, no build pipeline, and no app server.\n\nIf you are using PreviewShip, the upload flow is built for this kind of artifact:\n\n[Publish AI-generated HTML online](https://previewship.com/guides/publish-ai-generated-html)\n\nIf Claude Code or another local coding agent generated a file in your workspace, the command line can be faster than using a browser UI.\n\nFor example:\n\n```\nnpx previewship deploy ./report.html\n```\n\nOr, if you want a machine-readable result for scripting:\n\n```\nnpx previewship deploy ./report.html --json\n```\n\nA CLI-based workflow is useful when you repeatedly generate variations:\n\n```\nnpx previewship deploy ./experiments/pricing-page-v3.html\nnpx previewship deploy ./reports/weekly-growth.html\nnpx previewship deploy ./demos/onboarding-flow.html\n```\n\nThe important thing is that the deployed file or folder should already be browser-ready.\n\nFor a built frontend project, that usually means:\n\n```\nnpm run build\nnpx previewship deploy ./dist\n```\n\nThe exact output folder depends on your framework:\n\n``` php\nVite -> dist/\nAstro -> dist/\nNext.js -> out/ if using static export\nSvelteKit -> build/ depending on adapter\n```\n\nIf you are working inside Claude Code, Cursor, or another agentic coding tool, you can also make publishing part of the agent workflow.\n\nA typical prompt can be:\n\n```\nBuild the static preview, deploy the browser-ready output, and give me the public URL.\n```\n\nThis works best when the tool has a clear deployment command or MCP integration available.\n\nFor PreviewShip, the MCP docs are here:\n\nThat kind of setup is useful because the agent can:\n\nYou still need to be explicit about what should be deployed. If the agent built a Vite app, ask it to deploy `dist/`\n\n, not the raw source directory.\n\nBefore sending the preview to someone else, check these details:\n\n`