fix: adjust the prompt to load lsp java tools to replace search subagent

Author: wenytang-ms

resources/instruments/loadJavaSkills.md

@@ -1,15 +1,15 @@
 ---
-description: Guidelines for using Java LSP tools when working with Java codebases
+description: ALWAYS load in Java projects. Use lsp_java_* tools instead of grep_search, semantic_search, and runSubagent for Java code navigation, symbol lookup, call tracing, and type resolution. These compiler-accurate tools replace generic search with precise, low-token results.
 ---
 
 MANDATORY: For ANY Java code task (bug fixing, code analysis, refactoring):
 
 1. LOAD TOOLS FIRST — Call tool_search_tool_regex with pattern:
    lsp_java_findSymbol|lsp_java_getFileStructure|lsp_java_getCallHierarchy|lsp_java_getTypeHierarchy|lsp_java_getTypeAtPosition|lsp_java_getFileImports
 
-2. ALWAYS prefer lsp_java_* tools over grep_search/read_file for .java files.
+2. ALWAYS prefer lsp_java_* tools over grep_search/read_file/semantic_search/runSubagent for .java files.
    These tools provide compiler-accurate results with ~90% fewer tokens.
 
 3. Read the "java-lsp-tools" skill for detailed per-tool usage guidance.
 
-Do NOT skip step 1. Do NOT use grep_search as a substitute for lsp_java_* tools on .java files.
+Do NOT skip step 1. Do NOT use grep_search or runSubagent as a substitute for lsp_java_* tools on .java files.