launchframe 0.4.1 → 0.4.2

package/.amazonq/cli-agents/launchframe.json

@@ -1,7 +1,7 @@
 {
   "name": "launchframe",
-  "description": "Scaffold a Next.js app with npx launchframe@latest from a reference URL and SaaS idea",
-  "prompt": "\n# Launchframe\n\nYou are helping the user scaffold a **new** project from **the reference URL and SaaS idea from the user (see slash command arguments)**:\n\n- A **reference URL** (the website to copy later with `/clone-website`)\n- A **SaaS idea** string (headline / positioning for the generated landing page)\n\n## Parse inputs\n\n1. Split **the reference URL and SaaS idea from the user (see slash command arguments)** into:\n   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.\n   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.\n\n2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.\n\n## Run the published CLI\n\nExecute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):\n\n```bash\nnpx launchframe@latest \"<url>\" \"<saas-idea>\" [--dir <folder>] [--skip-install]\n```\n\n- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.\n- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.\n- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.\n\n## After scaffold\n\nTell the user:\n\n1. `cd` into the new project directory.\n2. `npm run dev` to preview the SaaS landing shell.\n3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.\n\n## Fallback (local dev only)\n\nIf `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs \"<url>\" \"<saas-idea>\" ...` with the same rules for `--dir` outside the package root.\n",
+  "description": "Scaffold with npx launchframe@latest into the current folder — no arguments required",
+  "prompt": "\n# Launchframe\n\nHelp the user create a **new** Launchframe project. The CLI is **parameterless**:\n\n```bash\nnpx launchframe@latest\n```\n\nIt unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.\n\n## What you do\n\n1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.\n\n2. Run exactly:\n\n   ```bash\n   npx launchframe@latest\n   ```\n\n   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.\n\n3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.\n\n4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.\n\n5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.\n\n## If optional notes from the user after the slash command (the CLI itself needs no URL or SaaS strings) are present\n\nThe user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.\n\n## Fallback (local dev only)\n\nFrom a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).\n",
   "fileContext": [
     "AGENTS.md",
     "docs/research/**"

package/.amazonq/rules/project.md

@@ -10,7 +10,7 @@ This version has breaking changes — APIs, conventions, and file structure may
 # Website Reverse-Engineer Template
 
 ## What This Is
-A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — start a **new** project with **`/launchframe <url> "your saas idea"`** (runs **`npx launchframe@latest`**), or work in the current repo and run **`/clone-website <url1> [<url2> ...]`** to clone into this tree.
+A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — for a **new** folder, `mkdir`, `cd` into an **empty** directory, run **`npx launchframe@latest`** (no parameters), then edit **`src/lib/launchframe-config.ts`** and run **`/clone-website`** with your URL (or invoke **`/launchframe`** so the agent runs the same command). Or work in this repo and run **`/clone-website <url1> [<url2> ...]`** to clone into the current tree.
 
 ## Tech Stack
 - **Framework:** Next.js 16 (App Router, React 19, TypeScript strict)

package/.augment/commands/launchframe.md

@@ -1,6 +1,6 @@
 ---
-description: "Scaffold a Next.js app with npx launchframe@latest from a reference URL and SaaS idea"
-argument-hint: "<url> \"<saas-idea>\""
+description: "Scaffold with npx launchframe@latest into the current folder — no arguments required"
+argument-hint: ""
 ---
 <!-- AUTO-GENERATED from .claude/skills/launchframe/SKILL.md — do not edit directly.
      Run `node scripts/sync-skills.mjs` to regenerate. -->
@@ -8,39 +8,36 @@ argument-hint: "<url> \"<saas-idea>\""
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **$ARGUMENTS**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **$ARGUMENTS** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If $ARGUMENTS are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).

package/.claude/skills/launchframe/SKILL.md

@@ -1,45 +1,42 @@
 ---
 name: launchframe
-description: Scaffold a new Next.js project with npx launchframe@latest using a reference URL and SaaS landing copy. Invoked as /launchframe.
-argument-hint: "<url> \"<saas-idea>\""
+description: Scaffold a Next.js app with npx launchframe@latest into the current folder — no CLI arguments required. Invoked as /launchframe.
+argument-hint: ""
 user-invocable: true
 ---
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **$ARGUMENTS**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **$ARGUMENTS** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If $ARGUMENTS are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).

