archtracker-mcp 0.4.3 → 0.6.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "archtracker-mcp",
-  "version": "0.4.3",
+  "version": "0.6.0",
   "description": "Architecture & Dependency Tracker — MCP server + CLI + interactive web viewer for AI-driven development",
   "type": "module",
   "main": "dist/index.js",

package/skills/arch-analyze/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: arch-analyze
-description: Analyze existing architecture — comprehensive report of an existing project's dependency structure, critical components, circular deps, orphan files, and coupling hotspots. Use when introducing archtracker to an existing project or when you need a full architectural overview.
+description: Analyze existing architecture — comprehensive report of dependency structure, critical components, circular deps, orphan files, and coupling hotspots. Auto-detects multi-layer projects (layers.json). Use when introducing archtracker or when you need a full architectural overview.
 argument-hint: "[target directory, e.g. src]"
 allowed-tools:
   - mcp__archtracker__analyze_existing_architecture
@@ -12,6 +12,10 @@ allowed-tools:
 Perform a comprehensive architecture analysis of the project.
 
 1. Run `analyze_existing_architecture` on the target directory
+   - For multi-layer projects: set `projectRoot` to the project root where `.archtracker/layers.json` exists, and leave `targetDir` as default `"src"` to trigger auto-detection
+   - For single-directory projects: set `targetDir` to the source directory
+   - Optional `topN` parameter to control number of items per section (default: 10, max: 50)
+   - Optional `language` parameter to specify target language (e.g. `python`, `rust`) if auto-detection fails
 2. Present the full report covering:
    - Overview (file count, edge count, circular deps)
    - Critical components (most depended-on files)
@@ -19,10 +23,12 @@ Perform a comprehensive architecture analysis of the project.
    - High coupling files (most imports)
    - Orphan files (isolated, no connections)
    - Directory breakdown
+   - **Multi-layer info** (if detected): layer summary, cross-layer connections
 3. Offer to save a snapshot if one doesn't exist yet
 
-Present results clearly, highlighting:
+Present results in the user's language, highlighting:
 - Architectural risks (circular deps, high coupling)
 - Key files that many components depend on
 - Orphan files that may be dead code
+- Cross-layer dependencies (if multi-layer)
 - Recommendations for improvement

package/skills/arch-check/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: arch-check
-description: Check architecture diff — compare current code against the saved snapshot and report components that may need updates. Use when checking for dependency breakage after code changes.
+description: Check architecture diff — compare current code against the saved snapshot and report components that may need updates. Auto-detects multi-layer projects. Use when checking for dependency breakage after code changes.
 allowed-tools:
   - mcp__archtracker__check_architecture_diff
   - mcp__archtracker__generate_map
@@ -10,13 +10,17 @@ allowed-tools:
 
 Run an architecture diff check for the current project.
 
-1. Generate the current dependency map
-2. Compare it against the saved snapshot
+1. Run `check_architecture_diff`
+   - For multi-layer projects: set `projectRoot` to the project root where `.archtracker/layers.json` exists
+   - Leave `targetDir` as default `"src"` to trigger multi-layer auto-detection
+   - Optional `language` parameter to specify target language (e.g. `python`, `rust`) if auto-detection fails
+2. Compare current code against the saved snapshot
 3. Report any files that have changed and their affected dependents
 
-If no snapshot exists, generate one first and inform the user this is the initial baseline.
+If no snapshot exists, one is auto-generated as the initial baseline.
 
-Present results in Japanese, clearly listing:
-- 変更されたファイル
-- 影響を受ける依存ファイル（要確認）
-- 推奨アクション
+Present results in the user's language, clearly listing:
+- Changed files (added, removed, modified edges)
+- Affected dependent files that may need updates
+- Cross-layer impact (if multi-layer project)
+- Recommended actions

package/skills/arch-context/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: arch-context
-description: Load the current architecture context into the session. Use at the start of a new session or when you need to understand the project structure. Prevents hallucination of old file paths.
+description: Load the current architecture context into the session. Auto-detects multi-layer projects. Use at the start of a new session or when you need to understand the project structure. Prevents hallucination of old file paths.
 allowed-tools:
   - mcp__archtracker__get_current_context
 ---
@@ -10,12 +10,14 @@ allowed-tools:
 Retrieve and display the current project architecture context.
 
 1. Call `get_current_context` to get valid file paths and architecture summary
+   - For multi-layer projects: set `projectRoot` to the project root where `.archtracker/layers.json` exists
 2. Internalize the returned structure so you reference only existing files
 3. Display a brief summary to the user
 
