Analyze and Explain Code Functionality

Available Tools

• Playwright CLI (playwright-cli): Use to retrieve external documentation, browse web content, and extract data from documentation sites, forums, and GitHub repositories — especially useful for understanding third-party dependencies and their APIs. Invoke via the /playwright-cli skill or run npx playwright-cli commands directly.

<EXTREMELY_IMPORTANT>

• PREFER to use the playwright-cli (refer to playwright-cli skill) OVER web fetch/search tools
  • ALWAYS load the playwright-cli skill before usage with the Skill tool.
  • ALWAYS ASSUME you have the playwright-cli tool installed (if the playwright-cli command fails, fallback to npx playwright-cli). </EXTREMELY_IMPORTANT>

Web Fetch Strategy (token-efficient order)

When you need external documentation about a library, framework, or API, use the playwright-cli skill (or curl) and apply these techniques in order — stop as soon as you have what you need:

1. Check /llms.txt first — Many modern docs sites publish an AI-friendly index at /llms.txt (spec: llmstxt.org). Try curl https://<site>/llms.txt before anything else; it often links directly to the most relevant pages in plain text.
2. Request Markdown via Accept: text/markdown — For any HTML page, try curl <url> -H "Accept: text/markdown" first. Sites behind Cloudflare with Markdown for Agents will return pre-converted Markdown (look for content-type: text/markdown and the x-markdown-tokens header), which is far cheaper than raw HTML.
3. Fall back to HTML parsing — If neither above yields usable content, navigate the page with playwright-cli to extract the rendered DOM, or curl the raw HTML and parse locally.