speccrew 0.6.69 → 0.7.1

package/.speccrew/skills/{speccrew-knowledge-bizs-api-analyze-xml/SKILL.md → speccrew-knowledge-bizs-api-analyze/workflow.agentflow.xml}

@@ -1,113 +1,3 @@
----
-name: speccrew-knowledge-bizs-api-analyze-xml
-description: Analyze a single API controller from source code to extract business features and generate API documentation using XML Block workflow. Used by Worker Agent in parallel execution during knowledge base initialization Stage 2. Each worker analyzes one API controller file.
-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# API Feature Analysis - Single Controller (XML Block Workflow)
-
-> **CRITICAL CONSTRAINT**: DO NOT create temporary scripts, batch files, or workaround code files (`.py`, `.bat`, `.sh`, `.ps1`, etc.) under any circumstances. If execution encounters errors, STOP and report the exact error. Fixes must be applied to the Skill definition or source scripts — not patched at runtime.
-
-Analyze one specific API controller from source code, extract all business features (API endpoints), and generate feature documentation. This skill operates at controller granularity - one worker per controller file.
-
-## Trigger Scenarios
-
-- "Analyze API controller {fileName} from source code"
-- "Extract API features from controller {fileName}"
-- "Generate documentation for API controller {fileName}"
-- "Analyze API feature from features.json"
-
-## Input Variables
-
-| Variable | Type | Description | Example |
-|----------|------|-------------|---------|
-| `${feature}` | object | Complete feature object from features.json | - |
-| `${fileName}` | string | Controller file name | `"UserController"`, `"OrderController"` |
-| `${sourcePath}` | string | Relative path to source file | `"yudao-module-system/yudao-module-system-biz/src/main/java/cn/iocoder/yudao/module/system/controller/admin/user/UserController.java"` |
-| `${documentPath}` | string | Target path for generated document | `"speccrew-workspace/knowledges/bizs/admin-api/system/user/UserController.md"` |
-| `${module}` | string | Business module name (from feature.module) | `"system"`, `"trade"`, `"_root"` |
-| `${analyzed}` | boolean | Analysis status flag | `true` / `false` |
-| `${platform_type}` | string | Platform type | `"admin-api"`, `"app-api"` |
-| `${platform_subtype}` | string | Platform subtype | `"spring-boot"`, `"java"` |
-| `${tech_stack}` | array | Platform tech stack | `["java", "spring-boot", "mybatis-plus"]` |
-| `${completed_dir}` | string | Marker files output directory | `"speccrew-workspace/knowledges/base/sync-state/knowledge-bizs/completed"` |
-| `${sourceFile}` | string | Source features JSON file name | `"features-admin-api.json"` |
-| `${language}` | string | Target language for content | `"zh"`, `"en"` |
-
-## Language Adaptation
-
-**CRITICAL**: Generate all content in the language specified by the `${language}` parameter.
-
-- `${language} == "zh"` → Generate all content in 中文
-- `${language} == "en"` → Generate all content in English
-- Other languages → Use the specified language
-
-**All output content (feature names, descriptions, business rules) must be in the target language only.**
-
-## Output Variables
-
-| Variable | Type | Description |
-|----------|------|-------------|
-| `${status}` | string | Analysis status: `"success"`, `"partial"`, or `"failed"` |
-| `${feature_name}` | string | Name of the analyzed controller |
-| `${generated_file}` | string | Path to the generated documentation file |
-| `${message}` | string | Summary message for status update |
-
-## Execution Requirements
-
-This skill operates in **strict sequential execution mode**:
-- Execute steps in exact order (Step 1 → Step 2 → ... → Step 7)
-- Output step status after each step completion
-- Do NOT skip any step
-
-## Output
-
-**Generated Files:**
-1. `${documentPath}` - Controller documentation file
-2. `${completed_dir}/{module}-{subpath}-{fileName}.done.json` - Completion status marker
-
-**Graph Data Generation:**
-Graph data (nodes, edges) construction is handled by `speccrew-knowledge-bizs-api-graph-xml` Skill.
-After completing API analysis, dispatch will invoke the graph skill to generate `.graph.json` files.
-
-**See Also:**
-- `speccrew-knowledge-bizs-api-graph-xml` - Constructs knowledge graph data from API analysis results
-
-**Return Value:**
-```json
-{
-  "status": "success|partial|failed",
-  "feature": {
-    "fileName": "UserController",
-    "sourcePath": "yudao-module-system/.../controller/admin/user/UserController.java"
-  },
-  "platformType": "admin-api",
-  "module": "system",
-  "featureName": "user-management-api",
-  "generatedFile": "speccrew-workspace/knowledges/bizs/admin-api/system/user/UserController.md",
-  "message": "Successfully analyzed UserController with 8 API endpoints"
-}
-```
-
-The return value is used by dispatch to update the feature status in `features-{platform}.json`.
-
-## Execution Checklist
-
-Before executing the workflow, verify the following inputs:
-
-- Controller: `${fileName}` (`${sourcePath}`)
-- Target: `${documentPath}`
-- Language: `${language}`
-- Module: `${module}`
-- Platform: `${platform_type}`/`${platform_subtype}`
-- Completed Dir: `${completed_dir}`
-- Source File: `${sourceFile}`
-
-## Workflow
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
-
-```xml
 <?xml version="1.0" encoding="UTF-8"?>
 <workflow id="api-controller-analysis" status="pending" version="1.0" desc="API controller analysis workflow">
   
@@ -590,7 +480,7 @@ Before executing the workflow, verify the following inputs:
   
   <!-- Dispatch to Graph Skill for .graph.json -->
   <block type="task" id="B32" action="dispatch-to-worker" desc="Dispatch graph generation">
-    <field name="skill">speccrew-knowledge-bizs-api-graph-xml</field>
+    <field name="skill">speccrew-knowledge-bizs-api-graph</field>
     <field name="parameters">
       <field name="controllerFile">${fileName}</field>
       <field name="sourcePath">${sourcePath}</field>
@@ -661,46 +551,3 @@ Before executing the workflow, verify the following inputs:
   </block>
   
 </workflow>
-```
-
-## Reference Guides
-
-### Mermaid Guide
-
-When generating Mermaid diagrams, follow compatibility guidelines:
-- Use `graph TB` or `graph LR` syntax (not `flowchart`)
-- No parentheses `()` in node text
-- No HTML tags like `<br/>`
-- No `style` definitions
-
-### Business Flow Guidelines
-
-- One diagram per API request
-- Focus on business operations
-- Refer to `templates/FEATURE-DETAIL-TEMPLATE.md`
-
-## Constraints
-
-1. **DO NOT analyze files outside the specified `${sourcePath}`**
-2. **DO NOT generate separate documents for internal/private methods**
-3. **All content MUST be in the language specified by `${language}`**
-4. **Use `search_replace` for section filling, NEVER rewrite entire document**
-5. **Mermaid diagrams MUST follow the rules in `mermaid-rule.md`**
-6. **All links MUST use relative paths, NEVER `file://` protocol**
-7. **Marker files MUST follow naming convention: `{module}-{subpath}-{fileName}.done.json`**
-8. **fileName in .done.json MUST NOT include file extension**
-9. **ALL paths in JSON MUST be relative, not absolute**
-
-## Checklist
-
-- [ ] Template file selected based on `${tech_stack}`
-- [ ] Template content read successfully
-- [ ] Controller file read and analyzed
-- [ ] API endpoints extracted with business flows
-- [ ] API consumers found
-- [ ] Template copied to document path
-- [ ] All sections filled using search_replace
-- [ ] All content in target language (`${language}`)
-- [ ] Results reported in JSON format
-- [ ] .done.json marker file written successfully
-- [ ] .graph.json generation dispatched to graph skill

