version: "1.0.1" name: gwt-project-index description: Semantic search over project files and GitHub Issues using vector embeddings. Use first when you need to find an existing SPEC or related Issue before creating/updating one.

Project Structure Index

gwt maintains a vector search index of all project files and GitHub Issues using ChromaDB embeddings.

Issues search first for spec integration

When the user asks any of the following, use GitHub Issues search before manual gh issue list, title grep, or file search:

• "既存仕様を探して"
• "どの SPEC に統合するべきか"
• "関連 Issue / spec を探して"
• "Project Index の統合仕様を確認して"
• "bug / feature の過去設計を見たい"

For spec integration work, the first question is not "which file should I edit?" but "which existing gwt-spec Issue is the canonical destination?".

Minimum workflow:

1. Update the Issues index with index-issues
2. Run search-issues with 2-3 semantic queries derived from the request
3. Pick the canonical existing spec if found
4. Only fall back to creating a new spec when no suitable canonical spec exists

Suggested query patterns:

• subsystem + purpose
• project index issue search spec
• user-facing problem + architecture term
• chroma persisted db recovery project index
• workflow / discoverability requirement
• LLM should use gwt-project-index before spec creation

File search command

Run in terminal to find files related to a feature or concept:

~/.gwt/runtime/chroma-venv/bin/python3 ~/.gwt/runtime/chroma_index_runner.py \
  --action search \
  --db-path "$GWT_PROJECT_ROOT/.gwt/index" \
  --query "your search query" \
  --n-results 10

On Windows, use ~/.gwt/runtime/chroma-venv/Scripts/python.exe as the Python executable.

File search output format

JSON object with ranked results:

{"ok": true, "results": [
  {"path": "src/git/issue.rs", "description": "GitHub Issue commands", "distance": 0.12},
  {"path": "src/lib/components/IssuePanel.svelte", "description": "Issue list panel", "distance": 0.25}
]}

GitHub Issues search command

First, update the Issues index (fetches gwt-spec Issues via gh CLI):

~/.gwt/runtime/chroma-venv/bin/python3 ~/.gwt/runtime/chroma_index_runner.py \
  --action index-issues \
  --db-path "$GWT_PROJECT_ROOT/.gwt/index"

Then search Issues semantically:

~/.gwt/runtime/chroma-venv/bin/python3 ~/.gwt/runtime/chroma_index_runner.py \
  --action search-issues \
  --db-path "$GWT_PROJECT_ROOT/.gwt/index" \
  --query "your search query" \
  --n-results 10

Issues search output format

{"ok": true, "issueResults": [
  {"number": 42, "title": "Add vector search for Issues", "url": "https://github.com/...", "state": "open", "labels": ["gwt-spec"], "distance": 0.08}
]}

When to use

• Spec integration: find the canonical gwt-spec Issue before creating or updating a spec
• Task start: search for files and Issues related to the assigned feature
• Bug investigation: find files and spec Issues that might relate to the bug
• Feature addition: locate existing similar implementations and relevant specs
• Architecture understanding: discover how components are organized

Environment

• GWT_PROJECT_ROOT: absolute path to the project root (set by gwt at pane launch)

Notes

• File index is auto-generated when the project is opened in gwt
• Issue index must be updated manually (via GUI "Update Index" button or index-issues action)
• Both use semantic similarity (not just keyword matching)
• Lower distance values indicate higher relevance
• For spec work, prefer search-issues first and use file search second