# App To Page — deploy-ready build rules
# Drop this in your project (e.g. as .cursorrules) so the AI produces a build that
# uploads cleanly to a WordPress site via the App To Page plugin.

When asked to build, deploy, or publish this app to WordPress with App To Page:

- Produce a PRODUCTION build of this browser-only app. Never assume a server-side build.
- Use a RELATIVE base so assets resolve at any URL:
  - Vite: base: './' in vite.config
  - Create React App: "homepage": "." in package.json
  - Vue CLI: publicPath: './' in vue.config.js
  - 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 output; reference them relatively.
- After building, zip the CONTENTS of the output folder (dist/ or build/) so index.html sits at the
  top of the archive — not nested under a wrapping folder.
- Then tell the user: upload the zip in WordPress under "App To Page → Apps" — drop it, pick a URL,
  preview, publish.

Avoid: root-absolute asset paths, external/CDN paths the user must configure, and burying index.html
inside extra directories.