-Present results in Japanese:
-- 現在の有効なファイルパス一覧
-- アーキテクチャの概要サマリー
-- 前回のスナップショットからの経過時間（あれば）
+Present results in the user's language:
+- Valid file paths (organized by layer if multi-layer)
+- Architecture overview summary
+- Time since last snapshot (if available)
+- Layer structure and cross-layer connections (if multi-layer)
 
-**重要**: このコンテキストを元に、以降のセッションでは存在しないファイルパスを参照しないこと。
+**Important**: Use this context to avoid referencing non-existent file paths in subsequent interactions.

package/skills/arch-search/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: arch-search
-description: Search the architecture for files, impact analysis, critical components, or orphans. Use when asking about dependencies, impact of changes, or finding important files.
+description: Search the architecture for files, impact analysis, critical components, or orphans. Works across all layers in multi-layer projects. Use when asking about dependencies, impact of changes, or finding important files.
 argument-hint: [query]
 allowed-tools:
   - mcp__archtracker__search_architecture
@@ -11,14 +11,18 @@ allowed-tools:
 Search the project architecture using $ARGUMENTS.
 
 Available search modes:
-- **path**: Find files matching a pattern (default)
-- **affected**: Find all files affected if a specific file changes
+- **path**: Find files matching a pattern (default). In multi-layer projects, paths are prefixed with layer name (e.g. `Backend/worker.py`)
+- **affected**: Find all files affected if a specific file changes (including cross-layer impact)
 - **critical**: Find the most important files (most depended-on)
 - **orphans**: Find isolated files with no connections
 
 Choose the most appropriate mode based on the user's question and execute the search.
 
-Present results in Japanese with clear formatting:
-- ファイルパスと依存関係の数
-- 検索にマッチした理由
-- 推奨アクション（影響分析の場合）
+Optional parameters:
+- `limit`: Max number of results to return (default: 10, max: 50)
+- `language`: Target language if auto-detection is insufficient (e.g. `python`, `rust`, `java`)
+
+Present results in the user's language with clear formatting:
+- File paths and dependency counts
+- Match reason
+- Recommended actions (for impact analysis)

package/skills/arch-serve/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: arch-serve
+description: Launch the interactive architecture graph viewer in the browser. Visualizes dependency graphs with force-directed layout, convex hull layer grouping, diff highlighting, and hierarchy view. Use when the user wants to see the architecture visually.
+argument-hint: "[port number, e.g. 3000]"
+---
+
+## Launch Architecture Viewer
+
+Start the interactive web-based architecture viewer.
+
+Run the following CLI command via Bash:
+```
+archtracker serve --root <projectRoot> --port <port>
+```
+
+- Default port: 3000
+- For multi-layer projects: use `--root <dir>` pointing to the directory containing `.archtracker/layers.json`
+- For single-directory projects: use `--target <dir>` to specify the source directory
+- Add `--watch` for auto-reload on file changes
+
+The viewer provides:
+- **Graph view**: Force-directed dependency graph with layer grouping (convex hulls), cross-layer links, and layer tab filtering
+- **Hierarchy view**: Depth-based layout showing import hierarchy levels with layer filtering
+- **Diff view**: Visual comparison against saved snapshot highlighting added/removed/modified files
+- **Settings**: Node size, gravity, layer cohesion, link opacity, cross-layer link toggle, theme, and language
+
+After launching, inform the user of the URL (http://localhost:<port>) and available features.

package/skills/arch-snapshot/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: arch-snapshot
-description: Save the current architecture state as a snapshot. Use when the current code state is confirmed good and should be the new baseline.
+description: Save the current architecture state as a snapshot baseline. Auto-detects multi-layer projects (layers.json). Use when the current code state is confirmed good and should be the new baseline for diff checks.
 allowed-tools:
   - mcp__archtracker__generate_map
   - mcp__archtracker__save_architecture_snapshot
@@ -10,11 +10,15 @@ allowed-tools:
 
 Save the current project architecture as the baseline snapshot.
 
-1. Generate the current dependency map
+1. Run `save_architecture_snapshot`
+   - For multi-layer projects: set `projectRoot` to the project root where `.archtracker/layers.json` exists
+   - Leave `targetDir` as default `"src"` to trigger multi-layer auto-detection
+   - Optional `language` parameter to specify target language (e.g. `python`, `rust`) if auto-detection fails
 2. Save it as `.archtracker/snapshot.json`
 3. Confirm the save with a summary
 
-Present results in Japanese:
-- 保存されたファイル数とエッジ数
-- 主要コンポーネント（依存が多いファイルのトップ5）
-- スナップショットのタイムスタンプ
+Present results in the user's language:
+- Saved file count and edge count
+- Key components (top 5 most depended-on files)
+- Snapshot timestamp
+- Layer breakdown (if multi-layer project)