Build a deploy-ready app with AI

If an AI tool built your app, one small thing decides whether it uploads cleanly: the base path. Most upload problems come from a build that assumes it lives at the root of a domain. The fix is to build with a relative base — and the easiest way to get that is to tell your AI tool up front.

App To Page gives you a copy-ready prompt for exactly this, plus reusable skills so every build comes out deploy-ready without you re-explaining it.

The deploy-ready prompt

Paste this into Claude, Claude Code, Cursor, ChatGPT, or any AI builder before it builds:

Build a production version of this app, deploy-ready for the App To Page WordPress plugin.

- Use a relative base so it works at any URL:
  Vite -> base: './'   |   CRA -> "homepage": "."   |   Vue CLI -> publicPath: './'
  Plain HTML/JS -> use relative asset paths (href="style.css", not "/style.css")
- Keep a single top-level index.html as the entry point.
- Bundle all assets (models, fonts, images, wasm) inside the build and reference them relatively.
- Run the production build, then zip the CONTENTS of dist/ (or build/) so index.html is
  at the top of the archive.

You’ll also find this prompt inside the plugin, under App To Page » Apps — look for “Building with AI? Copy a prompt so it builds deploy-ready.”

Notes for specific tools

The prompt works everywhere, but a couple of tools have their own quirks:

• Claude Code / Cursor / Codex — these edit your project directly. Drop in the matching skill below so you don’t have to paste the prompt each time.
• Bolt, v0, and other in-browser builders — you can’t always set a config file, so lean on the export: ask for a relative-base production build, then download the output and zip its contents.
• ChatGPT / Claude (chat) — paste the prompt, then ask it to output the final files or a downloadable build.

Reusable agent skills

Drop one of these into your project so your AI does the right thing every time, without re-pasting:

• Claude Code skill — download app-to-page.skill.md. Place it in your project’s skills directory; it triggers whenever you ask to deploy to WordPress.
• Cursor rules — download app-to-page.cursorrules. Save it as .cursorrules in your project root.

Both encode the same rules as the prompt: relative base, a top-level index.html, relative assets, and a correctly-zipped build.

Then deploy it

Once your AI produces the build, you’ve got two paths:

• Upload the zip — drop it on App To Page » Apps. See Deploy your first app.
• Deploy from GitHub — if your AI pushes to a repo, point App To Page at it and pull builds on demand. See Deploy from a GitHub repository.

Frequently asked questions

How do I get an AI to build an app I can host on WordPress?

Give it the deploy-ready prompt above before it builds. It tells the AI to use a relative base, keep a top-level index.html, and produce a correctly-zipped build — which is exactly what App To Page needs.

Do I still need to set a relative base if I use the prompt?

The prompt sets it for you. App To Page also rewrites paths on upload as a safety net, so builds that aren’t perfectly relative usually still work — the prompt just means fewer surprises.

Which AI tools does this work with?

Any of them — Claude, Claude Code, Cursor, ChatGPT/Codex, Bolt, v0, and others. The prompt is generic; the downloadable skills are shortcuts for Claude Code and Cursor specifically.