microsoft · IEvangelist · May 27, 2026 · May 29, 2026
@@ -13,7 +13,7 @@ This skill provides guidelines for AI agents to systematically validate the aspi
 
 ### Core Principles
 
-1. **Use Playwright exclusively** to browse and interact with the documentation site
+1. **Use `playwright-cli` exclusively** to browse and interact with the documentation site
 2. **Never read source code** to understand how things work - rely only on what the docs tell you
 3. **Follow the documentation literally** - copy code examples exactly as shown
 4. **Evaluate teaching effectiveness** - can you learn from this documentation?
@@ -28,7 +28,7 @@ This skill provides guidelines for AI agents to systematically validate the aspi
 - Silently fill gaps with your built-in knowledge - flag them instead
 
 ✅ **DO:**
-- Use Playwright MCP tools to navigate the documentation site
+- Use `playwright-cli` commands to navigate the documentation site
 - Read documentation content as displayed in the browser
 - Copy code examples and run them in test projects
 - Evaluate if explanations make sense without prior knowledge
@@ -185,7 +185,7 @@ iex "& { $(irm https://aspire.dev/install.ps1) } -Quality 'staging'"
 
 ### Aspire App Model
 
-The aspire.dev workspace uses Aspire to orchestrate local services. The app model in `apphost.cs` defines the documentation site resources. Use `mcp_aspire_list_resources` to get the current resource states and URLs.
+The aspire.dev workspace uses Aspire to orchestrate local services. The app model in `apphost.cs` defines the documentation site resources. Use the Aspire CLI output or dashboard resource list to get the current resource states and URLs.
 
 ### Starting the Local Environment
 
@@ -200,15 +200,7 @@ cd /path/to/aspire.dev
 aspire run
 ```
 
-Use the Aspire MCP tools to get the content URL:
-
-```
-# Call the MCP tool
-mcp_aspire_list_resources
-
-# Look for the frontend resource endpoint_urls
-# Example output: http://frontend.dev.localhost:5000
-```
+Use the Aspire CLI output or dashboard resource list to get the content URL. Look for the `frontend` resource endpoint URL, for example `http://frontend.dev.localhost:5000`.
 
 **IMPORTANT**: Use the local frontend URL for all testing, not https://aspire.dev
 
@@ -299,27 +291,30 @@ The documentation site includes:
 
 ## Testing Workflow
 
-**All testing uses Playwright MCP tools to interact with the documentation site.**
+**All browser-based testing uses `playwright-cli` to interact with the documentation site.**
 
 ### Phase 0: Environment Preparation
 
 1. **Start Aspire**: Run `aspire run` from the repository root
-2. **Get frontend URL**: Use `mcp_aspire_list_resources` to find the `frontend` endpoint
+2. **Get frontend URL**: Use the Aspire CLI output or dashboard resource list to find the `frontend` endpoint
 3. **Note the URL**: The script outputs the local development URL
 
 ### Phase 1: Navigate and Read Documentation (Playwright)
 
-Use Playwright MCP tools to browse the documentation:
+Use `playwright-cli` to browse the documentation:
+
+```bash
+# Open the local docs site
+playwright-cli open http://frontend.dev.localhost:5000
 
-```
 # Take an accessibility snapshot to read page content
-mcp_playwright_browser_snapshot
+playwright-cli snapshot
 
-# Navigate to a page
-mcp_playwright_browser_click with element="Getting Started link"
+# Navigate to a page by clicking a ref from the snapshot
+playwright-cli click e42
 
 # Read page content
-mcp_playwright_browser_snapshot
+playwright-cli snapshot
 ```
 
 For each documentation page:
@@ -652,28 +647,29 @@ Keep the workspace directory but remove contents to avoid cluttering the reposit
 4. Document any place where you got stuck
 5. Verify final result matches what's promised
 
-## Using MCP Tools
+## Using CLI Tools
 
-### Aspire MCP Tools
+### Aspire CLI
 
 Use for checking resource status:
 
-```
-mcp_aspire_list_resources        # Get all resources and URLs
-mcp_aspire_list_console_logs     # Check resource logs
-mcp_aspire_list_structured_logs  # Check structured logs
+```bash
+aspire run                 # Start the app and print resource URLs
+aspire ps --include-hidden # List running resources and URLs when using aspire start
+aspire describe            # Inspect AppHost resources and endpoints
 ```
 
