trading-best-practices
Critical analysis of trading techniques and financial innovation
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Critical analysis of trading techniques and financial innovation
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
TDD workflow for implementing features
Test and validation workflow before commit
Keep project documentation up to date
Manage and enforce project specifications for consistency
Designing premium user interfaces with egui
Trading performance evaluation via backtesting and metrics
SOC 직업 분류 기준
| name | Trading Best Practices |
| description | Critical analysis of trading techniques and financial innovation |
This skill ensures that trading implementations follow current best practices and avoid common pitfalls in algorithmic trading. It includes mechanisms to stay updated with the latest financial research and market structure changes.
Position Sizing:
Stop Losses:
Drawdown Protection:
Avoid Overfitting:
Backtesting Integrity:
Statistical Validation:
Execution Quality:
Regime Awareness:
| Pitfall | Why it's bad | Solution |
|---|---|---|
| Curve fitting | Strategy works on past but fails live | Walk-forward testing, simplicity |
| Ignoring costs | Profitable backtest becomes losing live | Include realistic commissions + slippage |
| Revenge trading | Emotional decisions after losses | Automated rules, circuit breakers |
| Over-leveraging | One bad trade wipes account | Fixed fractional position sizing |
| No stop loss | Small loss becomes catastrophic | Always use stops based on volatility |
| Ignoring correlation | Diversification illusion | Monitor sector/asset correlation |
To stay current with financial innovation, perform quarterly reviews:
# Use web search to find recent research
# Topics to research:
# - "algorithmic trading best practices 2026"
# - "quantitative finance risk management"
# - "market microstructure changes"
# - "regulatory changes algorithmic trading"
Compare findings against:
src/domain/risk/ - Risk management logicsrc/application/strategies/ - Strategy implementationsdocs/STRATEGIES.md - Strategy documentationDocument any practices we're missing or doing incorrectly.
If gaps found:
/implement workflowBefore implementing ANY new strategy:
// ❌ RED FLAG: No stop loss
if signal == Signal::Buy {
execute_order(symbol, quantity); // Where's the stop?
}
// ❌ RED FLAG: Fixed position size (ignores risk)
let quantity = 100; // Always 100 shares?
// ❌ RED FLAG: No transaction costs
let profit = exit_price - entry_price; // Ignores commissions/slippage
// ❌ RED FLAG: Too many parameters
struct Strategy {
sma_period_1: usize,
sma_period_2: usize,
rsi_period: usize,
rsi_oversold: f64,
rsi_overbought: f64,
macd_fast: usize,
macd_slow: usize,
// ... 20 more parameters = overfitting
}
// ✅ GOOD: Risk-based position sizing with stop
let risk_amount = capital * risk_per_trade;
let stop_distance = entry_price * atr_multiplier;
let quantity = risk_amount / stop_distance;
let stop_loss = entry_price - stop_distance;
Academic Research:
Industry Standards:
Market Data:
benchmarking skill to validate strategiescritical-review skill for code qualityrust-trading skill for implementation rulesdocumentation skill when best practices change