fix: restore MCP tool naming patterns corrupted by prettier

Prettier was converting `__` to `**` in MCP tool names like
`mcp__plugin_name__tool`, treating double underscores as emphasis.

- Restore correct `mcp__` patterns in SKILL.md and tool-usage.md
- Add .prettierignore to exclude these files from prettier formatting

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: sjnims

.prettierignore

@@ -0,0 +1,4 @@
+# MCP integration docs use mcp__plugin_*__* patterns that prettier
+# incorrectly converts __ to ** (treating as emphasis)
+plugins/plugin-dev/skills/mcp-integration/SKILL.md
+plugins/plugin-dev/skills/mcp-integration/references/tool-usage.md

plugins/plugin-dev/skills/mcp-integration/SKILL.md

@@ -376,12 +376,12 @@ Commands use MCP tools with user interaction:
 
 ---
 
-allowed-tools: mcp**plugin_name_server**create_item
+allowed-tools: `mcp__plugin_name_server__create_item`
 
 Steps:
 
 1. Gather item details from user
-2. Use mcp**plugin_name_server**create_item
+2. Use `mcp__plugin_name_server__create_item`
 3. Confirm creation
 ```
 
@@ -396,7 +396,7 @@ Agents use MCP tools autonomously:
 
 Analysis Process:
 
-1. Query data via mcp**plugin_db_server**query
+1. Query data via `mcp__plugin_db_server__query`
 2. Process and analyze results
 3. Generate insights report
 ```
@@ -452,9 +452,9 @@ Always use secure connections:
 Pre-allow only necessary MCP tools:
 
 ```markdown
-✅ allowed-tools: mcp**plugin_api_server**read_data, mcp**plugin_api_server**create_item
+✅ allowed-tools: `mcp__plugin_api_server__read_data`, `mcp__plugin_api_server__create_item`
 
-❌ allowed-tools: mcp**plugin_api_server**\*
+❌ allowed-tools: mcp__plugin_api_server__*
 ```
 
 ### Managed MCP Controls (Enterprise)

plugins/plugin-dev/skills/mcp-integration/references/tool-usage.md

@@ -60,7 +60,7 @@ allowed-tools: mcp__plugin_asana_asana__asana_create_task
 To create a task:
 
 1. Gather task details from user
-2. Use mcp**plugin_asana_asana**asana_create_task with the details
+2. Use mcp__\1__asana_create_task with the details
 3. Confirm creation to user
 ```
 
@@ -98,7 +98,7 @@ allowed-tools: mcp__plugin_asana_asana__asana_search_tasks, mcp__plugin_asana_as
 
 To search for tasks:
 
-1. Use mcp**plugin_asana_asana**asana_search_tasks
+1. Use mcp__\1__asana_search_tasks
 2. Provide search filters (assignee, project, etc.)
 3. Display results to user
 
@@ -112,7 +112,7 @@ To create a task:
    - Project
    - Assignee
    - Due date
-2. Use mcp**plugin_asana_asana**asana_create_task
+2. Use mcp__\1__asana_create_task
 3. Show confirmation with task link
 ```
 
@@ -136,10 +136,10 @@ Autonomous agent for generating Asana project status reports.
 
 ## Process
 
-1. **Query tasks**: Use mcp**plugin_asana_asana**asana_search_tasks to get all tasks
+1. **Query tasks**: Use mcp__\1__asana_search_tasks to get all tasks
 2. **Analyze progress**: Calculate completion rates and identify blockers
 3. **Generate report**: Create formatted status update
-4. **Update Asana**: Use mcp**plugin_asana_asana**asana_create_comment to post report
+4. **Update Asana**: Use mcp__\1__asana_create_comment to post report
 
 ## Available Tools
 
@@ -164,7 +164,7 @@ Single tool call with validation:
 Steps:
 
 1. Validate user provided required fields
-2. Call mcp**plugin_api_server**create_item with validated data
+2. Call mcp__\1__create_item with validated data
 3. Check for errors
 4. Display confirmation
 ```
@@ -176,9 +176,9 @@ Chain multiple tool calls:
 ```markdown
 Steps:
 
-1. Search for existing items: mcp**plugin_api_server**search
-2. If not found, create new: mcp**plugin_api_server**create
-3. Add metadata: mcp**plugin_api_server**update_metadata
+1. Search for existing items: mcp__\1__search
+2. If not found, create new: mcp__\1__create
+3. Add metadata: mcp__\1__update_metadata
 4. Return final item ID
 ```
 
@@ -191,7 +191,7 @@ Steps:
 
 1. Get list of items to process
 2. For each item:
-   - Call mcp**plugin_api_server**update_item
+   - Call mcp__\1__update_item
    - Track success/failure
 3. Report results summary
 ```
@@ -203,7 +203,7 @@ Graceful error handling:
 ```markdown
 Steps:
 
-1. Try to call mcp**plugin_api_server**get_data
+1. Try to call mcp__\1__get_data
 2. If error (rate limit, network, etc.):
    - Wait and retry (max 3 attempts)
    - If still failing, inform user
@@ -328,7 +328,7 @@ Steps:
 ```markdown
 Steps:
 
-1. Call mcp**plugin_api_server**search with filters:
+1. Call mcp__\1__search with filters:
    - project_id: "123"
    - status: "active"
    - limit: 100
@@ -341,7 +341,7 @@ Steps:
 Steps:
 
 1. For each item ID:
-   - Call mcp**plugin_api_server**get_item
+   - Call mcp__\1__get_item
    - Process item
 ```
 
@@ -350,7 +350,7 @@ Steps:
 ```markdown
 Steps:
 
-1. Call expensive MCP operation: mcp**plugin_api_server**analyze
+1. Call expensive MCP operation: mcp__\1__analyze
 2. Store results in variable for reuse
 3. Use cached results for subsequent operations
 4. Only re-fetch if data changes
@@ -364,9 +364,9 @@ When tools don't depend on each other, call in parallel:
 Steps:
 
 1. Make parallel calls (Claude handles this automatically):
-   - mcp**plugin_api_server**get_project
-   - mcp**plugin_api_server**get_users
-   - mcp**plugin_api_server**get_tags
+   - mcp__\1__get_project
+   - mcp__\1__get_users
+   - mcp__\1__get_tags
 2. Wait for all to complete
 3. Combine results
 ```
@@ -381,7 +381,7 @@ Steps:
 Steps:
 
 1. Inform user: "Searching Asana tasks..."
-2. Call mcp**plugin_asana_asana**asana_search_tasks
+2. Call mcp__\1__asana_search_tasks
 3. Show progress: "Found 15 tasks, analyzing..."
 4. Present results
 ```
@@ -507,7 +507,7 @@ Use delete_item with item ID (ask for confirmation first)...
 ```markdown
 Steps:
 
-1. **Search**: mcp**plugin_api_server**search with filters
+1. **Search**: mcp__\1__search with filters
 2. **Filter**: Apply additional local filtering if needed
 3. **Transform**: Process each result
 4. **Present**: Format and display to user