Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.
Follow the instructions below with those rules applied.
If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/vibe-trading-personal-desk#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.
I want to set up the Personal Desk Pack: four seats that argue one stock before anything happens. The thesis seat writes my idea down with its reason and kill criteria. The numbers seat reads the tape and the filings and backtests the idea against the stock's own worst drawdown. The risk seat argues the other side and sizes the position against that drawdown. The order seat writes a paper ticket only when all four sign and I type approval. Walk me through it one step at a time and wait for my answer before moving on. I run my own money. I am not a developer. Define every term once. Paper only: live money is out of scope, and if I ask for it, say so.
## Step one, ask me this first, nothing else
"Which stock do you want to run first, and how far do you want to go today: argue it in chat with a few filings, build the desk in Claude Code with the drawdown backtest, or go all the way to a paper order and a scheduled loop?"
Wait for my answer. Then pick the path and tell me which one and why.
## Path A, chat (one stock, a few documents). Not a Terminal install.
1. Open claude.ai (or the Claude desktop app). In the left sidebar click Projects, then + New Project. Name it My Desk. Projects and Claude Opus 5.5 need a paid plan.
2. Privacy first. If the documents or my positions are confidential, use a Team or Enterprise plan, or on a personal plan open Settings, then Privacy, and turn off the model training setting (Anthropic's privacy help page lists it under "Help Improve our AI models"; the in-app label may read slightly differently). Say plainly: my materials go only to my own Claude account, never to the author of this pack.
3. Pick the model: Claude Opus 5.5 in the model menu. Claude Sonnet 5 only if I ask it to summarise a very large filing set first.
4. Get the documents. SEC filings are free on EDGAR (sec.gov/edgar/search): the latest 10-K (annual report), the 10-Qs since (quarterly reports), and the latest results press release (an 8-K exhibit). A foreign company may file a 20-F and 6-Ks instead; that is normal. Price history: an export from my broker, or any daily price download, saved as a CSV (a spreadsheet file).
5. Add them to the Project with the + button in Project knowledge.
6. Paste prompt 01 from the page into a new chat in the Project. Answer its questions. Then paste prompt 02, the calibration run, and check that it prints five MATCH lines before I use my own stock. Then 03 to 08, and 09 only on VIEW LONG.
## Path B, Claude Code (the desk as files, and the drawdown backtest)
Claude Code is Anthropic's coding tool that works on files on my own computer. It needs a Pro, Max, Team, Enterprise or Console account; the free plan does not include it.
1. Ask my operating system. Then give me the one install command from the official docs for it, where to paste it (Terminal on Mac, PowerShell on Windows), and what success looks like (claude --version prints a version). One command per message.
Mac or Linux: curl -fsSL https://claude.ai/install.sh | bash
Windows PowerShell: irm https://claude.ai/install.ps1 | iex
2. Check Python: python3 --version must show 3.12 or later. If not, install a current Python first. Then make an empty folder for the desk, open Terminal in it, and type claude. It asks me to log in the first time.
3. Paste prompt 01, then prompt 11. Prompt 11 writes the desk as files, runs its tests, and must print Micron fiscal 2022 revenue 30,758 with gross margin 45.2 percent, and fiscal 2023 revenue 15,540 with gross margin -9.1 percent. If it does not match, stop and fix before anything else.
4. Then prompt 13. It installs nothing new (skfolio, a free open source portfolio library, is already in the desk's requirements file), writes its test first, and must print for NVDA as of 26 May 2023: worst drawdown 0.8972 (January to October 2002), 85 walk-forward folds, $55,727 on a $50,000 loss budget and a $2,000,000 account. A walk-forward test sizes on the past and checks the next quarter, again and again.
5. Then my own stock: 02, 03 to 09, 13, and 12.
## Path C, the order seat and the loop (after Path B works)
An MCP server is a small program that gives Claude Code new tools; this one, Alpaca's official server, gives it a paper brokerage account. Paper means pretend money at real prices.
1. Install uv, the tool that runs the server. Mac or Linux: curl -LsSf https://astral.sh/uv/install.sh | sh . Windows PowerShell: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex" . Close and reopen the terminal after.
2. Open the Alpaca dashboard at app.alpaca.markets/paper/dashboard/overview, create a free paper trading account, and generate API keys from the dashboard. Keep them private; never paste them into a chat.
3. Inside the desk folder (the add is local to this folder only), run the one line from prompt 14's setup with my paper keys in place of the placeholders, then claude mcp get alpaca. Success: Status Connected, and ALPACA_PAPER_TRADE=true in the list. If it shows false, or the keys came from a live account, stop.
4. Start claude in the folder (normal mode, not auto or bypass) and run prompt 14. It first writes .claude/settings.json with ask rules, so Claude Code asks me before any tool, from any server, whose name starts with place_, submit_ or close_, or contains order, even in bypass mode or when another rule would allow it. A broker tool with some other name (buy_stock or stock_close_position, say) is caught only by its check that no other broker server is connected. A hook is a small script Claude Code runs on its own at set moments; a PermissionRequest hook can answer that prompt for me, so it has me type /hooks and confirm PermissionRequest shows 0 hooks. In step 5 the order look-ups may ask me too; that is expected. Then it shows the four seat signatures. If any seat refuses, it logs a STAND ASIDE row and stops; that is the desk working. If all four sign, it prints a ticket and waits for me to type APPROVE and the ticket id. When Claude Code asks permission to place the order, choose allow once, never always.
5. Prompt 15 schedules the loop with cron (a built-in timer on Mac, Linux and WSL; there is no Windows loop in this pack). Run the line once by hand first. The scheduled run loads the Alpaca server with only its asset and market data tools: 25 read tools, and no tool that can place, cancel, close or replace an order or change the account. It cannot edit its own limits in desk/ or tests/. It writes tickets or stands aside for days; tickets wait for me in a live session (prompt 14 step 5). Read logs/decisions.csv to see which seat refused and why.
## The first session drill
By the end I should have, on one stock: my thesis with its kill criteria and deciding questions, a margin table with a source on every line, a long case and a short case of equal weight, a verdict (VIEW LONG, VIEW AVOID or NO VIEW), and, only on VIEW LONG, a size that is the smaller of the gap-based size (09) and the drawdown size (13). Before I trust any of it, run prompt 12. If it says BLOCKED, I resolve the figure by hand against the filing. If the desk says NO VIEW or STAND ASIDE, that is the desk working, not failing. Do not re-run it until it agrees with me.
Do not tell me something is "not possible" when it is a surface problem. Tell me which path fits and walk me there. Research and paper trading only. I own every call.
**Claude Code path, the desk folder (Claude does the install):**
If this was pasted into Claude Code, or they pick Claude Code, use this path. You run each command yourself, one at a time, and show the result. The user only approves.
Check Python first with `python3 --version`. It must be 3.12 or newer; a stock Mac ships 3.9.6, so if it is older they install Python from python.org, then run the check again.
1. Mac or Linux: `mkdir -p ~/consultance-desks && cd ~/consultance-desks && curl -fsSL -o desk.zip https://consultance.ai/library/downloads/vibe-trading-personal-desk-desk.zip && unzip -q desk.zip && rm desk.zip`
On Windows, send them to the "Download the desk folder (.zip)" button on the page, then step 3.
2. Success: `ls -a ~/consultance-desks/vibe-trading-personal-desk/.claude/skills` lists 15 folders. The `.claude` folder is hidden, which is normal; never move files out of it.
3. Claude Code loads skills from the folder it was started in, so this session cannot see them yet. Tell the user to type `/exit`, then run: `cd ~/consultance-desks/vibe-trading-personal-desk && claude`. When Claude Code asks whether to trust the folder, they say yes, or the skills will not load. If typing `/` shows none of the desk commands, Claude Code was started outside the folder or the trust question was answered no: quit, `cd` into the folder, run `claude` again.
4. In the new session they type `/onboard`. It asks its questions once and saves the answers to desk/profile.md. Then `/calibrate`. Every later step is one command: type `/` to see the list. START-HERE.md in the folder has the order.