package/.speccrew/skills/speccrew-knowledge-bizs-api-graph/SKILL.md

@@ -1,15 +1,19 @@
 ---
 name: speccrew-knowledge-bizs-api-graph
-description: Constructs knowledge graph data (nodes, edges, relationships) from API analysis results. Generates graph JSON files and completion markers for the bizs knowledge pipeline.
+description: Constructs knowledge graph data (nodes, edges, relationships) from API analysis results using XML workflow blocks. Generates graph JSON files and completion markers for the bizs knowledge pipeline.
 tools: Read, Write, Glob, Grep, Bash
 ---
 
-# API Knowledge Graph Constructor
+# API Knowledge Graph Constructor (XML Workflow)
 
 > **CRITICAL CONSTRAINT**: DO NOT create temporary scripts, batch files, or workaround code files (`.py`, `.bat`, `.sh`, `.ps1`, etc.) under any circumstances. If execution encounters errors, STOP and report the exact error. Fixes must be applied to the Skill definition or source scripts — not patched at runtime.
 
 Construct knowledge graph data structures (nodes and edges) from API analysis results. This skill transforms structured API documentation into graph JSON format for knowledge base integration.
 
+## Language Adaptation
+
+This skill automatically adapts to the user's input language. All documentation and output will be generated in the same language as the user's query.
+
 ## Trigger Scenarios
 
 - "Construct graph data from API analysis results"