package/.clinerules

@@ -10,7 +10,7 @@ This version has breaking changes — APIs, conventions, and file structure may
 # Website Reverse-Engineer Template
 
 ## What This Is
-A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — start a **new** project with **`/launchframe <url> "your saas idea"`** (runs **`npx launchframe@latest`**), or work in the current repo and run **`/clone-website <url1> [<url2> ...]`** to clone into this tree.
+A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — for a **new** folder, `mkdir`, `cd` into an **empty** directory, run **`npx launchframe@latest`** (no parameters), then edit **`src/lib/launchframe-config.ts`** and run **`/clone-website`** with your URL (or invoke **`/launchframe`** so the agent runs the same command). Or work in this repo and run **`/clone-website <url1> [<url2> ...]`** to clone into the current tree.
 
 ## Tech Stack
 - **Framework:** Next.js 16 (App Router, React 19, TypeScript strict)

package/.codex/skills/launchframe/SKILL.md

@@ -1,45 +1,42 @@
 ---
 name: launchframe
-description: Scaffold a new Next.js project with npx launchframe@latest using a reference URL and SaaS landing copy. Invoked as /launchframe.
-argument-hint: "<url> \"<saas-idea>\""
+description: Scaffold a Next.js app with npx launchframe@latest into the current folder — no CLI arguments required. Invoked as /launchframe.
+argument-hint: ""
 user-invocable: true
 ---
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **$ARGUMENTS**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **$ARGUMENTS** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If $ARGUMENTS are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).

package/.continue/commands/launchframe.md

@@ -1,6 +1,6 @@
 ---
 name: launchframe
-description: "Scaffold a Next.js app with npx launchframe@latest from a reference URL and SaaS idea"
+description: "Scaffold with npx launchframe@latest into the current folder — no arguments required"
 invokable: true
 ---
 <!-- AUTO-GENERATED from .claude/skills/launchframe/SKILL.md — do not edit directly.
@@ -9,39 +9,36 @@ invokable: true
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **$ARGUMENTS**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **$ARGUMENTS** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If $ARGUMENTS are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).

package/.continue/rules/project.md

@@ -14,7 +14,7 @@ This version has breaking changes — APIs, conventions, and file structure may
 # Website Reverse-Engineer Template
 
 ## What This Is
-A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — start a **new** project with **`/launchframe <url> "your saas idea"`** (runs **`npx launchframe@latest`**), or work in the current repo and run **`/clone-website <url1> [<url2> ...]`** to clone into this tree.
+A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — for a **new** folder, `mkdir`, `cd` into an **empty** directory, run **`npx launchframe@latest`** (no parameters), then edit **`src/lib/launchframe-config.ts`** and run **`/clone-website`** with your URL (or invoke **`/launchframe`** so the agent runs the same command). Or work in this repo and run **`/clone-website <url1> [<url2> ...]`** to clone into the current tree.
 
 ## Tech Stack
 - **Framework:** Next.js 16 (App Router, React 19, TypeScript strict)

package/.cursor/commands/launchframe.md

@@ -4,39 +4,36 @@
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **the reference URL and SaaS idea from the user (see slash command arguments)**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **the reference URL and SaaS idea from the user (see slash command arguments)** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If optional notes from the user after the slash command (the CLI itself needs no URL or SaaS strings) are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).

package/.gemini/commands/launchframe.toml

@@ -1,48 +1,45 @@
 # AUTO-GENERATED from .claude/skills/launchframe/SKILL.md
 # Run `node scripts/sync-skills.mjs` to regenerate.
 
