launchframe 0.4.0 → 0.4.1

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

@@ -0,0 +1,45 @@
+---
+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>\""
+user-invocable: true
+---
+
+# Launchframe
+
+You are helping the user scaffold a **new** project from **$ARGUMENTS**:
+
+- A **reference URL** (the website to copy later with `/clone-website`)
+- A **SaaS idea** string (headline / positioning for the generated landing page)
+
+## Parse inputs
+
+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.
+
+2. Optional flags the user might pass (same as the CLI): `--dir` / `-o` for output folder, `--skip-install` to skip `npm install`.
+
+## Run the published CLI
+
+Execute the scaffold using the **latest** package from npm (exact intent: **`launchframe@latest`**):
+
+```bash
+npx launchframe@latest "<url>" "<saas-idea>" [--dir <folder>] [--skip-install]
+```
+
+- 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`.
+
+## After scaffold
+
+Tell the user:
+
+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`.
+
+## 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.