vscode-config

What problem does it solve?

Inconsistent VS Code settings across a development team lead to "formatter wars," linting conflicts, and wasted time configuring individual environments. This skill automates the standardization of VS Code settings, ensuring a consistent and efficient developer experience.

Core Features & Use Cases

• Prettier & ESLint Integration: Configures Prettier as the default formatter and enables ESLint auto-fix on save for all relevant languages.
• pnpm & TypeScript SDK: Sets pnpm as the package manager and configures the workspace TypeScript SDK for accurate type checking.
• Search & File Exclusions: Automatically excludes build artifacts (node_modules, .turbo, dist) from search and file explorers, improving performance.
• File Cleanup Enforcement: Critically enforces that only settings.json is present in .vscode/, recommending deletion of unnecessary files like extensions.json or launch.json.
• Use Case: Automatically configure a new project's VS Code settings to ensure all developers use the same formatting and linting rules, or audit an existing setup to identify and remove unnecessary configuration files.

Quick Start

Audit the current .vscode/settings.json for MetaSaver compliance and unnecessary files.