@@ -42,7 +46,7 @@ Construct knowledge graph data structures (nodes and edges) from API analysis re
 ## Execution Requirements
 
 This skill operates in **strict sequential execution mode**:
-- Execute steps in exact order (Step 1 → Step 2 → ... → Step 5)
+- Execute steps in exact order (Step 1 → Step 2 → ... → Step 6)
 - Output step status after each step completion
 - Do NOT skip any step
 
@@ -65,70 +69,71 @@ This skill operates in **strict sequential execution mode**:
 }
 ```
 
-## Workflow
-
-```mermaid
-graph TB
-    Start([Start]) --> Step1[Step 1 Read API Analysis Document]
-    Step1 --> Step2[Step 2 Extract Graph Nodes]
-    Step2 --> Step3[Step 3 Extract Graph Edges]
-    Step3 --> Step4[Step 4 Write Graph JSON]
-    Step4 --> Step5[Step 5 Write Graph Completion Marker]
-    Step5 --> Step6[Step 6 Report Results]
-    Step6 --> End([End])
-```
+## AgentFlow Definition
 
----
+<!-- @agentflow: workflow.agentflow.xml -->
 
-### Step 1: Read API Analysis Document
+## Node ID Naming Convention
 
-**Step 1 Status: 🔄 IN PROGRESS**
+```
+{type}-{module}-{name}
 
-**Actions:**
+Examples:
+  api-system-user-list
+  api-system-user-create
+  service-system-user-service
+  table-system-system_user
+  dto-system-user-create-req
+```
 
-1. **Read the API analysis document** from `{{api_analysis_path}}`
+## Marker File Naming Convention
 
-2. **Parse the document structure** to extract:
-   - API endpoints (method, path, description)
-   - Service references
-   - Database tables accessed
-   - DTOs used
-   - Business rules and permissions
+```
+{output_dir}/{module}-{subpath}-{fileName}.graph.json
+```
 
-3. **Validate required information** is present for graph construction
+**How to Extract Each Component:**
 
-**Output:** "Step 1 Status: ✅ COMPLETED - Read {{api_analysis_path}} ({{lineCount}} lines), Found {{endpointCount}} endpoints"
+1. **module**: Use `{{module}}` input variable directly (e.g., `system`, `trade`, `ai`)
 
----
+2. **subpath**: Extract from `{{sourcePath}}`:
+   - For Java: Remove package prefix up to the business layer (e.g., `controller/admin/`, `controller/app/`)
+   - Remove the file name at the end
+   - Replace path separators (`/`) with hyphens (`-`)
+   - If the file is at module root, subpath will be empty → omit from filename
 
-### Step 2: Extract Graph Nodes
+3. **fileName**: Use `{{fileName}}` input variable (class name WITHOUT extension)
 
-**Step 2 Status: 🔄 IN PROGRESS**
+**Examples:**
 
-Based on the API analysis document, extract graph nodes for each entity type.
+| sourcePath | module | subpath | fileName | Marker Filename |
+|------------|--------|---------|----------|-----------------|
+| `yudao-module-system/.../controller/admin/notify/NotifyMessageController.java` | `system` | `controller-admin-notify` | `NotifyMessageController` | `system-controller-admin-notify-NotifyMessageController.graph.json` |
+| `yudao-module-system/.../controller/admin/user/UserController.java` | `system` | `controller-admin-user` | `UserController` | `system-controller-admin-user-UserController.graph.json` |
+| `yudao-module-ai/.../controller/admin/chat/ChatConversationController.java` | `ai` | `controller-admin-chat` | `ChatConversationController` | `ai-controller-admin-chat-ChatConversationController.graph.json` |
 
-**Node Types to Extract:**
+## Node Type Reference
 
-| Node Type | Source | ID Format | Context Fields |
-|-----------|--------|-----------|----------------|
-| `api` | Each public API endpoint | `api-{module}-{name}` | `method`, `path`, `params`, `tables`, `permissions` |
-| `service` | Each injected service | `service-{module}-{name}` | `methods`, `dependencies` |
-| `table` | Each database table accessed | `table-{module}-{tableName}` | `fields`, `indexes`, `engine` |
-| `dto` | Each request/response DTO | `dto-{module}-{name}` | `fields`, `validation` |
+| Type | Description | Required Metadata |
+|------|-------------|-------------------|
+| `api` | API endpoint | `method`, `path`, `permissions` |
+| `service` | Service class | `methods` |
+| `table` | Database table | `fields`, `indexes` |
+| `dto` | Data Transfer Object | `fields`, `validation` |
 
-**Node ID Naming Convention:**
-```
-{type}-{module}-{name}
+## Edge Type Reference
 
