Build with an AI agent

Help me prepare my existing project for PhotonSpark Webhost using the guide below. Ask for the project requirements and deployment choice when missing. Inspect existing files before editing, preserve behavior and data, and do not invent supported flags or deployment options. Keep credentials out of code and prompts. Explain dashboard settings and test production behavior. Publishing, DNS changes, and destructive actions need my authorization. Report what passed and what remains unverified.

# Build with an AI agent

Give your coding assistant a public, inspectable deployment contract and a clear verification task.

Source: https://webhost.photonspark.com/docs/agents

## Start with the matching guide

Use Copy AI prompt on a guide to copy its contract and source URL. The Site starter panel creates a mode-specific prompt with its reference files. Agents that cannot render pages can read the plain-text endpoints below.

- [Documentation index for agents](https://webhost.photonspark.com/llms.txt)
- [Complete documentation as text](https://webhost.photonspark.com/docs/llms-full.txt)
- [Site templates and prompts](https://webhost.photonspark.com/docs/sites#starters)

## Add your project's requirements



```text
Prepare my existing project for PhotonSpark Webhost.
Read https://webhost.photonspark.com/docs/llms-full.txt first.
Deployment: Site / App / SparkTunnel (choose one)
Framework and version: ...
Repository branch: ...
Public hostname: app.example.com
Features to preserve: login, API routes, uploads, WebSockets, ...
Persistent data: ...
Inspect before editing. Explain the required structure and build/runtime commands.
Keep credentials out of the repository and this conversation.
Implement the smallest complete change and test production startup and real routes.
Report changed files, dashboard settings, validation results, and remaining limits.
Do not deploy, delete data, or change DNS until I authorize those actions.
```

## Ask for evidence, not just generated files

- Exact repository structure and selected Site build mode or App manifest.
- A lockfile and reproducible production build steps.
- Environment variable names and scopes, with placeholders for secrets.
- Local verification plus public-route checks after an authorized deployment.
- Known limitations, failed checks, and recovery considerations.