vscode-cognitive-os

Audits and generates VS Code settings.json, keybindings, and extension configurations for specific tech stacks.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/Scardubu/SwarmXQ --skill vscode-cognitive-os-scardubu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-cognitive-os
Source: https://github.com/Scardubu/SwarmXQ/tree/main/.ai/skills/vscode-cognitive-os
Command: npx skills add https://github.com/Scardubu/SwarmXQ --skill vscode-cognitive-os-scardubu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuring VS Code for a specific tech stack involves hundreds of settings, conflicting extensions, and scattered documentation, often resulting in a slow, noisy editor that increases cognitive load instead of reducing it. ## Core Features & Use Cases - Configuration Audit: Reviews an existing settings.json to flag redundant settings, conflicting options, missing high-leverage settings, and extension bloat. - Stack-Aware Generation: Produces a fully commented settings.json, tiered extension list, and keybindings.json tailored to stacks like Next.js/TypeScript, Python, Rust, or monorepos. - Workspace Setup: Generates .code-workspace files with per-folder settings, recommended extensions, and launch configs for multi-root projects. - Use Case: A developer starting a new Next.js project asks for an optimized editor setup and receives a complete settings.json with justified options, a tiered extension list with publisher IDs, and keybindings for their ten most frequent actions. ## Quick Start Ask the assistant to generate an optimized VS Code settings.json and extension stack for your primary tech stack, or paste your existing settings.json for an audit.

Frequently Asked Questions about vscode-cognitive-os

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an optimized settings.json for VS Code?

Share your primary tech stack and the skill generates a complete, commented settings.json organized into sections like Editor Core, Typography, Terminal, and language-specific options. Every setting includes an inline comment explaining why it is set.

What VS Code extensions should I install for TypeScript or Next.js?

The recommended stack includes ESLint, Prettier, Tailwind CSS IntelliSense, Headwind, Pretty TypeScript Errors, and Error Lens, each with a publisher ID for CLI installation. Extensions are organized into non-negotiable, stack-specific, and optional tiers.

Can it audit my existing VS Code settings.json?

Yes, paste your existing settings.json and it flags redundant settings that re-declare defaults, conflicting options that cancel each other out, missing high-leverage settings for your stack, and installed extensions that overlap or go unused.

Does it support monorepo or multi-root workspace setup?

Yes, for Turborepo or Nx monorepos it produces a .code-workspace file with per-folder settings, recommended extensions, launch configurations, and per-package lint configs with task runner integration.

Why does my VS Code feel slow or cluttered?

Slowness and clutter usually come from decorative UI settings, overlapping extensions, and missing performance options. The audit step identifies these issues and the generated config disables low-value visuals while keeping information density high.