-Examples:
-  api-system-user-list
-  api-system-user-create
-  service-system-user-service
-  table-system-system_user
-  dto-system-user-create-req
-```
+| Type | Description | Source → Target |
+|------|-------------|-----------------|
+| `operates` | API operates on table | api → table |
+| `invokes` | API calls service | api → service |
+| `references` | API uses DTO | api → dto |
+| `depends-on` | Service dependency | service → service |
+| `maps-to` | DTO maps to table | dto → table |
+
+## Node Structure Examples
 
-**Node Structure:**
+### API Node Example
 ```json
 {
   "id": "api-{module}-{endpoint-name}",
@@ -146,7 +151,7 @@ Examples:
 }
 ```
 
-**Service Node Example:**
+### Service Node Example
 ```json
 {
   "id": "service-{module}-{service-name}",
@@ -161,7 +166,7 @@ Examples:
 }
 ```
 
-**Table Node Example:**
+### Table Node Example
 ```json
 {
   "id": "table-{module}-{table-name}",
@@ -177,7 +182,7 @@ Examples:
 }
 ```
 
-**DTO Node Example:**
+### DTO Node Example
 ```json
 {
   "id": "dto-{module}-{dto-name}",
@@ -193,48 +198,9 @@ Examples:
 }
 ```
 
-**IMPORTANT:**
-- `module` comes from `{{module}}` input variable
-- `name` should be a short, readable slug derived from the entity name
-- Each node must include `sourcePath` and `documentPath` (if applicable)
-- Convert class names to kebab-case for node IDs (e.g., `UserService` → `user-service`)
-
-**Output:** "Step 2 Status: ✅ COMPLETED - Extracted {{nodeCount}} graph nodes ({{apiCount}} APIs, {{serviceCount}} services, {{tableCount}} tables, {{dtoCount}} DTOs)"
-
----
-
-### Step 3: Extract Graph Edges
-
-**Step 3 Status: 🔄 IN PROGRESS**
-
-Based on the API analysis document, extract graph edges representing relationships between nodes.
+## Edge Structure Examples
 
-**Edge Types to Extract:**
-
-| Edge Type | Direction | When to Create |
-|-----------|-----------|----------------|
-| `operates` | api → table | API endpoint reads/writes a database table |
-| `invokes` | api → service | Controller calls a service method |
-| `references` | api → dto | API endpoint uses a request/response DTO |
-| `depends-on` | service → service | Service depends on another service |
-| `maps-to` | dto → table | DO/Entity maps to database table |
-
-**Edge Structure:**
-```json
-{
-  "source": "api-system-user-create",
-  "target": "table-system-system_user",
-  "type": "operates",
-  "metadata": {
-    "operation": "INSERT",
-    "description": "Create new user record"
-  }
-}
-```
-
-**Edge Examples:**
-
-1. **API → Table (operates):**
+### API to Table Edge (operates)
 ```json
 {
   "source": "api-system-user-list",
@@ -247,7 +213,7 @@ Based on the API analysis document, extract graph edges representing relationshi
 }
 ```
 
-2. **API → Service (invokes):**
+### API to Service Edge (invokes)
 ```json
 {
   "source": "api-system-user-create",
@@ -260,7 +226,7 @@ Based on the API analysis document, extract graph edges representing relationshi
 }
 ```
 
-3. **API → DTO (references):**
+### API to DTO Edge (references)
 ```json
 {
   "source": "api-system-user-create",
@@ -273,7 +239,7 @@ Based on the API analysis document, extract graph edges representing relationshi
 }
 ```
 
-4. **Service → Service (depends-on):**
+### Service to Service Edge (depends-on)
 ```json
 {
   "source": "service-system-user-service",
@@ -285,7 +251,7 @@ Based on the API analysis document, extract graph edges representing relationshi
 }
 ```
 
-5. **DTO → Table (maps-to):**
+### DTO to Table Edge (maps-to)
 ```json
 {
   "source": "dto-system-user-do",
@@ -297,185 +263,28 @@ Based on the API analysis document, extract graph edges representing relationshi
 }
 ```
 
-**Output:** "Step 3 Status: ✅ COMPLETED - Extracted {{edgeCount}} graph edges"
-
----
-
-### Step 4: Write Graph JSON
-
-**Step 4 Status: 🔄 IN PROGRESS**
-
-Write the complete graph data to JSON file.
-
-**Marker File Naming Convention:**
-```
-{output_dir}/{module}-{subpath}-{fileName}.graph.json
-```
-
-**How to Extract Each Component:**
-
-1. **module**: Use `{{module}}` input variable directly (e.g., `system`, `trade`, `ai`)
-
-2. **subpath**: Extract from `{{sourcePath}}`:
-   - For Java: Remove package prefix up to the business layer (e.g., `controller/admin/`, `controller/app/`)
-   - Remove the file name at the end
-   - Replace path separators (`/`) with hyphens (`-`)
-   - If the file is at module root, subpath will be empty → omit from filename
+## Pre-write Verification Checklist
 
-3. **fileName**: Use `{{fileName}}` input variable (class name WITHOUT extension)
-
-**Examples:**
-
-| sourcePath | module | subpath | fileName | Marker Filename |
-|------------|--------|---------|----------|-----------------|
-| `yudao-module-system/.../controller/admin/notify/NotifyMessageController.java` | `system` | `controller-admin-notify` | `NotifyMessageController` | `system-controller-admin-notify-NotifyMessageController.graph.json` |
-| `yudao-module-system/.../controller/admin/user/UserController.java` | `system` | `controller-admin-user` | `UserController` | `system-controller-admin-user-UserController.graph.json` |
-| `yudao-module-ai/.../controller/admin/chat/ChatConversationController.java` | `ai` | `controller-admin-chat` | `ChatConversationController` | `ai-controller-admin-chat-ChatConversationController.graph.json` |
-
-**CRITICAL - API Endpoint Coverage Check:**
-Before writing the graph.json file, verify:
-- [ ] ALL public API endpoint methods in the controller are represented as `api` nodes
-- [ ] Status update endpoints (updateStatus, toggleEnable) are included
-- [ ] Special operation endpoints (resetPassword, export, import, batch operations) are included
-- [ ] Each `api` node has proper metadata with HTTP method and path
-- [ ] No public endpoint method is left without a corresponding node
-
-**Pre-write Verification (MUST check before writing):**
+### Graph JSON Verification:
 - [ ] Root-level `module` field is present (MANDATORY)
 - [ ] `nodes` and `edges` are arrays (can be empty)
 - [ ] Valid JSON (no trailing commas, all strings quoted)
 - [ ] All node IDs are unique
 - [ ] All edge source/target references point to valid node IDs
 
-**Complete JSON Template:**
-```json
-{
-  "module": "{{module}}",
-  "nodes": [
-    {
-      "id": "api-{module}-{endpoint-name}",
-      "type": "api",
-      "name": "<display name>",
-      "module": "{{module}}",
-      "sourcePath": "{{sourcePath}}",
-      "documentPath": "{{api_analysis_path}}",
-      "description": "...",
-      "metadata": {
-        "method": "GET",
-        "path": "/admin-api/system/user/page",
-        "permissions": ["system:user:query"]
-      }
-    }
-  ],
-  "edges": [
-    {
-      "source": "api-...",
-      "target": "service-...",
-      "type": "invokes",
-      "metadata": { ... }
-    }
-  ]
-}
-```
-
-**⚠️ CRITICAL - Module Field Requirement:**
-- The `.graph.json` file **MUST** have a root-level `module` field
-- Do NOT assume scripts will fall back to reading from `.done` file
-- Missing `module` field will cause the graph merge pipeline to reject this file
-
-**⚠️ CRITICAL - Path Format:**
-- `sourcePath` in nodes: Relative path (as-is from input)
-- `documentPath` in nodes: Relative path (as-is from input)
-- NEVER convert relative paths to absolute paths in JSON content
-
-**Full Path Example:**
-`d:/dev/speccrew/speccrew-workspace/knowledges/base/sync-state/knowledge-bizs/completed/system-controller-admin-user-UserController.graph.json`
-
-**Output:** "Step 4 Status: ✅ COMPLETED - Graph JSON written to {{output_dir}}/{module}-{subpath}-{fileName}.graph.json ({{fileSize}} bytes)"
-
----
-
-### Step 5: Write Graph Completion Marker
-
-**Step 5 Status: 🔄 IN PROGRESS**
-
-Write the `.graph-done.json` completion marker file to signal successful graph data generation.
-
-**Marker File Path:**
-
-```
-{output_dir}/{module}-{subpath}-{fileName}.graph-done.json
-```
-
-**Marker JSON Structure:**
-
-```json
-{
-  "fileName": "{{fileName}}",
-  "module": "{{module}}",
-  "marker": "graph_completed",
-  "graphFile": "{module}-{subpath}-{fileName}.graph.json",
-  "nodeCount": {{node_count}},
-  "edgeCount": {{edge_count}},
-  "status": "completed"
-}
-```
-
-**Field Descriptions:**
-
-| Field | Description | Example |
-|-------|-------------|---------|
-| `fileName` | Feature file name WITHOUT extension | `"UserController"` |
-| `module` | Business module name | `"system"` |
-| `marker` | Fixed marker type | `"graph_completed"` |
-| `graphFile` | Corresponding graph JSON filename | `"system-controller-admin-user-UserController.graph.json"` |
-| `nodeCount` | Number of nodes in graph | `15` |
-| `edgeCount` | Number of edges in graph | `23` |
-| `status` | Completion status | `"completed"` |
+### API Endpoint Coverage Check:
+- [ ] ALL public API endpoint methods in the controller are represented as `api` nodes
+- [ ] Status update endpoints (updateStatus, toggleEnable) are included
+- [ ] Special operation endpoints (resetPassword, export, import, batch operations) are included
+- [ ] Each `api` node has proper metadata with HTTP method and path
+- [ ] No public endpoint method is left without a corresponding node
 
-**Pre-write Verification:**
+### Completion Marker Verification:
 - [ ] Filename follows `{module}-{subpath}-{fileName}.graph-done.json` pattern
 - [ ] JSON is valid
 - [ ] All required fields are present
 - [ ] `nodeCount` and `edgeCount` match actual graph data
 
-**Output:** "Step 5 Status: ✅ COMPLETED - Graph completion marker written to {{output_dir}}/{module}-{subpath}-{fileName}.graph-done.json"
-
----
-
-### Step 6: Report Results
-
-**Step 6 Status: 🔄 IN PROGRESS**
-
-Return graph construction result summary to dispatch:
-
-```json
-{
-  "status": "success",
-  "module": "{{module}}",
-  "fileName": "{{fileName}}",
-  "graphFile": "{{output_dir}}/{module}-{subpath}-{fileName}.graph.json",
-  "nodeCount": {{node_count}},
-  "edgeCount": {{edge_count}},
-  "message": "Generated graph data with {{node_count}} nodes and {{edge_count}} edges"
-}
-```
-
-Or in case of failure:
-
-```json
-{
-  "status": "failed",
-  "module": "{{module}}",
-  "fileName": "{{fileName}}",
-  "message": "{{error_message}}"
-}
-```
-
-**Output:** "Step 6 Status: ✅ COMPLETED - Graph construction {{status}}: {{message}}"
-
----
-
 ## Constraints
 
 1. **Single Document Input**: This skill processes ONE API analysis document at a time
@@ -484,22 +293,3 @@ Or in case of failure:
 4. **Node Uniqueness**: Each node ID must be unique within the graph
 5. **Edge Validity**: Edge source/target must reference existing node IDs
 6. **Path Format**: Use relative paths, NEVER absolute paths in JSON content
-
-## Node Type Reference
-
-| Type | Description | Required Metadata |
-|------|-------------|-------------------|
-| `api` | API endpoint | `method`, `path`, `permissions` |
-| `service` | Service class | `methods` |
-| `table` | Database table | `fields`, `indexes` |
-| `dto` | Data Transfer Object | `fields`, `validation` |
-
-## Edge Type Reference
-
-| Type | Description | Source → Target |
-|------|-------------|-----------------|
-| `operates` | API operates on table | api → table |
-| `invokes` | API calls service | api → service |
-| `references` | API uses DTO | api → dto |
-| `depends-on` | Service dependency | service → service |
-| `maps-to` | DTO maps to table | dto → table |