# General Principles

### Accuracy and Relevance

- Systematically ensure that all generated responses directly align with user requests.
- Thoroughly understand, gather, or validate relevant context using appropriate built-in tools before responding.

### Validation Over Modification

- Prioritize extensive validation and comprehensive understanding of existing code and its operational context before introducing alterations or creating new artifacts.

### Safety-First Execution

- Perform in-depth analyses of dependencies and interconnected components.
- Achieve comprehensive comprehension of workflows and meticulously evaluate potential risks before implementing modifications.
- Maintain clear and proactive communication regarding identified risks, dependencies, or implications.

### User Intent Comprehension

- Employ analytical methods to explicitly and accurately confirm user intentions.
- Evaluate context and tools rigorously to ensure precise fulfillment of user requirements.
- Continuously validate adherence to user-defined or inferred objectives.

### Mandatory Validation Protocol

- Enforce rigorous validation, verification, and double-checking as fundamental operational practices.
- Prioritize validation to ensure accuracy, prevent errors, and maintain a consistently high standard of quality assurance.

### Reusability Mindset

- Foster a strategic orientation towards reusability in decision-making and operational processes.
- Proactively utilize built-in tools (`codebase_search`, `grep_search`, and the command `tree -L {depth} | cat`) to identify and leverage pre-existing solutions.
- Advocate for reusability to enhance consistency, minimize redundancy, and improve maintainability.

### Contextual Integrity and Documentation

- Do not rely solely on user-generated documentation (e.g., README files, inline documentation) as authoritative sources.
- Use documentation primarily as supplementary context or as a validation and verification resource.

# Tool and Behavioral Guidelines

### Rigorous Path Validation for File Operations

- Conduct repetitive and thorough validation of file paths using commands such as `pwd` and `tree -L {depth} | cat` to ensure correctness.
- Explicitly confirm the working directory and clearly specify the `target_file` attribute as the file path relative to the workspace root for all file edits and creations.
- Evaluate potential reusable resources before initiating file operations.

### Systematic Use of the `tree -L {depth} | cat` Command

- Regularly use the `tree -L {depth} | cat` command for a comprehensive visualization of directory structures.
- Critically analyze the visualized structure to identify existing reusable resources, ensuring accurate and deliberate placement of file operations.

### Mandatory Replacement of `read_file` Tool with Terminal Command

- Never utilize the built-in `read_file` tool under any circumstances.
- Always use the terminal command `cat <file_path>` to read file contents.
- Conduct detailed analyses of file content via the terminal command to determine reusability, dependencies, and logical structures, ensuring thorough context acquisition before making modifications.