// Access local technical documentation before searching the internet. Use FIRST when researching any tech stack question.
Generate TypeScript API client from Swagger/Go comments. Use when updating API endpoints, adding new routes, or regenerating the frontend API client after backend changes.
Manage database migrations and Better Auth schema. Use when adding tables, modifying schema, running migrations, or resetting the database.
Generate full-stack features. Backend = hand-written bounded-context aggregates (DDD); frontend = FSD slices with HydrationBoundary. Use when creating new features, adding CRUD operations, or scaffolding new pages.
Create and manage authentication pages with server-side session handling. Use when adding login, register, or protected pages WITHOUT flicker/skeleton.
Server-Side + Client-Side Data Fetching with Orval + TanStack Query HydrationBoundary Pattern. ALWAYS use Orval - NEVER manual fetch()!
Feature-Sliced Design architecture for frontend. Use when creating new features, slices, or understanding the FSD layer structure.
| name | tech-docs |
| description | Access local technical documentation before searching the internet. Use FIRST when researching any tech stack question. |
| allowed-tools | Read, Glob, Grep, Bash |
ALWAYS search .docs/ FIRST before searching the internet!
.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
āāā 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
just search-docs "prefetchQuery" 5
just search-docs "HydrationBoundary" 3
just search-docs "authentication session" 5
# Output is LLM-optimized with relevance scores
When to use search-docs:
Question about a technology?
ā First: just search-docs "your question" to find relevant sections
ā Or: Read .docs/<tech>.md directly if you know the file
Docs not available?
ā Then search the internet
ā Save results in .docs/ for later
Docs outdated? ā Update with latest info
User: "How does HydrationBoundary work in TanStack Query?"
1. Run: just search-docs "HydrationBoundary" 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
When the user asks about tech stack topics, use this pattern:
# Step 1: Search for relevant docs
just search-docs "<user question keywords>" 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
just fetch-docs <documentation-url> <tech-name>
# Fetch docs from any URL
just fetch-docs https://tanstack.com/query/latest/docs
# With custom name
just fetch-docs https://nextjs.org/docs nextjs
just search-docs (semantic search, fast, targeted).docs/ files (local, fast, project-specific).claude/skills/ (project-specific patterns)