skills.rest
5MinFutures
5MinFuturesCOMMUNITY
Explore all skills by this author →
GitHub

planning-guidelines

Provide structured planning guidelines for Portfolio Buddy 2 development.

1|Updated Nov 14, 2025
Search Tags:#planning#architecture#refactoring#guidelines#clarifying-questions#Portfolio Buddy 2#mobile-desktop
One-click install
npx skills add https://github.com/5MinFutures/futures-arena --skill planning-guidelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-guidelines
Source: https://github.com/5MinFutures/futures-arena/tree/main/.claude/skills/planning-guidelines
Command: npx skills add https://github.com/5MinFutures/futures-arena --skill planning-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning principles and governance for Portfolio Buddy 2 development, ensuring stable, maintainable growth across features, refactors, and enhancements.

Core Features & Use Cases

  • Code Preservation: Default to extending existing code rather than rewriting.
  • Mobile & Desktop Optimization: Ensure new features work smoothly on all screen sizes.
  • Clarifying Questions Framework: Prompt-based questions to gather complete context before work.
  • Seamless Integration: New work should feel native to the codebase and patterns.

Quick Start

Use this Skill at the outset of any feature effort: load planning-guidelines, then apply the planning-framework, review architecture-reference, follow coding-standards, and update the migration-tracker with your changes.

Frequently Asked Questions about planning-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the planning guidelines for refactoring an existing codebase?▼

Planning guidelines for refactoring prioritize code preservation by defaulting to extend existing code rather than rewriting, ensuring stable and maintainable modifications. This approach integrates with architecture references to maintain codebase stability.

How do I ensure new features work smoothly on both mobile and desktop screens?▼

To ensure features work smoothly on mobile and desktop, apply planning guidelines that enforce responsive optimization requirements during the initial planning phase. This guarantees screen size compatibility before development begins.

What is the best way to gather complete requirements before starting a feature refactor?▼

The best way to gather requirements is using a clarifying-questions framework that prompts for complete context before work begins. This ensures all necessary information is collected to prevent scope creep during development.

Do I need to follow coding standards when planning new architecture changes?▼

Yes, you need to follow coding standards when planning architecture changes so new work integrates seamlessly and feels native to the existing codebase. Adherence ensures smooth integration and maintainable growth.

When should I not use a code preservation approach during development planning?▼

You should not use code preservation when the existing architecture fundamentally lacks the capacity to support required new features. In such cases, planning guidelines shift to evaluate necessary modifications while maintaining overall stability.

Related Skills

Explore More Software Engineering Skills→
BingChanCNBingChanCN

check-backend

Check code compliance against backend development guidelines.

Community
Intermediate
rachel353rachel353

change-doc

Reconcile FE design documents and tasks.json from change-analyzer outputs and feedback.

Community
Advanced
oddshipoddship
3

meta-extension-creator

Generate TypeScript Pi extension codebases with event handling and command registration.

Official
Intermediate
zhouboyu-xrealzhouboyu-xreal

requesting-code-review

Automate code review with security scans, quality checks, and linting.

Community
Advanced