-description = "Scaffold a Next.js app with npx launchframe@latest from a reference URL and SaaS idea"
+description = "Scaffold with npx launchframe@latest into the current folder — no arguments required"
 
 [prompt]
 text = '''
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **{{args}}**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **{{args}}** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If {{args}} are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).
 
 '''

package/.github/copilot-instructions.md

@@ -10,7 +10,7 @@ This version has breaking changes — APIs, conventions, and file structure may
 # Website Reverse-Engineer Template
 
 ## What This Is
-A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — start a **new** project with **`/launchframe <url> "your saas idea"`** (runs **`npx launchframe@latest`**), or work in the current repo and run **`/clone-website <url1> [<url2> ...]`** to clone into this tree.
+A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — for a **new** folder, `mkdir`, `cd` into an **empty** directory, run **`npx launchframe@latest`** (no parameters), then edit **`src/lib/launchframe-config.ts`** and run **`/clone-website`** with your URL (or invoke **`/launchframe`** so the agent runs the same command). Or work in this repo and run **`/clone-website <url1> [<url2> ...]`** to clone into the current tree.
 
 ## Tech Stack
 - **Framework:** Next.js 16 (App Router, React 19, TypeScript strict)

package/.github/skills/launchframe/SKILL.md

@@ -1,45 +1,42 @@
 ---
 name: launchframe
-description: Scaffold a new Next.js project with npx launchframe@latest using a reference URL and SaaS landing copy. Invoked as /launchframe.
-argument-hint: "<url> \"<saas-idea>\""
+description: Scaffold a Next.js app with npx launchframe@latest into the current folder — no CLI arguments required. Invoked as /launchframe.
+argument-hint: ""
 user-invocable: true
 ---
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **$ARGUMENTS**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **$ARGUMENTS** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If $ARGUMENTS are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).

package/.opencode/commands/launchframe.md

@@ -1,5 +1,5 @@
 ---
-description: "Scaffold a Next.js app with npx launchframe@latest from a reference URL and SaaS idea"
+description: "Scaffold with npx launchframe@latest into the current folder — no arguments required"
 ---
 <!-- AUTO-GENERATED from .claude/skills/launchframe/SKILL.md — do not edit directly.
      Run `node scripts/sync-skills.mjs` to regenerate. -->
@@ -7,39 +7,36 @@ description: "Scaffold a Next.js app with npx launchframe@latest from a referenc
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **$ARGUMENTS**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **$ARGUMENTS** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If $ARGUMENTS are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).

package/.windsurf/workflows/launchframe.md

@@ -4,39 +4,36 @@
 
 # Launchframe
 
-You are helping the user scaffold a **new** project from **the reference URL and SaaS idea from the user (see slash command arguments)**:
+Help the user create a **new** Launchframe project. The CLI is **parameterless**:
 
-- A **reference URL** (the website to copy later with `/clone-website`)
-- A **SaaS idea** string (headline / positioning for the generated landing page)
+```bash
+npx launchframe@latest
+```
 
-## Parse inputs
+It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
 
-1. Split **the reference URL and SaaS idea from the user (see slash command arguments)** into:
-   - **URL** — First `http://` or `https://` URL. Normalize (trim, validate). If invalid or missing, ask once for a correct URL.
-   - **SaaS idea** — Everything after the URL, typically in quotes. Strip surrounding quotes. If empty, ask for a short product pitch.
+## What you do
 
-2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
 
-## Run the published CLI
+2. Run exactly:
 
-Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+   ```bash
+   npx launchframe@latest
+   ```
 
-```bash
-npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
-```
+   Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
+
+3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
 
-- Use shell-appropriate quoting (PowerShell vs bash). Escape embedded quotes in the SaaS idea.
-- **Output path:** The Launchframe CLI must not write **inside** the npm package / template directory itself (that would recurse). If the open workspace is this repository, run `npx` with `--dir` pointing to a **sibling** path (e.g. `..\\my-app` on Windows, `../my-app` on macOS/Linux) or ask the user for a folder **outside** the repo.
-- Prefer letting the CLI run `npm install` unless the user passed `--skip-install`.
+4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
 
