planning-guidelineslisted

# Planning Guidelines for Portfolio Buddy 2 ## Core Principles When planning and implementing features for Portfolio Buddy 2, always follow these fundamental principles: 1. **Preserve Existing Code** - Default to extending rather than replacing 2. **Optimize for Mobile & Desktop** - Every feature must work well on both 3. **Ask Clarifying Questions** - Gather complete context before execution 4. **Integrate Seamlessly** - New code should feel native to the existing codebase --- ## Code Preservation Strategy ### Default Behavior: Always Preserve **Rule:** Preserve existing code unless explicitly instructed to refactor or rewrite. When implementing new features or fixes: - ✅ Extend existing components - ✅ Add new functions alongside existing ones - ✅ Preserve existing patterns and conventions - ✅ Maintain backward compatibility - ❌ Don't refactor working code "just because" - ❌ Don't introduce new patterns without justification ### Exception: Massively Better Options You MAY propose improvements to existing code **ONLY** when ALL conditions are met: 1. **Very Low Risk** - Change is isolated, well-understood, easily reversible 2. **Massive Upside** - Significant benefit (correctness, performance, maintainability) 3. **No Unnecessary Complexity** - Solution is simpler or equal complexity 4. **Clear Justification** - Can explain why exception applies **When exception applies, you MUST:** - Explain the problem with current implementation - Show the proposed improvement