メニュー
Access local technical documentation before searching the internet. Use FIRST when researching any tech stack question.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/atilladeniz/next-go-pg --skill tech-docsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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.
SOC 職業分類に基づく
SKILL.md を表示中
| 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)