gen-startup-batlisted

# Gen Startup BAT ## Workflow ### Step 1 — Scan project structure Read in order of preference: 1. `CLAUDE.md` — look for dev command blocks and port info 2. frontend package manifests, checking common locations first: `client/`, `frontend/`, `web/`, `app/`, then repo root `package.json`; for monorepos also inspect `pnpm-workspace.yaml`, `package.json` `workspaces`, `turbo.json`, and `nx.json` 3. `*.sln` → referenced `*.csproj`; if no `.sln` is useful, search for `*.csproj` and prefer web/API projects with `Properties/launchSettings.json` 4. `README.md` — fallback if no structured config found Identify: - **Frontend dir** + **dev command** (e.g. `npm run dev`, without `cd`) - **Backend dir** + **run command**: locate the `.csproj` file name → default to `dotnet run --project .\<name>.csproj` - **Backend URL** from `launchSettings.json` → select a `commandName: "Project"` profile when available → read `applicationUrl`; preserve the full URL list and prefer HTTPS only when choosing a browser/API URL - **Frontend dev server URL** from `vite.config.*` / `quasar.config.*` / framework config `server.port`; if not found, infer common defaults from scripts/frameworks ### Frontend detection details - Prefer a package manifest that contains a runnable `dev`, `start`, or framework-specific dev script over one that only contains build/test scripts. - In monorepos, inspect workspace packages and choose the app-like package (`vite`, `quasar`, `next`, `nuxt`, `react-scripts`, `astro`,