feat: implement comprehensive Technical Analysis fundamentals
- Add TECHNICAL_ANALYSIS_BASICS.md with complete indicator explanations - Add TA_QUICK_REFERENCE.md for quick lookup - Enhance AI analysis prompts with TA principles integration - Improve JSON response structure with dedicated analysis sections - Add cross-layout consensus analysis for higher confidence signals - Include timeframe-specific risk assessment and position sizing - Add educational content for RSI, MACD, EMAs, Stochastic RSI, VWAP, OBV - Implement layout-specific analysis (AI vs DIY layouts) - Add momentum, trend, and volume analysis separation - Update README with TA documentation references - Create implementation summary and test files
This commit is contained in:
@@ -2,6 +2,10 @@
|
||||
|
||||
This is a Next.js 15 App Router application with TypeScript, Tailwind CSS, and API routes. It's a production-ready trading bot with AI analysis, automated screenshot capture, and real-time trading execution via Drift Protocol and Jupiter DEX.
|
||||
|
||||
**Prerequisites:**
|
||||
- Docker and Docker Compose v2 (uses `docker compose` command syntax)
|
||||
- All development must be done inside Docker containers for browser automation compatibility
|
||||
|
||||
## Core Architecture
|
||||
|
||||
### Dual-Session Screenshot Automation
|
||||
@@ -28,16 +32,23 @@ This is a Next.js 15 App Router application with TypeScript, Tailwind CSS, and A
|
||||
### Docker Container Development (Required)
|
||||
**All development happens inside Docker containers** using Docker Compose v2. Browser automation requires specific system dependencies that are only available in the containerized environment:
|
||||
|
||||
**IMPORTANT: Use Docker Compose v2 syntax** - All commands use `docker compose` (with space) instead of `docker-compose` (with hyphen).
|
||||
|
||||
```bash
|
||||
# Development environment - Docker Compose v2 dev setup
|
||||
npm run docker:dev # Port 9001:3000, hot reload, debug mode
|
||||
# Direct v2 command: docker compose -f docker-compose.dev.yml up --build
|
||||
|
||||
# Production environment
|
||||
npm run docker:up # Port 9000:3000, optimized build
|
||||
# Direct v2 command: docker compose -f docker-compose.prod.yml up --build
|
||||
|
||||
# Debugging commands
|
||||
npm run docker:logs # View container logs
|
||||
# Direct v2 command: docker compose -f docker-compose.dev.yml logs -f
|
||||
|
||||
npm run docker:exec # Shell access for debugging inside container
|
||||
# Direct v2 command: docker compose -f docker-compose.dev.yml exec app bash
|
||||
```
|
||||
|
||||
**Port Configuration:**
|
||||
@@ -119,7 +130,7 @@ Test files follow specific patterns - use them to validate changes:
|
||||
# Test dual-session screenshot capture
|
||||
node test-enhanced-screenshot.js
|
||||
|
||||
# Test Docker environment
|
||||
# Test Docker environment (requires Docker Compose v2)
|
||||
./test-docker-comprehensive.sh
|
||||
|
||||
# Test API endpoints directly
|
||||
@@ -134,6 +145,7 @@ Browser automation debugging:
|
||||
- Debug screenshots: `takeDebugScreenshot('prefix')`
|
||||
- Session persistence prevents repeated logins/captchas
|
||||
- Use `npm run docker:logs` to view real-time automation logs
|
||||
- All Docker commands use v2 syntax: `docker compose` (not `docker-compose`)
|
||||
|
||||
## Code Style & Architecture Patterns
|
||||
- **Client Components**: Use `"use client"` for state/effects, server components by default
|
||||
Reference in New Issue
Block a user