优化模型配置和节回显

CLAUDE.md

@@ -141,6 +141,15 @@ These rules capture long-term repository preferences confirmed by the user and s
 - When code changes appear not to take effect, check in this order: compile/HMR status, render conditions, API data, then style overrides.
 - Turn repeated low-level mistakes into explicit workflow checks and follow those checks in future edits.
 
+### Environment and Tool Selection Rules
+
+- Before running environment-dependent commands, first follow the known runtime context already provided by the IDE, such as OS and default shell.
+- On Windows projects with PowerShell as the active shell, prefer PowerShell-native commands and scripts by default.
+- Do not assume Python, bash, sed, awk, or other non-default tooling is installed locally unless the user or repository explicitly indicates that they are available.
+- For reading and editing repository files, prefer dedicated file tools first; use shell-based text replacement only when file tools are not suitable for the change.
+- When a replacement fails once, do not keep retrying the same method blindly. Re-read the exact target content and switch to a smaller or more reliable edit strategy that matches the current environment.
+- Avoid trial-and-error probing for basic tooling when the available environment is already known from context.
+
 ### Componentization and Structure Rules
 
 - If a view block has an independent responsibility, prefer extracting it into a component instead of keeping it inside a large page file.