tech-docs

Access local technical documentation before searching the internet. Use FIRST when researching any tech stack question.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️2downloads

When & Why to Use This Skill

The Technical Documentation Skill is a specialized developer utility designed to prioritize local project context over generic web results. It enables Claude to perform semantic searches and direct file lookups within a local `.docs/` directory, ensuring that technical answers are grounded in the specific library versions and architectural patterns used in your codebase. This approach minimizes hallucinations, improves response accuracy for niche tech stacks, and streamlines the developer workflow by keeping documentation management within the agent's immediate reach.

Use Cases

  • Project Onboarding: Quickly understand a new codebase's architecture and tech stack by searching the local .docs/ directory for READMEs and implementation guides.
  • Precise API Reference: Retrieve specific code patterns and API usage examples for libraries like TanStack Query or GORM without leaving the terminal or IDE.
  • Documentation Synchronization: Use the fetch-docs tool to pull the latest documentation from official websites and save it locally to maintain an up-to-date, project-specific knowledge base.
  • Context-Grounded Debugging: Resolve errors by cross-referencing local logging standards and configuration docs before resorting to broad internet searches.
nametech-docs
descriptionAccess local technical documentation before searching the internet. Use FIRST when researching any tech stack question.
allowed-toolsRead, Glob, Grep, Bash

Technical Documentation Skill

ALWAYS search .docs/ FIRST before searching the internet!

Documentation Directory

.docs/
├── README.md           # Overview
├── nextjs.md           # Next.js 16 App Router
├── tanstack-query.md   # TanStack Query / React Query
├── better-auth.md      # Better Auth
├── gorm.md             # GORM ORM
├── gorilla-mux.md      # Gorilla Mux Router
├── goca.md             # Goca CLI
├── orval.md            # Orval API Client Generator
├── shadcn.md           # shadcn/ui Components
├── tailwind.md         # Tailwind CSS 4
├── kamal-deploy.md     # Kamal Deployment
└── logging.md          # Logging (zerolog + Pino)

Use the semantic search tool to find relevant documentation:

# Search for specific topics
make search-docs q="prefetchQuery" n=5
make search-docs q="HydrationBoundary" n=3
make search-docs q="authentication session" n=5

# Output is LLM-optimized with relevance scores

When to use search-docs:

  • Looking for specific patterns or APIs
  • Finding code examples for a concept
  • Researching how to implement something
  • The docs are large and you need targeted results

Workflow

  1. Question about a technology? → First: make search-docs q="your question" to find relevant sections → Or: Read .docs/<tech>.md directly if you know the file

  2. Docs not available? → Then search the internet → Save results in .docs/ for later

  3. Docs outdated? → Update with latest info

Example Usage

User: "How does HydrationBoundary work in TanStack Query?"

1. Run: make search-docs q="HydrationBoundary" n=5
2. Review the top results with relevance scores
3. If needed, read full file: .docs/tanstack-query.md
4. If not found/incomplete:
   - WebFetch from TanStack Query docs
   - Save relevant info to .docs/tanstack-query.md
5. Answer the question

Tool Calling Pattern

When the user asks about tech stack topics, use this pattern:

# Step 1: Search for relevant docs
make search-docs q="<user question keywords>" n=5

# Step 2: If results found, read the specific section
# The search output shows file and section info

# Step 3: If no results, fetch new docs
make fetch-docs url=<documentation-url> name=<tech-name>

Fetching New Documentation

# Fetch docs from any URL
make fetch-docs url=https://tanstack.com/query/latest/docs

# With custom name
make fetch-docs url=https://nextjs.org/docs name=nextjs

Priority

  1. make search-docs (semantic search, fast, targeted)
  2. .docs/ files (local, fast, project-specific)
  3. .claude/skills/ (project-specific patterns)
  4. Internet (only if local not available)