docs-fetcher

name	docs-fetcher
description	Fetch, cache, and use local documentation snapshots under references/ (via uvx devdocs-crawler). Use when implementing features and you need authoritative API/concept docs without relying on web browsing (e.g., “Implement X using React”).

Docs Fetcher

Overview

Keep local doc snapshots in this skill’s references/ directory and use them as the primary source of truth when implementing.

Core behavior for tasks like “Implement X using React”:

1. Check whether the relevant docs already exist under references/.
2. If missing, fetch them with uvx devdocs-crawler.
3. Search locally (ripgrep / workspace search) and implement using what the docs say.

Local Docs Inventory (Keep This Updated)

Whenever you fetch a new documentation site into references/:

• supabase.com/
• react.dev/
• tailwindcss.com/
• ui.shadcn.com/

Workflow

0) Only fetch docs when needed

Do not crawl documentation proactively.

Only crawl when the user explicitly asks about a particular framework/tool/site (e.g., React, Next.js, Tailwind, Prisma) AND the docs are not already present locally.

1) Check if docs already exist in references/

If the user asks: "Implement X using React", first look for a folder like:

• references/react.dev/

If it exists, do not fetch again—just search and use it: see Step 3 below.

2) Fetch docs (if missing)

Fetch React Learn docs into this skill's references folder:

uvx devdocs-crawler https://react.dev/learn -o /home/rubens/.copilot/skills/docs-fetcher/references

If Playwright fails (often on first run), install browser deps:

uvx --with devdocs-crawler playwright install

After fetching:

• Confirm a folder like references/react.dev/ exists
• Update Local Docs Inventory above (add the new site; keep entry points)

3) Search docs in references/

Prefer local search over scrolling.

Option A: Terminal search (fast)

From the skill directory:

rg -n "useEffect" references/react.dev
rg -n "controlled" references/react.dev
rg -n "useMemo" references/react.dev

Search tips:

• API names (useEffect, useReducer, useSyncExternalStore)
• Concept keywords (controlled, context, effects, suspense)

Option B: VS Code search

If your environment can search outside the project root, scope search to:

• /home/rubens/.copilot/skills/docs-fetcher/references/**

Otherwise, use terminal rg.

4) Use docs while implementing

• Prefer patterns recommended by the docs over guesswork.
• If the repo’s existing conventions differ, call it out and align with project style.
• When you rely on a specific guidance, point to the local doc path in your explanation (e.g., references/react.dev/learn/...).

Resources

references/

Local documentation snapshots and reference material intended to be searched and loaded as needed.