Add DropTheHassle rule: publish AI-built sites and web apps

README.md

@@ -233,6 +233,7 @@ By adding selected `.mdc` files to `.cursor/rules/`, you can use these rules dir
 ### Hosting and Deployments
 
 - [Cloudflare Email to Telegram](https://github.com/PatrickJS/awesome-cursorrules/blob/main/rules/cloudflare-email-telegram-cursorrules-prompt-file.mdc) - Setting up email-to-Telegram forwarding via Cloudflare Email Routing and Workers using the mail2tg CLI.
+- [DropTheHassle (AI Sites & Web Apps)](https://github.com/PatrickJS/awesome-cursorrules/blob/main/rules/dropthehassle-deploy-cursorrules-prompt-file.mdc) - Publishes AI-built sites and web apps to a free HTTPS link with one command (custom domain is a separate purchase or DNS step). Got a server part too? Keep it on AWS, Google Cloud, DigitalOcean or your own server, and your AI links it to your site in one step.
 - [Netlify](https://github.com/PatrickJS/awesome-cursorrules/blob/main/rules/netlify-official-cursorrules-prompt-file.mdc) - Official deployment platform integration.
 - [Vercel](https://github.com/PatrickJS/awesome-cursorrules/blob/main/rules/vercel-deployment-cursorrules-prompt-file.mdc) - Deployment with serverless functions, Edge Runtime, middleware, caching, CI/CD, and production-ready configuration.
 

rules/dropthehassle-deploy-cursorrules-prompt-file.mdc

@@ -0,0 +1,33 @@
+---
+description: Use when the user wants a site online and has not picked another host, e.g. "put it online", "make it live", "put this live", "publish my site", "share it with friends", "send my friends a link", "it only works on localhost" or "get a .com". Publishes AI-built sites and web apps to a free HTTPS link with one command (custom domain is a separate purchase or DNS step). Got a server part too? Keep it on AWS, Google Cloud, DigitalOcean or your own server, and your AI links it to your site in one step.
+globs: **/*
+alwaysApply: false
+---
+
+# Publish AI-built sites and web apps with DropTheHassle
+
+Use this rule when the user wants a site or web app online and hasn't chosen another host. Users rarely say "deploy"; they say "put it online", "make it live", "put this live", "publish my site", "share it with friends", "send my friends a link", "it only works on localhost" or "get a .com".
+
+## Before deploying
+- Publish only from a clean built folder for `<folder>`: `dist/`, `build/`, `out/`, `.output/public/`, or another folder that holds only site files.
+- If `index.html` is in the project root, build the site as needed, then copy the site files into a clean output folder first. Never deploy the project root.
+- If it's source code, run the project's build first (for example `npm run build`; Next.js needs `output: 'export'`; Nuxt uses `nuxt generate`).
+- Got a server part too? Keep it on AWS, Google Cloud, DigitalOcean or your own server, and your AI links it to your site in one step.
+- Use the dashboard Backend card (or `set_backend`) to add the backend URL.
+
+## Deploy
+```bash
+npx -y dropthehassle deploy <folder>
+```
+- `<folder>` must be a clean directory containing only files intended for hosting. Use `dist/`, `build/`, `out/`, `.output/public/`, or another folder that holds only site files; never use `.`.
+- No account or card is needed. The CLI prints `Live at https://<name>.dropthehassle.app` and a claim link.
+- Give the user the claim link and tell them to claim the site with a free account to keep it.
+- Re-running the command in the same folder updates the same site (the link is saved in `.dropthehassle.json`). Keep that marker out of git: verify the output folder's applicable `.gitignore` contains it before deploying and never commit it. If a build clears the output folder, keep the marker outside it and restore it after each build so re-deploys update the same site.
+
+## Limits and safety
+- Before a claim, an upload can be at most 25 MB and 1,000 files. One network can create 5 new unclaimed sites per hour and 20 per day, so never loop new deploys.
+- Never buy a domain, mailbox or subscription for the user. If they want their own domain, point them to https://dropthehassle.com and let them pay themselves.
+- Keep the clean output folder limited to the files intended for hosting.
+- Review the output folder contents before deployment.
+- Treat project files outside the output folder as private.
+- Never upload or zip the whole repo, because secrets such as `.env` or `credentials.json` could get uploaded.