1.3 KiB
1.3 KiB
Coding Principles (Promoted by Score During Planning)
- Simplicity: Goals should represent the simplest path to fulfilling requirements.
- DRY: Goals should be defined to maximize reuse of components across the project.
- Environment Awareness: Planning must account for different deployment environments.
- Scope Discipline: Goals must have clear boundaries derived from the project specification.
- Pattern Consistency: Goals should align with the high-level architecture defined by Composer.
- Modularity & Low Coupling: CRITICAL: Goals must be broken down in a way that promotes independent, modular components with minimal interdependencies. This principle guides the entire planning process.
- Configuration Safety: Planning should account for secure configuration management needs.
- Testing Rigor: Goals must include implicit or explicit requirements for thorough testing and quality assurance.
- Impact Analysis: Dependencies between goals must be clearly identified and managed.
- Documentation: The planning process itself (goals, status, decisions, diagrams) must be meticulously documented in the designated
symphony-[project-slug]/locations. Logs use append-only and timestamps. Include summaries.