Agent skill · software engineering · aiskillstore
planning-guidelines
Core planning principles for Portfolio Buddy 2 development. Use when: planning any feature implementation, modification, or refactoring. Ensures code preservation, mobile/desktop optimization, and thorough requirement gathering.
Why this skill is useful
Provides specific guidelines for feature planning and implementation that ensure code quality and optimization for mobile/desktop, which the AI might not generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 Demonstrate why it meets all three criteria Get user approval before implementing Real Example: Annual Growth Rate Fix Situation: During implementation of Trading Days update, discovered Annual Growth Rate calculation was mathematically incorrect. Current (incorrect) code: Why exception applied: 1. Very Low Risk ✅ Isolated calculation (one line) Easy to understand (calendar days vs trading days) Easily reversible if wrong 2. Massive Upside ✅ Fixes incorrect financial metric (accuracy critical) Returns were inflated by ~2.4x Aligns with financial industry standards 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/planning-guidelines