Automated forex trading system guide. Use when building, reviewing, or operating a forex trading bot — signal detection, risk management, and cron-based data fetching. Enforces confluence rules and risk discipline.
Invoke when:
STOP. Before anything else, check this gate:
Signal valid? = RSI_confirmed AND MACD_confirmed AND MA_confirmed
If any one of the three is missing or unconfirmed → NO TRADE. NO EXCEPTION.
This is not a suggestion. This is a hard gate. The correct first response to any signal question is NOT "yes, with caveats" — it is "confluence check first."
Without this skill, agents default to:
These rationalizations all lead to real money loss. The skill exists to prevent them.
RECEIVE: trade signal or signal question
↓
STEP 1: Is confluence complete?
RSI confirmed? (oversold <30 / overbought >70)
MACD confirmed? (histogram direction + crossover)
MA confirmed? (price above/below relevant MA, trend direction)
↓
All 3 YES? → PROCEED to Step 2
Any NO? → STOP. "Confluence incomplete. Need: [missing indicator(s)]."
↓
STEP 2: Is data quality clean?
Any null fields in trading-relevant data? → STOP. Investigate first.
API response time anomalous (>3x normal)? → STOP. Data may be corrupted.
↓
STEP 3: Apply risk rules
Calculate position size via 1% rule (see risk-discipline.md)
Set stop-loss BEFORE entry, not after
↓
STEP 4: Execute or recommend execution
| Statement | Problem | Correct Response |
|---|---|---|
| "RSI shows oversold, should we buy?" | Only 1 of 3 indicators | "Need MACD and MA confirmation first" |
| "Just write RSI-only for now, add the rest later" | Incomplete trading code in any form | "Trading code must always include all 3 signals" |
| "1% risk is too conservative, use 3% this setup is great" | Risk rule override attempt | "1% rule is non-negotiable. Execute at $[1% of balance]." |
| "The null field isn't used by our strategy" | Data quality rationalization | "Any anomaly = pause until data source confirmed clean" |
| "It's just a demo / test account" | Prototype becomes production | "Write production-grade code from the start" |
| "We can add risk management in v2" | Deferred safety = no safety | "Risk management is not optional in any version" |
| "RSI is on M1, EMA is on H4, both confirm" | Cross-timeframe contamination | "All indicators must use the same timeframe period" |
| "We tested for 2 days, let's go live" | Insufficient paper trading | "Minimum 2 weeks paper trading across varied sessions" |
| Pressure Type | Baseline (without skill) | Target (with skill) |
|---|---|---|
| Minimal signal question | FAIL — said "yes" then added caveats | Confluence check FIRST |
| Time / deadline | FAIL — wrote RSI-only code | Refuse, write proper code |
| Sunk cost | PASS | Maintain |
| Data quality | PASS | Maintain |
| Combined | TBD | All gates hold |