# Guide Portfolio Buddy Development

Portfolio Buddy 2 development needs consistent project memory across React, TypeScript, and trading analytics work. This skill gives Claude, Codex, and Claude Code the project context needed for safer implementation decisions.

## Install

```bash
npx skillstore add 5minfutures/portfolio-context
```

## Metadata

- Status: approved
- Slug: 5minfutures-portfolio-context
- Skillstore revision: r1
- Version status: missing
- Tree hash: 032bea686d81653ff87eddc77107af84d71430f81e2339dfce513ae94e60f3a5
- Author: 5MinFutures
- GitHub username: 5MinFutures
- License: MIT
- Repository: https://github.com/5MinFutures/futures-arena/tree/main/.claude/skills/portfolio-context
- Ref: 820ccb93d2e2fe828678ed05433bafd1054e5000
- 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
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/5minfutures-portfolio-context
- Manifest: https://skillstore.pages.dev/api/skills/5minfutures-portfolio-context/manifest

## Capabilities

- Summarizes the Portfolio Buddy 2 tech stack and supported libraries.
- Identifies known technical debt in React components and TypeScript types.
- Documents trading analytics features such as Sortino ratio and date filtering.
- Explains architecture rules for hooks, utilities, state, and component size.
- Maps important source areas for portfolio, metrics, upload, and correlation features.
- Provides migration context for remaining work from the older application.

## Use Cases

- Plan React Refactors: Use the documented component limits and known oversized files to scope refactoring work before editing.
- Maintain Trading Metrics: Use the project notes to preserve Sortino, Sharpe, correlation, and contract multiplier behavior during changes.
- Review Migration Progress: Use the migration context and feature list to align new tasks with the remaining Portfolio Buddy 2 roadmap.

## Prompt Templates

### Understand the Project

```
Explain the Portfolio Buddy 2 stack, main features, known issues, and architecture constraints from this skill.
```

### Scope a Small Fix

```
Using the Portfolio Buddy 2 context, identify the likely files and constraints for fixing this issue: [describe issue].
```

### Refactor a Feature Area

```
Plan a refactor for [component or hook] while respecting the 200-line component limit, strict TypeScript, and existing hook patterns.
```

### Evaluate Analytics Changes

```
Review this proposed change to portfolio metrics for correctness, affected files, and risks to Sortino, correlation, date filtering, and contract multipliers.
```

## Limitations

- It contains static project notes and does not inspect the current repository state.
- It does not run tests, linting, builds, or database checks by itself.
- It is specific to Portfolio Buddy 2 and is not a general portfolio analytics framework.
- Some line counts and known issues may become stale as the codebase changes.

## Best Practices

- Pair this context with a fresh repository inspection before editing files.
- Use the documented architecture rules to keep hooks, utilities, and components separated.
- Recheck financial metric formulas and chart behavior after analytics changes.

## Anti Patterns

- Do not treat the stored line counts as authoritative after code changes.
- Do not add new state management libraries without a project decision.
- Do not move portfolio-level calculations without checking existing feature context.

## Security Audit

- Audited at: 2026-07-20T17:17:50.497\+00:00
- Summary: All six static findings are false positives caused by Markdown inline and fenced code formatting. The skill contains project documentation only and no executable commands, network instructions, credential handling, or prompt-injection content.

## Stats

- Views: 200
- Downloads: 18
- Favorites: 0
- Popularity score: 0