Tooling Rules

<TOOLING_REQUIREMENTS>
  <NOTE> Make sure you follow the rules when performing tool calls - you must only use valid tools for editing and finding / replacing within files. Don't make tools up. </NOTE>
  <MANDATORY_TOOL_USAGE>
    <NOTE> Below is a high level overview some of the useful tools you have available, you may have more at your disposal and should make effect use of tools to help completing tasks </NOTE>
    <TOOL name="fetch_url">
      <WHEN> Needing to fetch content from a URL </WHEN>
    </TOOL>
    <TOOL name="[ resolve_library_id , get_library_docs ]">
      <WHEN> Researching or implementing complex packages / libraries </WHEN>
      <PURPOSE> Use these tools to access up to date documentation and implementation patterns for packages. Especially useful when implementing complex or recently updated packages or frameworks </PURPOSE>
    </TOOL>
    <TOOL name="search_packages">
      <WHEN> Adding or updating packages / libraries </WHEN>
      <PURPOSE> To get the latest stable versions to use </PURPOSE>
    </TOOL>
    <TOOL name="internet_search">
      <WHEN> Searching for internet for information or solutions not found in existing tools </WHEN>
      <PURPOSE> Perform web searches to find relevant information, documentation, or solutions </PURPOSE>
    </TOOL>
    <TOOL name="think">
      <WHEN> Encountering complex problems or requiring intermediate reasoning </WHEN>
      <PURPOSE> Document thought process and solve complex issues </PURPOSE>
      <ESCALATION> Use 'think harder' if standard thinking insufficient, use 'ultra think' if you continue to resolve an issue </ESCALATION>
    </TOOL>
  </MANDATORY_TOOL_USAGE>
  <BEST_PRACTICES>
    <PRACTICE> Always consider available MCP tools before manual or guessed approaches </PRACTICE>
    <PRACTICE> Tool use is preferred for efficiency and accuracy </PRACTICE>
  </BEST_PRACTICES>
</TOOLING_REQUIREMENTS>