← ClaudeAtlas

setup-launch-jsonlisted

Inspect a project and create, update, migrate, or repair a standards-aligned DAP launch.json for Logos or the VS Code-compatible subset. Use when an Agent needs to set up launch or attach debugging, choose a debug adapter, add Node/Chrome/Electron/custom runtime configurations, validate existing .logos/launch.json or .vscode/launch.json, or diagnose why Logos cannot load a launch configuration.
zixiao-labs/logos · ★ 4 · Data & Documents · score 70
Install: claude install-skill zixiao-labs/logos
# Set up launch.json Create a minimal, evidence-based debug configuration that Logos can load and the selected Debug Adapter Protocol implementation accepts. ## Workflow 1. Inspect the workspace before editing. - Read package/build scripts, entry points, runtime manifests, and relevant documentation. - Read both `.logos/launch.json` and `.vscode/launch.json` when present. - Identify the runtime executable, launch target or attach endpoint, working directory, and whether a build/dev server must already be running. 2. Choose the target file without changing precedence accidentally. - Update `.logos/launch.json` when it exists; Logos always loads it first. - Otherwise update `.vscode/launch.json` only when every new field belongs to the compatible subset. - When a Logos-only feature is required while `.vscode/launch.json` exists, explain that a new `.logos/launch.json` will shadow it and preserve every configuration the user still needs. - Prefer `.vscode/launch.json` when the configuration uses the shared VS Code subset, so mainstream editors and coding agents can discover it. Use `.logos/launch.json` when Logos-specific fields are required. 3. Choose `request` and `type` from project evidence. - Use `launch` when Logos should start the debuggee and `attach` when another process owns its lifecycle. - Use `node`/`pwa-node` for Node.js and `chrome`/`pwa-chrome` for Chromium. - Use `electron` only for the Logos Electron alias; use a valid Node conf