chore: update MCP configuration and add Nx guidelines

- Update nx-mcp command format in .mcp.json
- Add Nx configuration section to CLAUDE.md
- Create AGENTS.md with Nx guidelines
- Improve formatting in CLAUDE.md

.mcp.json

@@ -1,22 +1,22 @@
-{
-  "mcpServers": {
-    "context7": {
-      "type": "http",
-      "url": "https://mcp.context7.com/mcp"
-    },
-    "nx-mcp": {
-      "type": "stdio",
-      "command": "npx",
-      "args": ["nx-mcp@latest"]
-    },
-    "angular-mcp": {
-      "type": "stdio",
-      "command": "npx",
-      "args": ["@angular/cli", "mcp"]
-    },
-    "figma-desktop": {
-      "type": "http",
-      "url": "http://127.0.0.1:3845/mcp"
-    }
-  }
-}
+{
+  "mcpServers": {
+    "context7": {
+      "type": "http",
+      "url": "https://mcp.context7.com/mcp"
+    },
+    "nx-mcp": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["nx", "mcp"]
+    },
+    "angular-mcp": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["@angular/cli", "mcp"]
+    },
+    "figma-desktop": {
+      "type": "http",
+      "url": "http://127.0.0.1:3845/mcp"
+    }
+  }
+}

AGENTS.md

@@ -0,0 +1,13 @@
+<!-- nx configuration start-->
+<!-- Leave the start & end comments to automatically receive updates. -->
+
+# General Guidelines for working with Nx
+
+- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
+- You have access to the Nx MCP server and its tools, use them to help the user
+- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
+- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
+- For questions around nx configuration, best practices or if you're unsure, use the `nx_docs` tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
+- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
+
+<!-- nx configuration end-->

CLAUDE.md

@@ -5,6 +5,7 @@ This file contains meta-instructions for how Claude should work with the ISA-Fro
 ## 🔴 CRITICAL: Mandatory Agent Usage
 
 **You MUST use these subagents for ALL research and knowledge management tasks:**
+
 - **`docs-researcher`**: For ALL documentation (packages, libraries, READMEs)
 - **`docs-researcher-advanced`**: Auto-escalate when docs-researcher fails
 - **`Explore`**: For ALL code pattern searches and multi-file analysis
@@ -14,6 +15,7 @@ This file contains meta-instructions for how Claude should work with the ISA-Fro
 ## Communication Guidelines
 
 **Keep answers concise and focused:**
+
 - Provide direct, actionable responses without unnecessary elaboration
 - Skip verbose explanations unless specifically requested
 - Focus on what the user needs to know, not everything you know
@@ -26,13 +28,13 @@ This file contains meta-instructions for how Claude should work with the ISA-Fro
 
 ### Required Agent Usage
 
-| Task Type | Required Agent | Escalation Path |
-|-----------|---------------|-----------------|
-| **Package/Library Documentation** | `docs-researcher` | → `docs-researcher-advanced` if not found |
-| **Internal Library READMEs** | `docs-researcher` | Keep context clean |
-| **Code Pattern Search** | `Explore` | Set thoroughness level |
-| **Implementation Analysis** | `Explore` | Multiple file analysis |
-| **Single Specific File** | Read tool directly | No agent needed |
+| Task Type                         | Required Agent     | Escalation Path                           |
+| --------------------------------- | ------------------ | ----------------------------------------- |
+| **Package/Library Documentation** | `docs-researcher`  | → `docs-researcher-advanced` if not found |
+| **Internal Library READMEs**      | `docs-researcher`  | Keep context clean                        |
+| **Code Pattern Search**           | `Explore`          | Set thoroughness level                    |
+| **Implementation Analysis**       | `Explore`          | Multiple file analysis                    |
+| **Single Specific File**          | Read tool directly | No agent needed                           |
 
 ### Documentation Research System (Two-Tier)
 
@@ -57,3 +59,17 @@ This file contains meta-instructions for how Claude should work with the ISA-Fro
 ```
 
 **Remember: Using subagents is NOT optional - it's mandatory for maintaining context efficiency and search quality.**
+
+<!-- nx configuration start-->
+<!-- Leave the start & end comments to automatically receive updates. -->
+
+# General Guidelines for working with Nx
+
+- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
+- You have access to the Nx MCP server and its tools, use them to help the user
+- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
+- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
+- For questions around nx configuration, best practices or if you're unsure, use the `nx_docs` tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
+- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
+
+<!-- nx configuration end-->