smith-ide

Convert conceptual path variables into IDE-specific syntax for VS Code and JetBrains.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/tianjianjiang/smith --skill smith-ide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-ide
Source: https://github.com/tianjianjiang/smith/tree/main/smith-ide
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-ide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts conceptual path variables into IDE-specific syntax to ensure consistent configuration across editors.

Core Features & Use Cases

  • Centralized variable translation: maps $WORKSPACE_ROOT, $REPO_ROOT, and $HOME to IDE-specific syntax for VS Code-based IDEs and JetBrains.
  • Cross-editor compatibility: supports VS Code, Cursor, Kiro, and JetBrains environments with both workspace and project-level setups.
  • Guided integration: references style and prerequisites to align configurations with smith-style, smith-principles, and smith-standards.

Quick Start

Configure a sample project in your IDE and verify that conceptual path variables are translated to the IDE syntax.

Frequently Asked Questions about smith-ide

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

FAQPage Schema
How do I convert conceptual path variables to IDE syntax for VS Code and JetBrains?

Path variable translation maps $WORKSPACE_ROOT, $REPO_ROOT, and $HOME to IDE-specific syntax, solving inconsistent configuration across different editors. It ensures workspace and project setups remain uniform across VS Code-based environments and JetBrains IDEs.

Does path variable translation work with Cursor and Kiro IDEs?

Path variable translation works with Cursor and Kiro IDEs. It supports VS Code-based environments, including VS Code, Cursor, and Kiro, alongside JetBrains IDEs, applying consistent variable mapping for both workspace and project-level configurations.

What conceptual path variables are mapped to IDE-specific syntax?

The conceptual path variables mapped to IDE-specific syntax include $WORKSPACE_ROOT, $REPO_ROOT, and $HOME. These variables are translated to match the specific syntax requirements of VS Code-based environments and JetBrains IDEs.

Do I need prerequisites to configure cross-editor path variables?

Configuring cross-editor path variables requires prerequisites from smith-principles, smith-standards, and smith-style SKILL entries. These define the necessary path-references and best practices to align configurations before applying the IDE-specific syntax translation.

Why are my workspace path configurations inconsistent between VS Code and JetBrains?

Workspace path configurations become inconsistent between VS Code and JetBrains due to differing IDE-specific syntax requirements. Translating conceptual variables like $WORKSPACE_ROOT into each editor's native format resolves these cross-editor compatibility issues.