Menu
Use TGlider for TypeScript and JavaScript semantic navigation, references, diagnostics, dependency topology, impact analysis, and refactoring.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use GliderTrace for .NET runtime evidence, test runs, failure summaries, exceptions, counters, traces, dumps, and artifact indexing.
Use GliderMCP for C#/.NET navigation, diagnostics, references, call graphs, impact analysis, and safe refactoring.
Use Scout for repo-wide code search in any language - ranked fuzzy discovery, exhaustive strict literal, regex, and word search, plus structural patterns, symbol outlines, and semantic queries.
| name | tglider-typescript |
| description | Use TGlider for TypeScript and JavaScript semantic navigation, references, diagnostics, dependency topology, impact analysis, and refactoring. |
Use TGlider when working in a TypeScript or JavaScript repository and the task needs semantic facts rather than plain text search.
Start by loading the relevant workspace when needed. Prefer semantic symbol, reference, export, diagnostic, hierarchy, call graph, impact, and dependency tools before reading source text. Use source reads only for bounded context after the semantic tools identify the relevant files or symbols.
For edits, gather evidence first with tools for references, callers, outgoing calls, diagnostics, dependency topology, and change impact. Prefer preview-first refactoring tools where available, and refresh diagnostics after meaningful edits.
For non-code assets, generated output, literal config files, and repo-wide text search, prefer Scout's find when Scout is installed. TGlider's own search_text searches with Scout and requires it - without a scout binary on PATH it returns a scout_not_installed hint, so install Scout globally to use that tool at all. Use shell text search when Scout is absent, or when neither can answer the question.