-### Playwright MCP Tools
+### `playwright-cli`
 
 Use for navigating and reading documentation:
 
-```
-mcp_playwright_browser_navigate   # Go to a URL
-mcp_playwright_browser_snapshot   # Read page content
-mcp_playwright_browser_click      # Click elements
-mcp_playwright_browser_type       # Type text
-mcp_playwright_browser_screenshot # Capture screenshot
+```bash
+playwright-cli open <url>          # Open a browser at a URL
+playwright-cli goto <url>          # Navigate to a URL
+playwright-cli snapshot            # Read page content
+playwright-cli click <ref>         # Click an element from the snapshot
+playwright-cli type "text"         # Type text into the active element
+playwright-cli screenshot          # Capture a screenshot
 ```
 
 ### Hex1b CLI Tools

@@ -832,6 +832,7 @@ Use the smallest set of checks that proves the change is correct:
 - For custom component usage changes, run the component render tests that cover the affected behavior.
 - For component prop surface changes, update and run the prop-contract coverage so editor completions and consumer typings stay intact.
 - For interactive behavior changes, run targeted Playwright coverage for the scenario you changed rather than relying on unrelated broad suites.
+- For browser-based local verification, use `playwright-cli` (`playwright-cli open <frontend-url>`, `playwright-cli snapshot`, `playwright-cli click <ref>`) instead of Playwright MCP tools.
 - For accessibility-sensitive changes, validate both the rendered page and any focused accessibility tests that exercise the affected interaction.
 
 ### Custom Component and Test Expectations
@@ -929,13 +930,14 @@ aspire run
 When testing code examples that add integration packages, use `aspire add <package-name>` rather than `dotnet add package`. The Aspire CLI automatically adds packages to the correct project.
 </Aside>
 
-Use the Aspire MCP tools to check the status of resources:
+Use the Aspire CLI output or dashboard resource list to find the `frontend` endpoint, then open it with `playwright-cli`:
 
-```
-mcp_aspire_list_resources
+```bash
+playwright-cli open <frontend-url>
+playwright-cli snapshot
 ```
 
-Navigate to the `frontend` resource endpoint to view the documentation site.
+Use snapshot refs with `playwright-cli click <ref>` for page interactions.
 
 ## Cross-Referencing
 

@@ -306,7 +306,7 @@ dotnet hex1b terminal attach <id>
 Generate this skill file for a repository so AI agents know how to use the CLI.
 
 ```bash
-# Write skill file to .github/skills/hex1b/SKILL.md
+# Write skill file to .agents/skills/hex1b/SKILL.md
 dotnet hex1b agent init
 
 # Specify a different repo root

@@ -274,7 +274,7 @@ dotnet hex1b terminal attach <id>
 Generate this skill file for a repository so AI agents know how to use the CLI.
 
 ```bash
-# Write skill file to .github/skills/hex1b/SKILL.md
+# Write skill file to .agents/skills/hex1b/SKILL.md
 dotnet hex1b agent init
 
 # Specify a different repo root

@@ -299,7 +299,7 @@ This agent depends on the following skills. Read the full skill instructions bef
 
 | Skill | File | When used |
 |-------|------|-----------|
-| doc-tester | `.github/skills/doc-tester/SKILL.md` | Phase 3 (content validation), Phase 6 (smoke test) |
-| hex1b | `.github/skills/hex1b/SKILL.md` | Phase 2 (preview server management), terminal capture |
-| playwright-cli | `.github/skills/playwright-cli/SKILL.md` | Phase 3d, Phase 6 (browser-based verification) |
-| update-integrations | `.github/skills/update-integrations/SKILL.md` | Phase 5 (integration docs sync) |
+| doc-tester | `.agents/skills/doc-tester/SKILL.md` | Phase 3 (content validation), Phase 6 (smoke test) |
+| hex1b | `.agents/skills/hex1b/SKILL.md` | Phase 2 (preview server management), terminal capture |
+| playwright-cli | `.agents/skills/playwright-cli/SKILL.md` | Phase 3d, Phase 6 (browser-based verification) |
+| update-integrations | `.agents/skills/update-integrations/SKILL.md` | Phase 5 (integration docs sync) |