-## After scaffold
+5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
 
-Tell the user:
+## If optional notes from the user after the slash command (the CLI itself needs no URL or SaaS strings) are present
 
-1. `cd` into the new project directory.
-2. `npm run dev` to preview the SaaS landing shell.
-3. Run **`/clone-website <same-reference-url>`** in that project so the agent can reverse-engineer the reference site into components, while keeping the SaaS idea from `launchframe.context.json` / `src/lib/launchframe-config.ts`.
+The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
 
 ## Fallback (local dev only)
 
-If `npx launchframe@latest` is unavailable (offline), from a **checkout of this repo** you may run `node bin/launchframe.mjs "<url>" "<saas-idea>" ...` with the same rules for `--dir` outside the package root.
+From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).

package/AGENTS.md

@@ -7,7 +7,7 @@ This version has breaking changes — APIs, conventions, and file structure may
 # Website Reverse-Engineer Template
 
 ## What This Is
-A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — start a **new** project with **`/launchframe <url> "your saas idea"`** (runs **`npx launchframe@latest`**), or work in the current repo and run **`/clone-website <url1> [<url2> ...]`** to clone into this tree.
+A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — for a **new** folder, `mkdir`, `cd` into an **empty** directory, run **`npx launchframe@latest`** (no parameters), then edit **`src/lib/launchframe-config.ts`** and run **`/clone-website`** with your URL (or invoke **`/launchframe`** so the agent runs the same command). Or work in this repo and run **`/clone-website <url1> [<url2> ...]`** to clone into the current tree.
 
 ## Tech Stack
 - **Framework:** Next.js 16 (App Router, React 19, TypeScript strict)

package/README.md

@@ -2,7 +2,7 @@
 
 <a href="https://github.com/JCodesMore/ai-website-cloner-template/blob/master/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License" /></a> <a href="https://github.com/JCodesMore/ai-website-cloner-template/stargazers"><img src="https://img.shields.io/github/stars/JCodesMore/ai-website-cloner-template?style=flat" alt="Stars" /></a> <a href="https://discord.gg/hrTSX5yTpB"><img src="https://img.shields.io/discord/1400896964597383279?label=discord" alt="Discord" /></a>
 
