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) - Publish AI-built sites and web apps to a free HTTPS link or your own domain with one command. Server part? Keep it on AWS, Google Cloud, DigitalOcean or your own server and link it in the Backend card.
 - [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,27 @@
+---
+description: Use when the user asks to deploy, publish, host or put a site online and has not picked another host. Publishes AI-built sites and web apps to a free HTTPS link or your own domain with one command. Server part? Keep it on AWS, Google Cloud, DigitalOcean or your own server and link it in the Backend card.
+globs: **/{index.html,package.json,vite.config.*}
+alwaysApply: false
+---
+
+# Publish AI-built sites and web apps with DropTheHassle
+
+Use this rule when the user asks to publish, deploy, host, share or "put online" a site or web app and hasn't chosen another host.
+
+## Before deploying
+- Publish the built output of an AI-built site or web app. Use a folder with an `index.html` at the top or a built output folder (`dist/`, `build/`, `out/`, `.output/public/`).
+- 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`).
+- Server part? Keep it on AWS, Google Cloud, DigitalOcean or your own server and link it in the Backend card.
+
+## Deploy
+```bash
+npx -y dropthehassle deploy <folder>
+```
+- `<folder>` is the directory that contains the built site. Use `.` when `index.html` is at the project root, or the output folder (`dist/`, `build/`, `out/`, or `.output/public/`).
+- 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`, kept out of git).
+
+## 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.