flingit 0.0.49 → 0.0.50

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "flingit",
-    "version": "0.0.49",
+    "version": "0.0.50",
     "description": "Small Software Platform - Build and deploy personal tools through conversation",
     "type": "module",
     "engines": {

package/templates/default/dot-claude/skills/fling/.hash

@@ -1 +1 @@
-fb441c8b2dd2df7a51209941ca4cbd17
+56ff0f95fb32f366e828b1f9b58a4c30

package/templates/default/dot-claude/skills/fling/SKILL.md

@@ -138,7 +138,7 @@ Always use `npx` to run the project's installed Fling (not global).
 **Important:** The CLI must be called without a TTY (e.g., with stdout redirected), or with the `--cli` flag. When both stdin and stdout are a TTY and `--cli` is not passed, the CLI launches an interactive mode instead of executing commands. If you are running from an environment where a TTY may be present, always pass `--cli`:
 
 ```bash
-npx fling -- --cli push        # Safe from any environment
+npx fling --cli push        # Safe from any environment
 ```
 
 ```bash
@@ -173,13 +173,13 @@ Each cron invocation logs "Running cron job <name>" at the start. To see all log
 
 1. **Find the invocation** by searching for the cron job name:
    ```bash
-   npx fling -- --prod logs --search "Running cron job daily-cleanup"
+   npx fling --prod logs --search "Running cron job daily-cleanup"
    ```
    This shows log entries with Ray IDs like `[ray:abc12345]`.
 
 2. **Filter by that Ray ID** to see all logs from that invocation:
    ```bash
-   npx fling -- --prod logs --ray abc12345
+   npx fling --prod logs --ray abc12345
    ```
 
 ### Local vs Production (`--prod`)
@@ -194,11 +194,11 @@ npx fling db sql "SELECT 1" # Local SQLite
 npx fling storage list      # Local storage
 
 # Production (requires login)
-npx fling -- --prod secret list       # Deployed secrets
-npx fling -- --prod logs              # Deployed logs
-npx fling -- --prod db sql "SELECT 1" # Deployed D1
-npx fling -- --prod storage list      # R2 storage
-npx fling -- --prod cron list         # Deployed cron jobs
+npx fling --prod secret list       # Deployed secrets
+npx fling --prod logs              # Deployed logs
+npx fling --prod db sql "SELECT 1" # Deployed D1
+npx fling --prod storage list      # R2 storage
+npx fling --prod cron list         # Deployed cron jobs
 ```
 
 **Note:** Production logs have a delay of ~10 seconds or more before they appear.
@@ -230,7 +230,7 @@ After each deploy, tell the user what the deployed URL is.  With Fling, to deplo
 
 ### After First Deployment
 
-After your first `fling push`, consider asking the user if they want a custom URL.
+After your first `fling it`, consider asking the user if they want a custom URL.
 Their project was auto-assigned a slug like `proj-abc123`.
 
 To change it: `npx fling project slug:set my-custom-slug`
@@ -246,36 +246,36 @@ If the user isn't logged in (no token stored), help them authenticate:
 
 **New user:** Sign up with email and name:
 ```bash
-npx fling -- --cli signup --email user@example.com --name "User Name"
+npx fling --cli signup --email user@example.com --name "User Name"
 ```
 
 **Existing user:** Log in via magic link email:
 ```bash
-npx fling -- --cli login --email user@example.com
+npx fling --cli login --email user@example.com
 ```
 After running login, tell the user to check their email and click the login link.
 The CLI will wait until the link is clicked, then complete login automatically.
 
-If the user prefers, they can run `fling signup` or `fling login` interactively themselves.
+DO NOT ASK THE USER TO RUN THESE COMMAND THEMSELVES. You have bash access, run them directly, unless they ask explicitly.
 
 ### Email Verification
 
 After signing up, you must verify your email to deploy.
-If `fling push` fails with "Email verification required":
+If `fling it` fails with "Email verification required":
 
 1. Run `fling verify` to check verification status
 2. Run `fling verify --resend` to resend the verification email
 3. **Tell the user they need to check their email and click the verification link.** You cannot do this step for them — they must open their inbox, find the email from Fling, and click the link. Wait for them to confirm they have done this before proceeding.
-4. Retry `fling push` after the user confirms they clicked the link
+4. Retry `fling it` after the user confirms they clicked the link
 
-### What `fling push` does:
+### What `fling it` does:
 
 1. **Builds frontend** - Runs `vite build`, outputs to `dist/client/`
 2. **Uploads static assets** - HTML, JS, CSS, images from `dist/client/`
 3. **Bundles backend** - Compiles `src/worker/index.ts` with esbuild
 4. **Deploys to Cloudflare** - Both frontend and backend go live
 
-**Secrets:** Always stored locally in `.fling/secrets`. Use `fling push` to deploy secrets to production along with your code.
+**Secrets:** Always stored locally in `.fling/secrets`. Use `fling it` to deploy secrets to production along with your code.
 
 ### Static Asset Limits
 
@@ -328,7 +328,7 @@ This gives collaborators:
 
 7. **Use /api prefix for backend routes** - Required for Vite proxy during development.
 
-8. **Run commands yourself** - You have bash access. Don't ask the user to run `fling push`, `fling dev`, `npm start`, etc. Execute them directly.
+8. **Run commands yourself** - You have bash access. Don't ask the user to run `fling it`, `fling dev`, `npm start`, etc. Execute them directly.
 
 9. **Reserved paths (`/__*`)** - Paths starting with `/__` are reserved for internal platform use (e.g., `/__cron` for cron jobs). Do not create routes with these prefixes.