shuttles-radar-ast

name: Shuttles Radar AST description: Structural codebase analysis and logic mapping using AST-based tools and local LLM offloading.

Radar AST Skill

This skill enables precise, token-efficient codebase exploration by prioritizing structural understanding over raw file reading.

Core Tools

1. `get_dir_tree`

Use Case: Mapping the project layout or finding a specific module.
Protocol: Always set max_depth to 2 or 3 initially to avoid token bloat.

2. `get_file_skeleton`

Use Case: Understanding a file's API (classes, methods, arguments) without reading the implementation.
Mandate: RUTHLESSLY MANDATORY. Always call this before reading ANY file larger than 100 lines. Failure to do so burns excessive tokens.

3. `read_specific_lines`

Use Case: Focusing on a specific function implementation identified via get_file_skeleton.
Mandate: Use exact line ranges to stay within context limits.

4. The TOON Response Protocol

Mandatory for list-based analysis. When returning lists of files, search results, or structural mappings, use the TOON (Array of Arrays) format to minimize boilerplate keys.

5. `summarize_logic_local` [REQUIRES LOCAL GPU/Ollama]

Use Case: Explaining "How it works" for complex logic.
Protocol: Mandatory for any file > 300 lines or complex logic blocks. Use this to offload long-form analysis to the local RTX 3060 (Ollama), then synthesize the result for the user.

Strategic Workflow

graph TD
    Start[User Query] --> Tree[get_dir_tree]
    Tree --> Find[Find Relevant Files]
    Find --> Skeleton[get_file_skeleton]
    Skeleton --> Decide{Complex?}
    Decide -- Yes --> Summarize[summarize_logic_local]
    Decide -- No --> Read[read_specific_lines]
    Summarize --> Apply[Implement / Fix]
    Read --> Apply

Anti-Patterns

Full Reading: Using view_file on 500+ line files without a skeleton review.
Manual Summary: Trying to explain a 1000-line file manually instead of using _local tools.