This Claude skill streamlines IDE configuration by providing precise path variable mappings for VS Code, Cursor, Kiro, and JetBrains. It bridges the gap between conceptual path references and IDE-specific syntax, ensuring that configuration files are accurate, portable, and optimized for cross-platform development environments.

When should I use smith-ide?

smith-ide is useful in the following scenarios: • Case 1: Automatically translating conceptual paths like $WORKSPACE_ROOT into IDE-specific syntax such as ${workspaceFolder} for VS Code or $PROJECT_DIR$ for JetBrains when generating config files. • Case 2: Configuring workspace-specific settings in .vscode/settings.json or .kiro/settings/mcp.json to ensure environment variables are correctly referenced. • Case 3: Standardizing technical documentation by using conceptual variables that can be easily mapped to functional code for different development teams. • Case 4: Migrating project configurations between different IDEs (e.g., from IntelliJ to Cursor) while maintaining correct pathing logic and macro syntax.

name	smith-ide
description	IDE path variable mappings for VS Code, Cursor, Kiro, and JetBrains. Use when writing or editing IDE config files or using path variables. Covers variable translation between conceptual and IDE-specific syntax.

IDE Path Variable Mappings

Scope: Maps conceptual path variables to IDE-specific syntax
Load if: Writing/editing IDE config files (.vscode/, .kiro/, .cursor/) OR using IDE path variables
Prerequisites: @smith-principles/SKILL.md, @smith-standards/SKILL.md, @smith-style/SKILL.md

CRITICAL: Variable Translation (Primacy Zone)

Always use conceptual variables in documentation, translate to IDE-specific syntax in configs:

$WORKSPACE_ROOT → ${workspaceFolder} (VS Code) or $PROJECT_DIR$ (JetBrains)
$HOME → ${userHome} (VS Code) or $USER_HOME$ (JetBrains)

Overview

Maps conceptual path variables to IDE-specific syntax. For variable definitions and usage, see @smith-style/SKILL.md#path-references.

Conceptual Variables

Defined in: @smith-style/SKILL.md#path-references

For path variable definitions ($WORKSPACE_ROOT, $REPO_ROOT, $HOME) and usage patterns, see @smith-style/SKILL.md#path-references.

IDE Syntax Mappings

VS Code-Based IDEs (VS Code, Cursor, Kiro)

Syntax: ${variableName}

Common Variables:

${workspaceFolder} — Workspace root directory
${userHome} — User home directory
${env:VAR} — Environment variable
${config:key} — Settings value

Mappings:

$WORKSPACE_ROOT → ${workspaceFolder}
$REPO_ROOT → ${env:REPO_ROOT} or ${workspaceFolder}/../../../../
$HOME → ${userHome}

Multi-root workspaces: Use ${workspaceFolder:folderName} for specific folders

Configuration:

VS Code/Cursor: .vscode/settings.json
Kiro: .kiro/settings/mcp.json (workspace) or ~/.kiro/settings/mcp.json (global)

Note: Kiro is VS Code-based (Code OSS fork) and inherits VS Code configuration system.

JetBrains IDEs (PyCharm, IntelliJ IDEA)

Syntax: $MACRO_NAME$

Common Macros:

$PROJECT_DIR$ — Project root directory
$USER_HOME$ — User home directory

Mappings:

$WORKSPACE_ROOT → $PROJECT_DIR$
$REPO_ROOT → $PROJECT_DIR$/../../../../ (or custom path variable)
$HOME → $USER_HOME$

Configuration: File → Settings → Appearance & Behavior → Path Variables

Best Practices

Documentation: Always use conceptual variables ($WORKSPACE_ROOT, $REPO_ROOT, $HOME)
IDE Configs: Translate to IDE-specific syntax using above mappings
Cross-IDE Compatibility: Prefer environment variables when possible
Security: Use variable references for sensitive values, never hardcode

Reference

VS Code Variables: Documentation
PyCharm Macros: Documentation
Path Standards: @smith-style/SKILL.md#path-references

ACTION (Recency Zone)

When writing IDE configs:

Use conceptual variables in docs ($WORKSPACE_ROOT)
Translate to IDE syntax in config files
Prefer environment variables for cross-IDE compatibility

smith-ide

When & Why to Use This Skill

Use Cases