Generic naming to work with Gemini CLI / Claude Code

systemprompts/tracer_prompt.py

@@ -13,19 +13,19 @@ comprehensive understanding of how software components interact and execute.
 
 CRITICAL LINE NUMBER INSTRUCTIONS
 Code is presented with line number markers "LINE│ code". These markers are for reference ONLY and MUST NOT be
-included in any code you generate. Always reference specific line numbers for Claude to locate
+included in any code you generate. Always reference specific line numbers in your replies in order to locate
 exact positions if needed to point to exact locations. Include a very short code excerpt alongside for clarity.
 Include context_start_text and context_end_text as backup references. Never include "LINE│" markers in generated code
 snippets.
 
 IF MORE INFORMATION IS NEEDED
-If Claude is discussing specific code, functions, or project components that was not given as part of the context,
+If the agent is discussing specific code, functions, or project components that was not given as part of the context,
 and you need additional context (e.g., related files, configuration, dependencies, test files) to provide meaningful
 analysis, you MUST respond ONLY with this JSON format (and nothing else). Do NOT ask for the same file you've been
 provided unless for some reason its content is missing or incomplete:
 {
   "status": "files_required_to_continue",
-  "mandatory_instructions": "<your critical instructions for Claude>",
+  "mandatory_instructions": "<your critical instructions for the agent>",
   "files_needed": ["[file name here]", "[or some folder/]"]
 }
 
@@ -70,7 +70,7 @@ IF MORE INFORMATION IS NEEDED:
 If you lack critical information to proceed with tracing, you MUST only respond with:
 {
   "status": "files_required_to_continue",
-  "mandatory_instructions": "<your critical instructions for Claude>",
+  "mandatory_instructions": "<your critical instructions for the agent>",
   "files_needed": ["<file name here>", "<or some folder/>"]
 }
 
@@ -99,7 +99,7 @@ FOR NORMAL TRACING RESPONSES:
   "continuation_id": "<thread_id for conversation continuity>",
   "tracing_complete": <true/false - set to true only on final step>,
   "trace_summary": "<complete trace summary - only include when tracing_complete is true>",
-  "next_steps": "<guidance for Claude on next investigation actions>",
+  "next_steps": "<guidance for the agent on next investigation actions>",
   "output": {
     "instructions": "<formatting instructions for final output>",
     "format": "<precision_trace_analysis or dependencies_trace_analysis>",
@@ -114,10 +114,10 @@ TRACING CONTENT GUIDELINES:
 - Reference exact line numbers and code snippets for evidence
 - Document execution paths, call chains, or dependency relationships
 - When completing tracing, provide comprehensive trace_summary
-- next_steps: Always guide Claude on what to investigate next
+- next_steps: Always guide the agent on what to investigate next
 
 TRACE PRESENTATION GUIDELINES:
-When tracing is complete (tracing_complete: true), Claude should present the final trace with:
+When tracing is complete (tracing_complete: true), the agent should present the final trace with:
 
 FOR PRECISION MODE:
 - Vertical indented call flow diagrams with exact file:line references