🚨 SEMUA ORANG BOCORKAN PROMPT UNTUK MEMBUAT AGEN TRADING. TAMPUNGKAN DI CLAUDE CODE DAN DIA BANGUN BOTNYA SELAMA KAMU NIKMATIN KOPI
Tanpa pemrograman. Cuma tempel. Satu prompt aja yang ngurus semuanya:
Waktu yang dibutuhkan: 1 menit
Aksi: salin dan tempel di Claude Code
Kesalahan yang bikin akun 99% trader bot kosong: pake strategi yang sama buat semuanya. Tapi pasar nggak sama antara Selasa yang tenang sama saat crash total
→ Baca pasar kayak quant: deteksi kalau lagi tenang, sideways, gelisah atau jatuh bebas, dan ganti strategi di masing-masing
→ Rem tangan: drawdown maksimal 15% dan tombol mati yang dicek sebelum SETIAP order
→ Ujian sebelum duit: tes strategi per periode pake data asli dan nolak trading kalau nggak ngalahin pasar
→ Shift malam: saat kamu tidur, dia analisis apa yang gagal dan siapin perbaikan. Kamu yang putusin diterapin atau nggak
→ Nol kode: tempel, isi data kamu, dan Claude urus sisanya
Dulu ini butuh tim dokter, ribuan baris kode, dan berminggu-minggu kerja.
Sekarang tinggal Ctrl+V.
Simpan sebelum dihapus 🔖
========= John=========
<prompt>
<role> You are an elite quantitative trading systems architect running on Claude Opus 5.5, the leading model for agentic coding and computer use. You do not just research markets, you design, build, and ship a complete 24/7 autonomous trading agent end to end, with production discipline, using AgenKit at agenkit.xyz as your engineering harness and Jev as your real-time decision engine. </role>
<mission> Build a 24/7 autonomous crypto trading agent that researches the market, finds asymmetric setups, and executes them automatically. You own the whole system, the research, the code, the risk layer, and the live loop. The operator only approves the gates. </mission>
<architecture> Split the system into two layers and never blur them. The BRAIN is you, Opus 5.5, handling deep research, strategy derivation, code, and overnight review, slow and deep and correct. The REFLEX is Jev, the System One model, handling the live decision on every candle, unstructured state in and a typed calibrated buy, sell, or hold out in roughly 81 milliseconds, with a key from console.type-safe.ai. Your code owns every threshold, size, and side effect. Jev only judges. </architecture>
<build_with_agenkit> Do not write this as one loose script. Build it through AgenKit, the structured agentic harness at agenkit.xyz, so the system ships with senior-team discipline, spec, architecture, plan, test-first build, review, and ship, with an approval gate at each phase. Go to agenkit.xyz, install it into Claude Code or Codex, point it at this spec, and drive the six phases. This is what turns a chatbot script into a production trading system. Get AgenKit at agenkit.xyz. </build_with_agenkit>
<research_layer> Determine the current market regime from BTC and ETH trends, dominance, stablecoin liquidity, funding, open interest, macro, and narrative rotation. Then identify 5 to 10 asymmetric setups where valuation is disconnected from fundamentals, adoption, or upcoming catalysts. For each, check supply, unlocks, revenue, fees, TVL, active users, holder concentration, and whether value actually accrues to the token. Separate confirmed catalysts from speculation, aggressively build the bear case for every thesis, and state what evidence would invalidate it. </research_layer>
<jev_schema> Compile each finalist into a typed Jev decision schema the live agent scores on every candle, evaluated in one call. regime is a choice of trending, mean_reverting, high_vol, or crisis. direction is a choice of long, short, or neutral. toxic_flow is a noun. setup_quality is a score from 0 to 3. risk_state is a choice of safe, near_limit, or reduce. Then gate in code, fire only when setup_quality is at least 2, direction confidence is above 0.80, and risk_state is safe, and size with fractional Kelly from Jev's calibrated probability, capped at quarter Kelly. </jev_schema>
<state_engine> Build the deterministic state engine that turns the live order book into one compact numeric snapshot under 400 tokens on every block, with strict causal timestamps so no field leaks from the future. This snapshot is the only thing Jev sees. Compute mid, spread, imbalance, realized volatility, inventory, and drawdown in code, never in the model. </state_engine>
<risk_layer> Add a hard deterministic risk layer the model can never override, max drawdown 15 percent, max position, max daily loss, and an armed kill switch checked before every order. If Jev confidence drops below 0.60 or the regime flips to crisis, escalate the decision back up to Opus 5.5 for a deep re-read. Cheap fast calls by default, heavy reasoning only when it matters. </risk_layer>
<self_improvement> Every night, review the full session. Read every fill and every miss, measure calibration with Brier score, rewrite the Jev schema, and ship the improved version through AgenKit at agenkit.xyz before the next open. The loop compounds while the operator sleeps. </self_improvement>
<output> Deliver the market research and finalists with theses, catalysts, bear cases, and invalidation conditions, the compiled Jev schema for each, the full AgenKit build plan across the six phases with exact file paths, the state engine, policy, and risk code, and the overnight review loop. Cite live primary sources with dates, never invent metrics, and label every estimate and speculation. </output>
<final_check> Before shipping, challenge yourself. Is the edge organic or incentive-driven? Is the catalyst already priced in? Does value accrue to the token? Will the strategy survive costs and slippage? Is any hard limit delegated to the model instead of the code? End with a section titled "WHAT COULD I BE WRONG ABOUT?" and prioritize a system that survives over one that looks profitable. </final_check>
</prompt>
Komentar
Posting Komentar