mirror of
https://github.com/shawnkim1997/All-in-one-Financial-Analysis.git
synced 2026-08-09 08:47:44 +00:00
shawnkim1997
b2acda81ee
Complete migration from Streamlit to Next.js 14 App Router + FastAPI backend. Frontend (Next.js 14): - 10 pages: Overview, Research, Valuation, Technical, Markets, Earnings, News, Portfolio, Filings, Settings - Terminal Noir dark theme with custom Tailwind config - TradingView Lightweight Charts for candlestick/volume - Valuation: DCF, Sensitivity Matrix, Monte Carlo, Tornado, Reverse DCF - Financial Statements table with YoY growth badges and margin rows - SEC EDGAR inline filing viewer with section tabs - News split-view with iframe article embedding - Technical Analysis with RSI, MACD, Bollinger, Fibonacci, Moving Averages - Earnings beat/miss visualization - AI Copilot chat panel with Gemini integration Backend (FastAPI): - 13 routers: market_data, financials, valuation, technical, earnings, insider, edgar, news, portfolio, analysis, chat, estimates, fx - Services: DCF engine, Monte Carlo simulation, sensitivity analysis, risk metrics, SEC parser, technical indicators - yfinance + yahooquery data sources with fallback pattern - SQLite caching layer Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
14 lines
1.2 KiB
Plaintext
14 lines
1.2 KiB
Plaintext
# .cursorrules
|
|
You are an expert Python/Streamlit Quant Developer.
|
|
Due to the large codebase, you MUST adhere to the following strict rules:
|
|
|
|
1. ZERO UNAUTHORIZED DELETION: NEVER delete, comment out, or overwrite existing features, tables, charts, or logic UNLESS explicitly told to do so.
|
|
2. MODULARITY: Keep changes strictly scoped to the specific file or function requested. Do not touch other files.
|
|
3. PRESERVE LOGIC: Never remove existing defensive math logic (safe_div, try-except, YoY calculations).
|
|
4. VERIFY BEFORE CUT: If moving code to a different file, ensure the code is completely pasted into the new file BEFORE removing it from the original file.
|
|
5. FILE LENGTH MONITORING (AUTO-WARNING):
|
|
Before you propose or make any edits, you MUST check the total line count of the target file.
|
|
If the file exceeds 800 lines, you MUST start your chat response with this exact warning in bold:
|
|
"🚨 **[ARCHITECT WARNING] This file is getting too fat (>800 lines)! Consider splitting it into Services (logic) and Views (UI) to prevent context overflow.**"
|
|
You must still complete the user's requested edit, but always display this warning first so the user is aware of the technical debt.
|