tech-docs

Search local .docs/ documentation via make search-docs before internet queries.

2|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/atilladeniz/next-go-pg --skill tech-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-docs
Source: https://github.com/atilladeniz/next-go-pg/tree/main/.claude/skills/tech-docs
Command: npx skills add https://github.com/atilladeniz/next-go-pg --skill tech-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill drastically reduces the time spent searching for answers to technical questions by prioritizing local, project-specific documentation. It provides a semantic search tool for the .docs/ directory, ensuring you get relevant, context-aware information quickly, rather than sifting through generic internet results.

Core Features & Use Cases

  • Semantic Search: Use make search-docs to intelligently query local documentation for specific topics and code examples.
  • Comprehensive Local Knowledge Base: Access detailed documentation on Next.js, TanStack Query, Better Auth, GORM, Tailwind CSS, and more.
  • Documentation Workflow: Guides on how to effectively search, fetch new, and update existing documentation.
  • Use Case: Before searching Google for "How to implement prefetchQuery in Next.js," use make search-docs q="prefetchQuery TanStack Query" to quickly find relevant project-specific documentation and code snippets, saving valuable development time.

Quick Start

Search the local documentation for information on "Tailwind CSS 4" and list the top 3 results with their relevance scores.

Frequently Asked Questions about tech-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search local project documentation instead of using Google?

Use `make search-docs q="your-topic"` to perform semantic search across your `.docs/` directory. This queries local project-specific documentation on frameworks like Next.js, TanStack Query, and Tailwind CSS before falling back to internet searches, returning relevant results with relevance scores.

What's the best way to find API usage examples in my project docs?

Run `make search-docs` with specific keywords—for example, `q="prefetchQuery TanStack Query"`—to retrieve code snippets and implementation patterns from local `.docs/<tech>.md` files. Results rank by relevance, surfacing the most applicable examples first.

Can I access documentation on Next.js, TanStack Query, and other frameworks locally?

Yes. The `.docs/` repository contains comprehensive documentation on Next.js, TanStack Query, Better Auth, GORM, Tailwind CSS, and other technologies in your stack. Semantic search indexes all files, enabling rapid context-aware lookups without internet dependency.

When should I search local docs instead of searching the web?

Prioritize local docs for technology stack inquiries, API usage questions, and code-pattern lookups. Local search returns project-specific context faster than generic web results. Use web search only when local documentation is unavailable or doesn't cover your query.

How do I update or add new documentation to my local knowledge base?

Documentation workflow guides show how to fetch, update, and maintain `.docs/<tech>.md` files. Adding or updating local docs ensures `make search-docs` indexes current information and improves future query results with project-specific patterns.

Does semantic search work for all programming questions?

Semantic search works best for technology stack inquiries, API usage, and code-pattern questions where project documentation exists. It gracefully falls back to internet sources when local docs don't cover a topic, ensuring you still get answers.