-Scaffold a Next.js + shadcn/ui project from **a reference URL you want to copy** plus **your SaaS idea** that drives landing-page positioning. Use **`npx launchframe@latest`** or the slash command **`/launchframe <url> "your idea"`** to scaffold, then run **`/clone-website`** so your AI agent reverse-engineers the reference layout while preserving your messaging inputs (`launchframe.context.json`, `docs/research/LAUNCHFRAME.md`, `src/lib/launchframe-config.ts`).
+Scaffold a Next.js + shadcn/ui project in **the folder where you run the command** — use **`npx launchframe@latest`** (no arguments; create an empty directory, `cd` into it, then run it). Configure the reference URL and SaaS copy in **`src/lib/launchframe-config.ts`**. Then run **`/clone-website`** so your AI agent reverse-engineers the reference layout while preserving your messaging (`launchframe.context.json`, `docs/research/LAUNCHFRAME.md`, `src/lib/launchframe-config.ts`). In the agent, **`/launchframe`** means the same one-liner.
 
 **Recommended: [Claude Code](https://docs.anthropic.com/en/docs/claude-code) with Opus 4.7 for best results** — but works with a variety of AI coding agents.
 
@@ -14,44 +14,33 @@ Scaffold a Next.js + shadcn/ui project from **a reference URL you want to copy**
 
 ## Quick Start
 
-### AI agents (slash command)
-
-In Cursor, Claude Code, Continue, and other synced tools:
-
-```text
-/launchframe https://example.com "Your SaaS idea in plain language"
-```
-
-The agent runs **`npx launchframe@latest`** with those arguments (see `.cursor/commands/launchframe.md`). Output must be **outside** the template package directory when developing from a clone of this repo — use `--dir ../my-app` or an absolute path.
+### 1. New project (empty folder)
 
-### CLI (same as slash command)
-
-From an empty folder (or anywhere you want the project folder created):
+Create an **empty** directory, go into it, run the CLI with **no parameters** — files are written to **that folder** (your project root):
 
 ```bash
-npx launchframe@latest https://example.com "Your SaaS idea in plain language"
+mkdir my-app
+cd my-app
+npx launchframe@latest
 ```
 
-Scaffolding copies the full template at the repository root — including **hidden agent config** (for example `.cursor/`, `.claude/`, `.github/`, `.amazonq/`, `.augment/`, and other dotfiles) so tools see the same rules and commands as this template.
+Optional: set `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` in the environment before running to pre-fill config without editing files.
 
-Optional flags:
+Then edit `src/lib/launchframe-config.ts` if you still need to change the reference URL or SaaS pitch, run `npm run dev`, and use **`/clone-website`** with your reference URL.
 
-- `--dir my-app` / `-o my-app` — output folder name (default: `<hostname>-launchframe`)
-- `--skip-install` — scaffold files only; run `npm install` yourself
+### AI agents (slash command)
 
-Then:
+In Cursor, Claude Code, Continue, etc., **`/launchframe`** tells the agent to run **`npx launchframe@latest`** in an empty folder the user chooses (same as above). No URL or SaaS strings are required on the command line.
 
-```bash
-cd <your-project-folder>
-npm run dev
-```
+### Optional flags
 
-Open your AI agent and run `/clone-website <same-reference-url>` so it rebuilds the reference site into components while aligning hero copy with your SaaS idea files above.
+- `--dir path` / `-o path` — scaffold into another folder instead of the current directory (must be empty)
+- `--skip-install` — skip `npm install`
 
 ### Git template (advanced)
 
 1. Clone this repository and `npm install`
-2. Replace `src/lib/launchframe-config.ts` or run `npx launchframe@latest ...` into a fresh folder
+2. Point `src/lib/launchframe-config.ts` at your site, or create sibling folder and run **`npx launchframe@latest`** there
 3. Run `/clone-website <target-url>` from your agent
 
 > Using a different agent? Open `AGENTS.md` for project instructions — most agents pick it up automatically.

package/bin/launchframe.mjs

@@ -1,21 +1,26 @@
 #!/usr/bin/env node
 /**
- * Scaffold a Launchframe project: clone reference URL via AI workflow + SaaS landing copy.
- * Usage: npx launchframe@latest <url> "<saas-idea>" [--dir=name] [--skip-install]
+ * Scaffold a Launchframe project into the current directory (or --dir).
+ * Usage: npx launchframe@latest [--dir=path] [--skip-install]
+ * Optional: LAUNCHFRAME_SOURCE_URL, LAUNCHFRAME_SAAS_IDEA env vars, or legacy CLI args.
  */
 
-import { cp, mkdir, readdir, readFile, writeFile } from "fs/promises";
+import { cp, mkdir, readdir, readFile, stat, writeFile } from "fs/promises";
 import { spawn } from "node:child_process";
-import { dirname, isAbsolute, join, relative, resolve } from "node:path";
+import { basename, dirname, isAbsolute, join, relative, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const PKG_ROOT = resolve(__dirname, "..");
 
+const DEFAULT_URL = "https://example.com";
+const DEFAULT_SAAS_IDEA =
+  "Edit your SaaS pitch in src/lib/launchframe-config.ts, then run /clone-website with your reference URL.";
+
 /**
  * Never copy these root entries into a scaffolded app (build artifacts, VCS, the CLI itself).
  * All other root files and folders are copied as-is — including every dotfile and dot-directory
- * so AI agents see the same agent rules, skills, and IDE metadata as this template.
+ * so AI agents see the same agent rules and commands as this template.
  */
 const SKIP_DIR_NAMES = new Set([
   "bin",
@@ -34,29 +39,44 @@ const SKIP_ROOT_FILES = new Set([
   "Thumbs.db",
 ]);
 
+async function pathExists(p) {
+  try {
+    await stat(p);
+    return true;
+  } catch {
+    return false;
+  }
+}
+
 function printHelp() {
   console.log(`
-launchframe — scaffold a Next.js app for cloning a reference site + your SaaS idea
+launchframe — scaffold a Next.js app into the current directory (project root)
 
 Usage:
-  npx launchframe@latest <url> "<saas-idea>" [options]
+  npx launchframe@latest
 
-Arguments:
-  <url>           HTTPS URL of the site to reverse-engineer (visual reference)
-  "<saas-idea>"   Short pitch / positioning that should appear on the landing page
+This unpacks the template into the folder you are in (where you ran the command).
+No URL or SaaS arguments are required — edit src/lib/launchframe-config.ts after scaffold.
+
+Optional environment variables (same session):
+  LAUNCHFRAME_SOURCE_URL     Reference site to clone later (https://...)
+  LAUNCHFRAME_SAAS_IDEA     Short landing-page pitch text
+
+Legacy (optional positional args, for scripts only):
+  npx launchframe@latest <url> "<saas-idea>"
 
 Options:
-  --dir, -o       Output folder (default: first label of hostname + "-launchframe")
+  --dir, -o       Scaffold into this folder instead of the current directory (must be empty)
   --skip-install  Do not run npm install after scaffolding
   -h, --help      Show this message
 
 Note:
-  The output folder must not live inside the Launchframe package directory (the folder that contains this CLI).
-  Scaffolding copies every root file and folder from the template (including dotfiles such as .cursor, .claude,
-  .github, etc.) except build/cache directories, so your AI tools see the same rules and commands as upstream.
+  Run inside an empty project folder (no existing package.json / src / next.config).
+  The output folder must not be inside the Launchframe npm package directory.
 
 Example:
-  npx launchframe@latest https://stripe.com "AI invoicing for freelancers"
+  mkdir my-app && cd my-app
+  npx launchframe@latest
 `);
 }
 
@@ -114,20 +134,8 @@ function validateUrl(raw) {
   return u.href;
 }
 
-function defaultDirName(urlStr) {
-  try {
-    const host = new URL(urlStr).hostname.replace(/^www\./i, "");
-    const label = host.split(".")[0] || "site";
-    const safe = label.replace(/[^a-zA-Z0-9-_]/g, "-").toLowerCase();
-    return `${safe || "site"}-launchframe`;
-  } catch {
-    return "launchframe-app";
-  }
-
-}
-
-function slugFromDir(dir) {
-  const base = dir.replace(/\\/g, "/").split("/").filter(Boolean).pop() ?? "launchframe-app";
+function slugFromDir(destRootAbs) {
+  const base = basename(resolve(destRootAbs));
   return base
     .toLowerCase()
     .replace(/[^a-z0-9-_]/g, "-")
@@ -193,7 +201,8 @@ async function writeGeneratedPackageJson(destRoot, npmPackageName) {
 
 async function writeLaunchframeArtifacts(destRoot, url, idea) {
   const configTs = `/**
- * Written by Launchframe CLI — edit freely after scaffolding.
+ * Set your reference site and positioning, then use /clone-website with the same URL.
+ * Written by Launchframe CLI — edit freely.
  */
 export const LAUNCHFRAME_SOURCE_URL = ${tsStringLiteral(url)} as const;
 
@@ -206,7 +215,7 @@ export const LAUNCHFRAME_SAAS_IDEA = ${tsStringLiteral(idea)} as const;
     sourceUrl: url,
     saasIdea: idea,
     notes:
-      "Use /clone-website with sourceUrl for pixel-perfect extraction. Align landing copy with saasIdea.",
+      "Edit this file or src/lib/launchframe-config.ts. Use /clone-website with sourceUrl for pixel-perfect extraction.",
   };
   await writeFile(
     join(destRoot, "launchframe.context.json"),
@@ -224,7 +233,7 @@ ${url}
 
 ${idea}
 
-When running \`/clone-website\`, pass the reference URL above. After structural cloning, rewrite headings and hero copy so they clearly communicate the SaaS idea while respecting attribution and copyright for third-party brands.
+When running \`/clone-website\`, pass the reference URL above (update src/lib/launchframe-config.ts first if you still use the default). After structural cloning, align hero copy with your SaaS idea while respecting attribution and copyright for third-party brands.
 `;
 
   await mkdir(join(destRoot, "docs", "research"), { recursive: true });
@@ -236,7 +245,14 @@ async function writeReadme(destRoot, npmPackageName, url, idea) {
 
 Created with [\`launchframe\`](https://www.npmjs.com/package/launchframe).
 
-## Inputs
+## Configure
+
+Edit \`src/lib/launchframe-config.ts\`:
+
+- \`LAUNCHFRAME_SOURCE_URL\` — site to reverse-engineer
+- \`LAUNCHFRAME_SAAS_IDEA\` — landing copy / positioning
+
+Current values (from scaffold):
 
 - **Reference site:** ${url}
 - **SaaS idea:** ${idea}
@@ -248,13 +264,7 @@ npm install
 npm run dev
 \`\`\`
 
-Open your AI agent (Cursor, Claude Code, etc.) and run:
-
-\`\`\`
-/clone-website ${url}
-\`\`\`
-
-Keep the SaaS positioning from \`launchframe.context.json\` / \`src/lib/launchframe-config.ts\` when adapting cloned sections.
+Open your AI agent and run \`/clone-website <your-reference-url>\` (same URL as in the config).
 
 See \`AGENTS.md\` for full agent instructions.
 `;
@@ -262,6 +272,21 @@ See \`AGENTS.md\` for full agent instructions.
   await writeFile(join(destRoot, "README.md"), body, "utf8");
 }
 
+/** Refuse to stomp an existing Next-style project in the target directory. */
+async function assertScaffoldTargetVacant(destRoot) {
+  const conflicts = ["package.json", "next.config.ts", "src"];
+  for (const c of conflicts) {
+    if (await pathExists(join(destRoot, c))) {
+      console.error(
+        `Refusing to scaffold: "${c}" already exists in this folder.\n` +
+          `Create a new empty directory, cd into it, then run:\n` +
+          `  npx launchframe@latest\n`,
+      );
+      process.exit(1);
+    }
+  }
+}
+
 function runNpmInstall(cwd) {
   return new Promise((resolvePromise, reject) => {
     const child = spawn("npm", ["install"], {
@@ -277,6 +302,17 @@ function runNpmInstall(cwd) {
   });
 }
 
+function resolveUrlAndIdea(args) {
+  const envUrl =
+    process.env.LAUNCHFRAME_SOURCE_URL?.trim() || process.env.LAUNCHFRAME_URL?.trim();
+  const envIdea = process.env.LAUNCHFRAME_SAAS_IDEA?.trim();
+
+  let urlRaw = args.url?.trim() || envUrl || DEFAULT_URL;
+  let ideaRaw = args.idea?.trim() || envIdea || DEFAULT_SAAS_IDEA;
+
+  return { urlRaw, ideaRaw };
+}
+
 async function main() {
   const args = parseArgs(process.argv.slice(2));
   if (args.help) {
@@ -284,36 +320,31 @@ async function main() {
     process.exit(0);
   }
 
-  if (!args.url || !args.idea) {
-    console.error("Error: missing URL or SaaS idea.\n");
-    printHelp();
+  const destRoot = args.dir?.trim()
+    ? resolve(process.cwd(), args.dir.trim())
+    : resolve(process.cwd());
+
+  if (isForbiddenOutput(PKG_ROOT, destRoot)) {
+    console.error(
+      "Output folder cannot be inside the Launchframe package directory. Create a new folder outside this package and cd into it, then run npx launchframe@latest again.",
+    );
     process.exit(1);
   }
 
+  await assertScaffoldTargetVacant(destRoot);
+
+  const { urlRaw, ideaRaw } = resolveUrlAndIdea(args);
+
   let url;
   try {
-    url = validateUrl(args.url);
+    url = validateUrl(urlRaw);
   } catch (e) {
     console.error(String(e.message));
     process.exit(1);
   }
 
-  const idea = args.idea.trim();
-  if (!idea) {
-    console.error("Error: SaaS idea cannot be empty.");
-    process.exit(1);
-  }
-
-  const dirName = args.dir?.trim() || defaultDirName(url);
-  const destRoot = resolve(process.cwd(), dirName);
-  const npmPackageName = slugFromDir(dirName);
-
-  if (isForbiddenOutput(PKG_ROOT, destRoot)) {
-    console.error(
-      "Output folder cannot be inside the Launchframe package directory. Run from a parent folder or choose another path.",
-    );
-    process.exit(1);
-  }
+  const idea = ideaRaw.trim() || DEFAULT_SAAS_IDEA;
+  const npmPackageName = slugFromDir(destRoot);
 
   await mkdir(destRoot, { recursive: true });
 
@@ -323,22 +354,23 @@ async function main() {
   await writeLaunchframeArtifacts(destRoot, url, idea);
   await writeReadme(destRoot, npmPackageName, url, idea);
 
-  console.log(`\nCreated Launchframe project at ${destRoot}`);
+  console.log(`\nScaffolded Launchframe in:\n  ${destRoot}`);
   console.log(`  Reference URL: ${url}`);
   console.log(`  SaaS idea: ${idea}\n`);
+  console.log("Edit src/lib/launchframe-config.ts if you need different values.\n");
 
   if (!args.skipInstall) {
     console.log("Running npm install...\n");
     try {
       await runNpmInstall(destRoot);
-      console.log("\nDone. Next: cd " + JSON.stringify(dirName) + " && npm run dev\n");
+      console.log("\nDone. From this folder: npm run dev\n");
     } catch (e) {
       console.error(String(e.message));
-      console.error("\nDependencies were not installed. Run npm install inside the folder manually.\n");
+      console.error("\nRun npm install in this folder manually.\n");
       process.exit(1);
     }
   } else {
-    console.log("Skipped npm install (--skip-install). Run npm install inside the folder.\n");
+    console.log("Skipped npm install (--skip-install). Run npm install in this folder.\n");
   }
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "launchframe",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "private": false,
   "description": "Scaffold a Next.js app from a reference URL plus your SaaS idea — AI-ready website cloning",
   "author": "JCodesMore",

package/scripts/sync-skills.mjs

@@ -25,10 +25,10 @@ const SKILLS = [
     id: "launchframe",
     sourceRel: ".claude/skills/launchframe/SKILL.md",
     shortDesc:
-      "Scaffold a Next.js app with npx launchframe@latest from a reference URL and SaaS idea",
+      "Scaffold with npx launchframe@latest into the current folder — no arguments required",
     plainSubstitution:
-      "the reference URL and SaaS idea from the user (see slash command arguments)",
-    augmentArgumentHint: "<url> \"<saas-idea>\"",
+      "optional notes from the user after the slash command (the CLI itself needs no URL or SaaS strings)",
+    augmentArgumentHint: "",
   },
 ];
 

package/src/lib/launchframe-config.ts

@@ -1,8 +1,7 @@
 /**
- * Defaults for local development before running `npx launchframe`.
- * The Launchframe CLI overwrites this file in scaffolded projects.
+ * Defaults before scaffolding. After `npx launchframe@latest`, edit these values.
  */
 export const LAUNCHFRAME_SOURCE_URL = "https://example.com" as const;
 
 export const LAUNCHFRAME_SAAS_IDEA =
-  'Run `npx launchframe <url> "your SaaS idea"` to scaffold with real inputs.' as const;
+  "Edit your SaaS pitch here, then run /clone-website with LAUNCHFRAME_SOURCE_URL." as const;