Merge pull request #5206 from ag-grid/ajt/fix-gemini-prompt-config

Fix Gemini /docs-review prompt.

Author: AG-DavidG

.gitignore

@@ -68,4 +68,5 @@ vitest.config.*.timestamp*
 /.github/prompts/
 /.github/instructions/
 /.mcp.json
+/.vscode/mcp.json
 .tmp

tools/prompts/AGENTS.md

@@ -8,7 +8,7 @@ AG Charts is a sophisticated TypeScript monorepo providing canvas-based JavaScri
 
 ## Technology Stack
 
-For detailed information about preferred technologies and architectural constraints, see [`tools/prompts/technology-stack.md`](tools/prompts/technology-stack.md).
+For detailed information about preferred technologies and architectural constraints, see [Technology Stack](tools/prompts/technology-stack.md).
 
 **Key Constraint:** The main AG Charts libraries must have ZERO third-party runtime dependencies.
 
@@ -46,6 +46,15 @@ nx benchmark <package>       # Performance benchmarks
 nx lint <package>           # ESLint + custom rules
 ```
 
+## Slash Commands
+
+NOTE: These are only intended for agentic tools that don't support custom slash commands, such as Cursor or Codex.
+
+-   `/spruce-example` - execute `tools/prompts/commands/spruce-example.md` on specified example.
+-   `/pr-review` - execute `tools/prompts/commands/pr-review.md` on specified PR.
+-   `/release-options-review` - execute `tools/prompts/commands/release-options-review.md` on specified release options.
+-   `/docs-review` - execute `tools/prompts/commands/docs-review.md` on specified docs.
+
 ## Architecture
 
 ### Monorepo Structure
@@ -225,3 +234,11 @@ nx e2e ag-charts-website
     -   For typechecking docs examples run: `nx run ag-charts-website-${pageName}_${exampleName}_main.ts:typecheck`
 -   For all examples also run: `nx validate-examples` (NOTE: This does a batch `typecheck` which is VERY fast compared to running individual `typecheck` targets).
 -   For adhoc examples to quickly test things or `-test` pages, adding `// @ag-skip-fws` to `main.ts` will disable framework (React, Angylar, Vue) variant generation.
+
+## Releases
+
+-   Releases are typically monthly for minor releases, and 6-monthly for major releases (typically in June and December).
+-   Patch releases are typically only for critical bug fixes, at most weekly.
+-   Minor releases cannot have breaking changes, we must hold these back for major releases.
+    -   Deprecations are allowed, but must be clearly marked as deprecated and still work as before.
+    -   Deprecated features/options are typically immediately removed from public website documentation to discourage use.

tools/prompts/commands/docs-review.md

@@ -29,8 +29,7 @@ Then: **ADAPTIVE MODE** - Allow degraded operation with user confirmation.
 When running in orchestrated mode, ALL tools are REQUIRED:
 
 1. **MCP Puppeteer** - REQUIRED, no fallback
-    - Must be available via `ListMcpResourcesTool`
-    - Test with `mcp__puppeteer__puppeteer_navigate` and `mcp__puppeteer__puppeteer_screenshot`
+    - There tools must be available for testing `puppeteer_navigate` and `puppeteer_screenshot`
 2. **Task tool** - REQUIRED for example-tester delegation
 3. **Read/Write tools** - REQUIRED
 

tools/setup-prompts.sh

@@ -98,7 +98,46 @@ function setup_instructions() {
 function setup_mcp() {
     local target_file=$1
 
-    ln -sf "./tools/prompts/.mcp.json" "$target_file"
+    # Calculate the relative path from target_file to the MCP config
+    local target_dir=$(dirname "$target_file")
+    
+    # Count directory levels in target_file path
+    local dir_count=$(echo "$target_file" | tr -cd '/' | wc -c)
+    
+    # Build relative path with appropriate number of ../ prefixes
+    local relative_path="./"
+    for ((i=0; i<dir_count; i++)); do
+        relative_path="$relative_path../"
+    done
+    
+    # Create symlink with calculated relative path
+    ln -sf "${relative_path}tools/prompts/.mcp.json" "$target_file"
+}
+
+function setup_vscode_mcp() {
+    local target_file=$1
+    local mcp_json_file="./tools/prompts/.mcp.json"
+    
+    # Check if jq is available
+    if ! command -v jq >/dev/null 2>&1; then
+        echo "Warning: jq not found. Cannot update MCP config."
+        echo "Install with: brew install jq"
+        return 1
+    fi
+    
+    # Check if source JSON file exists
+    if [[ ! -f "$target_file" ]]; then
+        mkdir -p $(dirname "$target_file")
+        echo '{"servers": {}}' > "$target_file"
+    fi
+
+    # Add each MCP server from JSON to the target JSON file by reading and then editing the file in place
+    jq -r '.mcpServers | to_entries[] | @base64' "$mcp_json_file" | while read -r entry; do
+        local server_name=$(echo "$entry" | base64 -d | jq -r '.key')
+        local server_config=$(echo "$entry" | base64 -d | jq -r '.value')
+        jq --argjson server_config "$server_config" ".servers += { (\"$server_name\"): \$server_config }" "$target_file" > "$target_file.tmp"
+        mv "$target_file.tmp" "$target_file"
+    done
 }
 
 function setup_codex_mcp() {
@@ -248,6 +287,7 @@ fi
 
 # Copilot setup - not sure if there is a better way to detect?
 if [[ "${TERM_PROGRAM:-}" == "vscode" ]]; then
+    setup_vscode_mcp .vscode/mcp.json
     setup_instructions AGENTS.md
     mkdir -p .github/prompts
     for prompt in pr-review.md release-options-review.md docs-review.md spruce-example.md; do