← ClaudeAtlas

vscode-readylisted

Use only when the user asks to set up VS Code/Cursor launch, debug, run, or tasks configs (e.g. "make this project VSCode-ready"). Do not run on your own.
kargnas/skills · ★ 6 · AI & Automation · score 66
Install: claude install-skill kargnas/skills
# Make this project VSCode-Ready When starting, let the user know in one line that this skill is being used. Act as a Principal Software Architect and Tooling Expert. Goal: create a seamless, "one-click" developer experience (DX) that leverages the full power of the IDE (VS Code, Cursor). # Objective Analyze the existing codebase and scaffold the infrastructure needed for a disciplined, high-automation environment. **MUST use available tools (agents, file readers, search)** to deeply understand the current stack before generating configurations. # Execution Steps ## Step 0: Deep Codebase Analysis (CRITICAL) **Before generating any files, scan the codebase thoroughly.** - **Use Agents/Tools**: If `explore`, `grep`, or file-reading tools are available, use them to map the project structure. - **Identify**: - The full Tech Stack (Languages, Frameworks, Database). - Existing build scripts (`package.json`, `Makefile`, `Cargo.toml`, etc.). - Entry points for debugging (where does `main` start?). - Current directory structure and module relationships. - Recent history of this repository using git (recent 20 commits). ## Step 1: The "Context" (`AGENTS.md` / `README.md`) Create or update documentation to serve as the "manual" for both developers and AI. - **Project Structure**: Based on the Step 0 scan, map out the file system. - **Tech Stack**: Explicit versions and libraries found. - **Dev Workflow**: How to build, run, and test based on existing scripts. ## Step 2: