architecture-reference

Document component hierarchy, core hooks, utilities, and data flow for the Portfolio Buddy 2 codebase.

1|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/5MinFutures/futures-arena --skill architecture-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-reference
Source: https://github.com/5MinFutures/futures-arena/tree/main/.claude/skills/architecture-reference
Command: npx skills add https://github.com/5MinFutures/futures-arena --skill architecture-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This architecture reference provides a centralized overview of the Portfolio Buddy 2 codebase to accelerate onboarding, design decisions, and maintenance by clarifying structure and patterns.

Core Features & Use Cases

  • Component Hierarchy: Visual map of top-level components and their relationships to data flows.
  • Core Hooks & Utilities: Documentation of commonly used hooks and utility functions to guide development and refactors.
  • Data Flow & Integration: Reference of how data travels through the app, from uploads to analytics visualizations.
  • Use Case: When adding a new feature, consult this reference to identify impacted modules and hooks.

Quick Start

Review the architecture-reference to understand the project skeleton and recommended integration points for new features.

Frequently Asked Questions about architecture-reference

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

FAQPage Schema
How do I get a quick architecture reference for codebase onboarding?

A quick architecture reference accelerates onboarding by providing a centralized overview of the codebase structure, core hooks, and data flow to guide developers through rapid integration and maintenance.

What is the best way to understand component hierarchy and data flow before adding a new feature?

Understanding component hierarchy and data flow is best achieved by consulting an architecture reference that maps top-level components and traces data from uploads to analytics visualizations to identify impacted modules.

How does documenting core hooks and utility functions support feature planning?

Documenting core hooks and utility functions supports feature planning by clarifying codebase patterns and structure, enabling developers to identify integration points and execute consistent implementations.

Can I use an architecture reference to identify impacted modules for codebase refactoring?

Yes, you can use an architecture reference to identify impacted modules during refactoring by reviewing the documented component hierarchy and commonly used utility functions to guide maintenance.

Does this architecture reference cover data flow from uploads to analytics visualizations?

Yes, this architecture reference covers data flow from uploads to analytics visualizations, detailing how data travels through the app to support cross-team collaboration and rapid integration.