mirror of https://github.com/MODSetter/SurfSense.git synced 2026-04-27 09:46:25 +02:00

API Test Bot d20cb8a538 feat(crypto): implement hybrid approach with real-time DexScreener tools

- Add crypto_realtime.py with get_live_token_price and get_live_token_data tools
- Register real-time tools in registry.py (no dependencies required)
- Export tool factories in __init__.py
- Create LiveTokenPriceToolUI component for real-time price display
- Create LiveTokenDataToolUI component for comprehensive market data
- Register tool-ui components in new-chat page

Hybrid Architecture:
- RAG (search_knowledge_base): Historical context, trends from indexed data
- Real-time tools: Current prices, live market data via direct API calls
- AI agent decides which to use based on query intent

2026-02-04 00:12:32 +07:00

3.4 KiB

Raw Blame History

stepsCompleted:

1
2
3
4
5
6
7
8
9
14 inputDocuments:
_bmad-output/planning-artifacts/prd.md
_bmad-epics/epic-1-ai-powered-crypto-assistant.md
_bmad-epics/epic-2-smart-monitoring-alerts.md
_bmad-epics/epic-3-trading-execution-safety.md
_bmad-epics/epic-4-adaptive-learning-evolution.md outputDocument: _bmad-output/planning-artifacts/ux-design-specification.md

UX Design Specification: SurfSense v2

1. Design Strategy

"Evolution, Not Revolution"

Core Philosophy: SurfSense v2 features will be "grafted" (injected) into the existing Research Dashboard rather than replacing it.
Goal: Maintain the professional, clean utility of the current "SaaS-style" research tool while adding "Crypto-Native" signals only where critical (the "Intel Layer").
Visual Identity: "Smart Cards" & "Traffic Lights" embedded in a Clean UI.

2. Core User Experience

The "Intel Layer" Concept

Problem: Users have to switch contexts between Charts (DexScreener) and Safety Scans (Scanners/Twitter).
Solution: A hybrid "Intel Layer" that sits on top of the chart or inside the research chat.
Mental Model: "Traffic Light System" (Red/Green/Yellow).
- 🔴 Stop: Scam/Rug/High Risk. (Immediate Action: Ignore)
- 🟢 Go: Safe/Whale Buying. (Immediate Action: Ape in/Research)
- 🟡 Caution: Mixed signals. (Action: Open Dashboard for Deep Dive)

Key Mechanics:

Initiation: Extension detects Token URL -> Shows Traffic Light Badge.
Interaction: Click Badge -> Opens Overlay (Summary).
Deep Dive: "Ask SurfSense" -> Redirects to existing Web Dashboard (Port 3999).
Integration: Inside the Chat Interface, AI answers are formatted as Rich UI Cards, not just text.

3. Visual Foundation (Confirmed Step 8 & 9)

Tokens & Theming

Source of Truth: Inherited from existing surfsense_web (globals.css + Tailwind v4).
Base Theme: Dark Mode (Deep Navy / #0B1221) to match crypto aesthetic but cleaner.
Typography: Inter (Sans) for UI, Geist Mono for Data/Numbers.

Color Palette Extension (The "Traffic Light" Overlay)

Success (Buy/Safe): #22c55e (Green-500) - Solid, trustworthy.
Danger (Scam/Sell): #f43f5e (Rose-500) - Urgent, alarming.
Warning (Volatility): #f59e0b (Amber-500) - Cautionary.
Whale (Institutional): #3b82f6 (Blue-500) - Consistent with brand.

4. Component Strategy (Smart Cards)

Instead of building a full trading terminal, we build "Injectable Components":

Signal Card: Used in Chat & Extension. Shows Risk Score + 3 Key Bullets.
Whale Alert Row: Used in Lists & Notifications. Shows "Wallet X bought $50K".
Mini-Chart: Sparklines only, for quick trend context.

5. Mobile & Responsive

Extension: Fixed width (360px-400px), focused on "At-a-glance" data.
Web Dashboard: Responsive, but optimized for Desktop Research. Mobile view converts Tables to Cards.

6. Implementation Notes

Frontend: Next.js (Port 3999). Use standard Tailwind classes.
Backend: FastAPI (Port 3998). Serves structured JSON for UI Cards.
Extension: Chrome Side Panel API. Shares UI components with Web via Repo Monorepo/Shared Lib structure.

Status: ✅ APPROVED Next Steps: Proceed to Architecture Design to map these UI components to Backend APIs.

3.4 KiB Raw Blame History