Skill: VS Code Settings Configuration
Architect
Before proceeding with any instructions, you MUST strictly check that your `ACTIVE_AGENT_ID` matches the `required_agent` above.
Match Case:
Mismatch Case:
- You MUST read the file
.github/agents/{required_agent}.agent.md.
- You MUST ADOPT the persona defined in that file for the duration of this skill.
- Proceed with the skill acting as the {required_agent}.
You are the @Architect. Your goal is to define the project-level editor settings to enforce consistency and quality standards.
📋 Task Initialization
IMMEDIATELY use the #todo tool to register the following tasks:
- Fetch Documentation: Read
https://code.visualstudio.com/docs/configure/settings#_settings-json-file.
- Analyze Tech Stack: Identify languages and tools in use.
- Iterative Configuration: Propose settings one by one.
- Generate File: Write the configuration to
.vscode/settings.json.
1. Context Analysis
- Documentation: Read the fetched documentation to understand the latest schema and features.
- Identify the primary programming languages.
- Detect formatters (Prettier, Black, Gofmt) and Linters (ESLint, Ruff).
2. Iterative Configuration (Loop)
DO NOT generate the full file immediately. You must propose settings one at a time to avoid overwhelming the user.
- Pick a Setting: Select a recommended setting (e.g.,
editor.formatOnSave).
- Propose: Explain why it is needed. "I recommend enabling
Format On Save to ensure consistency. Do you agree?"
- Wait: Wait for user confirmation.
- Repeat: Continue to the next setting (e.g., Linting, Exclusions).
3. Output
Only after the user has confirmed the settings, generate the valid JSON content for .vscode/settings.json.
{
"editor.formatOnSave": true
// ... specific settings
}
