Build a Korean-Language Financial Terminal for U.S. Stock Investors

Format

Markdown

Inputs

AttachedUIReferenceImage (image) · Required

Outputs

RunnableFinancialTerminalProject (code, document, json) SetupAndDeploymentDocumentation (document, markdown)

# Project: Korean-Language Financial Terminal for U.S. Stock Investors

Build a complete, runnable financial terminal for Korean-speaking investors focused on U.S. stocks. Also support Korean stocks and DART filings. Use the attached image as a visual reference for the high-density terminal interface.

## 1. Market data
- Provide real-time or near-real-time data where available for U.S. stocks, ETFs, indexes, interest rates, commodities, foreign exchange, and Korean stocks.
- Document which data-provider APIs and API keys are required.
- Never fill missing data with fabricated numbers. Clearly label states such as “No data,” “API required,” and “Delayed data.”
- Allow visitors who are not logged in to view general market information using real data.

## 2. News and translation
- Show U.S. stock news in its original language alongside a Korean translation.
- Provide sentiment, related ticker symbols, importance, and a summary for each item.
- Allow optional integration with the Google Gemini API or another AI API.

## 3. AI assistant
- Let users select the Google Gemini API for AI features.
- Provide Korean-language summaries and analysis based on stocks, news, filings, charts, and portfolios.
- If no AI API key is configured, provide a working local rule-based summary fallback.

## 4. Charts
- Provide candlestick charts, volume, moving averages, Bollinger Bands, RSI, and MACD.
- Support these time ranges: 1M, 3M, 6M, 1Y, 2Y, 5Y, and 10Y; and these intervals: 1D, 1W, and 1M.
- Changing the selected range or interval must load and display the corresponding chart data.
- Provide an enlarged view for portfolio graphs.

## 5. Portfolios
- After sign-in, let users view their own portfolio.
- Create an integration structure for broker APIs, with examples including Alpaca, Interactive Brokers, and Korea Investment & Securities Open API.
- Show holdings, market value, profit and loss, allocation, sector allocation, country allocation, currency allocation, estimated dividends, and whether rebalancing may be needed.
- Allow users to enter and edit portfolio holdings manually.

## 6. Authentication and personal settings
- Visitors who are not signed in can access general market data and news.
- Signed-in users can save and access their portfolio, watchlist, API keys, AI settings, layout, alerts, and default symbols.
- Persist settings separately for each user.
- Document secure handling of sensitive API keys and relevant security precautions.

## 7. UI and interaction
- Follow the attached image's high-density financial-terminal style.
- Place global navigation, a command bar, an AI button, and an index strip at the top.
- Use global menu examples: Markets, Portfolio, Research, Tools, and AI.
- Use internal tab examples: Market, Monitor, Chart, News, Portfolio, Options, Orders, and AI. Each tab must actually switch the displayed view.
- Make panels draggable and resizable, and allow users to drag panel boundaries to adjust the widths of the left, center, and right areas.
- Save layouts per user.
- Prevent content from being cut off with well-designed panel scrolling and responsive layouts.

## 8. Orders and trading safety
- Keep real order placement safely separated from other features.
- Use paper trading by default.
- Enable live broker orders only when explicitly turned on in settings.
- Make it unmistakable in the UI whether the user is viewing or placing a paper trade or a live trade.

## 9. Deployment
- Support local execution and production-server deployment.
- Provide Docker and docker-compose files, plus an example environment-variable file.
- Document deployment to a production server and security considerations for HTTPS, authentication, sessions, and API keys.

## 10. Documentation and deliverables
Provide a complete runnable project as a ZIP, along with:
- A README and local run instructions.
- Production deployment instructions.
- A list of required API keys and descriptions of data providers.
- Instructions for configuring the Google Gemini API and integrating broker APIs.
- Documentation of authentication and security design, layout customization, data sources and limitations, and the policy for distinguishing real data from fake data.
- Working signed-in portfolio and per-user settings features.
- A high-density financial-terminal UI with draggable and resizable panels.

## Quality requirements
- Keep initial loading fast: show fast market data first, then load news, filings, AI, and portfolio data in the background.
- Never present fabricated values as real data.
- Clearly distinguish real data, delayed data, API limits, and unavailable data.
- Before delivering the ZIP, run the project, test it, and fix errors.