Getting Started with ContextDX Claude Code Plugin

ContextDX maps your codebase into a living architecture diagram and runs targeted analysis on it — all from Claude Code.

---

Prerequisites

• Claude Code installed and running

---

Setup (one-time)

1. Install the plugin

/install-plugin cdx-code

Use cdx-infra if you're working with AWS CDK infrastructure.

2. Connect to your workboard

/configure

Paste your Binding Token and API Secret from the ContextDX portal.

---

Map your architecture

/analyze

Claude scans your project — detects services, APIs, databases, queues — and maps how they connect. The result is a structured graph of your architecture (L0 overview, 10-30 nodes).

To zoom into a specific node:

/analyze --drill my-project/api-gateway

This creates a child board (L1/L2) for that node with finer-grained components.

To analyze all layers progressively (L0 → L1 → L2):

/analyze --all

Each layer is presented for review before proceeding to the next.

To force a full re-analysis from scratch:

/analyze --clean

---

Push to the portal

/sync

Your architecture appears as a visual diagram on your ContextDX workboard. Nodes show components with their types and descriptions. Edges show how they relate — imports, API calls, data access, event flows.

If you have multiple boards, sync a specific one:

/sync --board my-project-overview

Or sync all boards at once:

/sync --all

---

Run targeted analysis

/insights

Insight templates are defined by your workspace admin on the portal — security checks, quality reviews, dependency audits, and more. Claude fetches the template, analyzes your code against it, and pushes findings back.

Each finding is tied to a specific component on your diagram. Affected areas are highlighted so your team sees impact at a glance.

To see what's available:

/insights --list

To run a specific one:

/insights security-analysis

To run all available templates:

/insights --all

---

Keep it current

After code changes, just re-run:

/analyze
/sync

Analysis is incremental — it detects the git diff since last run and only re-analyzes changed files. This applies to all modes: /analyze, /analyze --drill, and /analyze --all will each update only what changed in existing boards.

Use /analyze --clean if the incremental result looks stale.

---

Check where things stand

/status

Shows configuration, board manifest, analysis summary per board, sync status, and changed files since last analysis.

---

All commands