In a previous hands-on articles, we built agents using local LLMs, and another article hands-on with AI-Integrated Development Environment using Claude Code. This article continues that journey, Here the focus is different: 👉 How Claude Code becomes an Agent Platform — not just a coding assistant. In this article, we will teach Claude how to work with us. We will progressively build: Skills, Agents, MCP tools, Plugin integrations amd by the end, Claude will act as: an About-Me agent, a Books price agent, and an externally powered MCP agent

Integrated Development Environments (IDEs) have played a crucial role in shaping the way software is developed. Engineering Practices such as Agile development, eXtreme Programming, Test-Driven Development (TDD), became practical largely because IDEs provided a visual and integrated workflow for writing and managing code. In the early days, developers interacting heavily on command-line. Formatting code, navigating files, searching references, and refactoring logic were mostly manual tasks. Over time, IDEs transformed this experience.

This article is in continuation of Static Code Analysis for Unity3D — Part 1 where we talked about setting up a local sonar server, sonar scanner and running the analysis for a Unity3D project. It this article, we will discuss setting up the Static Code Analysis with SonarCube in IDE — Rider. We are using Rider as the “External Script Editor” in Unity. Configure Rider here in Unity> Preferences > External Tools > External Script Editor.