# Plan safer Portfolio Buddy changes

Portfolio Buddy feature work can drift into risky refactors or mobile gaps. This skill guides Claude, Codex, and Claude Code to plan conservative, responsive changes.

## Install

```bash
npx skillstore add 5minfutures/planning-guidelines
```

## Metadata

- Status: approved
- Slug: 5minfutures-planning-guidelines
- Skillstore revision: r1
- Version status: missing
- Tree hash: 7e24821749a4782db2249fadd39c1c0350ad3b6092eab7c1d6da16203e270c30
- Author: 5MinFutures
- GitHub username: 5MinFutures
- License: MIT
- Repository: https://github.com/5MinFutures/futures-arena/tree/main/.claude/skills/planning-guidelines
- Ref: c1fdca50ff516318f65fed0d7f9e82797c5171dc
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/5minfutures-planning-guidelines
- Manifest: https://skillstore.pages.dev/api/skills/5minfutures-planning-guidelines/manifest

## Capabilities

- Defines preservation-first rules for feature work and refactoring decisions.
- Provides criteria for proposing high-value improvements with user approval.
- Requires responsive Tailwind planning for mobile and desktop layouts.
- Supplies a clarifying question format with options, pros, cons, and recommendations.
- Shows Portfolio Buddy examples for financial metrics, state defaults, and responsive buttons.

## Use Cases

- Plan a safe feature change: Use the guide to preserve working code, identify risks, and request approval before larger changes.
- Check responsive design choices: Apply the mobile and desktop checklist before adding UI controls, spacing, or visibility rules.
- Standardize requirement gathering: Use the clarifying question format to compare options and explain trade-offs before implementation starts.

## Prompt Templates

### Plan a small fix

```
Use the planning guidelines to plan this small Portfolio Buddy fix: [describe fix]. Preserve existing behavior and list mobile checks.
```

### Prepare clarification options

```
Use the clarifying question format for this request: [describe request]. Give recommended and alternate options with trade-offs.
```

### Evaluate an improvement exception

```
Assess whether this proposed improvement meets the low-risk, high-upside, low-complexity criteria: [describe improvement].
```

### Create a full implementation plan

```
Create a Portfolio Buddy implementation plan for [feature]. Include preservation strategy, responsive behavior, approval points, risks, and validation steps.
```

## Limitations

- Focused on Portfolio Buddy 2, so examples may need adaptation for other projects.
- Does not run tests, inspect repositories, or enforce code quality by itself.
- Does not replace product requirements, security review, or architecture approval.
- Assumes Tailwind and React-style patterns for many UI examples.

## Best Practices

- Start by identifying existing code that should be preserved.
- Check mobile and desktop behavior before calling a plan complete.
- Ask one clear clarification when requirements affect architecture or user experience.

## Anti Patterns

- Replacing working code because a different pattern looks cleaner.
- Adding libraries or abstractions before proving they reduce real complexity.
- Guessing product behavior when a short clarification would prevent rework.

## Security Audit

- Audited at: 2026-07-06T00:45:08.985\+00:00
- Summary: Manual review found the static findings are false positives caused by Markdown fences, inline code formatting, and ordinary planning prose. The skill is documentation-only and shows no executable shell commands, network access, credential handling, system reconnaissance, or prompt injection attempt.

## Stats

- Views: 218
- Downloads: 12
- Favorites: 0
- Popularity score: 0