daBongo LMS AI Training Courses

← Back to Course

Claude Code in Your Development Flow

Lesson 1: Integrating Claude Code with Your Tools and IDE

Lesson Objectives

By the end of this lesson, students should be able to:

  • Configure Claude Code's IDE extension for VS Code or JetBrains
  • Use Claude Code from within the IDE without switching to a separate terminal
  • Integrate Claude Code into a git-based workflow
  • Configure CLAUDE.md to reflect their team's existing conventions

Lesson Content

IDE integration options.

Claude Code offers IDE extensions for VS Code and JetBrains products (verify current extension availability and installation at docs.anthropic.com). The extension surfaces Claude Code within the IDE environment – typically as a side panel or inline chat – reducing context switching compared to a separate terminal window.

For developers with established terminal-first workflows, the standalone terminal mode is fully featured and does not require the extension. Choose based on your existing workflow, not convenience at installation time.

VS Code integration.

The Claude Code VS Code extension (verify current extension name and installation in the VS Code marketplace) provides:

  • A panel for Claude Code conversations within VS Code
  • Context-aware assistance (Claude knows which file you have open)
  • Inline code suggestion acceptance or rejection
  • Integration with the VS Code source control view for reviewing proposed changes

JetBrains integration.

The JetBrains plugin (verify current plugin name and compatibility in the JetBrains Marketplace) provides equivalent functionality within IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs. Check current support for your specific IDE version.

Claude Code in a git workflow.

Claude Code integrates naturally with git:

  • Ask Claude to review a diff before committing: "Review this git diff for potential issues"
  • Use Claude to write commit messages: "Write a conventional commit message for this diff"
  • Ask Claude to summarize what a branch has changed: "Summarize the changes in this git diff"

Claude Code does not have direct git integration by default – it reads diffs you share with it or can run git commands via shell in Code mode. Configure your git workflow explicitly.

Updating CLAUDE.md for team conventions.

When joining a team codebase, the most valuable CLAUDE.md content is team-specific:

  • The team's preferred patterns and approaches (not just the language)
  • The PR review checklist items that come up most often
  • The things that were done before that we no longer do
  • The specific test patterns the team uses

A CLAUDE.md that reflects how your team actually works produces Claude output that fits your codebase – rather than generic well-styled output that then needs restyling to fit the team.

Practical Example

A TypeScript developer joins a team using JetBrains WebStorm with strict ESLint rules, a specific import ordering convention, and a custom test helper pattern.

She installs the JetBrains plugin, configures Claude Code with a CLAUDE.md that includes the team's ESLint config file location, the import ordering rule, and two examples of the test helper pattern.

Her first PR uses Claude Code for test generation – and the tests use the team's test helper pattern because she included it in CLAUDE.md.

No restyling required.

The CLAUDE.md onboarding investment: forty-five minutes.

Safety Notes

IDE extensions for Claude Code request permissions to read files and potentially execute commands within the IDE environment. Review the specific permissions an extension requests before installing – particularly in environments with sensitive files (credentials, private keys, proprietary code). Verify current permission models for IDE extensions at docs.anthropic.com.

Log in and enroll to access lesson quizzes.

← Back to Course

Scroll to Top