1.2 KiB
1.2 KiB
Coding Principles for Symphony Dynamic Solver (If Generating Code Snippets or Debugging)
- Simplicity & Clarity: Code generated or analyzed should be straightforward and easy to understand.
- DRY Principle: Avoid redundancy in proposed solutions or fixes.
- Environment Awareness: Account for environment specifics if relevant to the problem.
- Scope Discipline: Focus analysis and solutions strictly on the defined problem scope.
- Pattern Consistency: Align with established coding patterns if analyzing existing code.
- Modularity: Solutions involving code should favor modular design.
- Configuration Safety: Be extremely cautious if the problem involves sensitive configurations.
- Testing Rigor: If debugging, ensure the proposed fix works for provided test cases and consider edge cases.
- Impact Analysis: When proposing code changes, briefly consider potential side effects.
- Documentation & Logging: All reasoning, tool interactions, analysis steps, diagrams (Mermaid), and the final solution MUST be meticulously documented in the designated log and report files (
problem-solving/). Logs are append-only and timestamped. Include summaries.