Write prompts

Every prompt on this page changes something in your account, so it needs Read and change access. See Access levels. For questions that only read, see Read prompts. Illustrative example. The figures are hypothetical, not a recommendation.

​

Record what already happened

These record a change you made elsewhere. This records the change in Allocait only. It moves no money and places no order. I added 50 shares of ALFA at $181.5 outside Allocait, add it. Claude reads your current ALFA holding from list_portfolios, then calls save_position with the new total (for example, 150 shares if you held 100) and the price. Your other holdings stay as they are, and cash moves by the cost of the 50 shares. I deposited $4,825 outside Allocait, record it. Claude calls record_cash_movement with direction: DEPOSIT, the amount, and an idempotency_key, so a retry can’t record it twice.

​

Keep your research

Add BRAV to my Main watchlist. Claude calls list_watchlists to find the Main watchlist, then save_watchlist with add: [{symbol: "BRAV"}]. Every other symbol on the list stays. Fill in today’s playbook. Claude calls list_portfolios to find the playbook, then get_playbook for today’s date (US Eastern) to see its symbols, its columns and the values already there. An input you set to keep until changed shows its latest value, marked as carried. Claude asks you for the cells listed as needing input (a blank cell of an optional input isn’t listed), then calls record_input_values by input name. For a CHOICE column, it uses one of that input’s options. Ask what changed since the last entry and Claude reads the same call: each value says what it was before and since when it has held.

​

Set up or edit rules

Here’s my investment policy statement, set up my rules from it. Claude reads the ranges from your statement to draft rules text, calls preview_rules to show you the diff, and, once you agree, calls apply_rules with the identical text. To start with no statement, you can run the draft_rules prompt from your client’s prompt menu. Otherwise Claude asks the plain questions one at a time. Here’s a setup file someone sent me, add it to my account. Claude calls preview_setup with the file’s text and shows you the author, the disclosure in the author’s own words, Allocait’s note about the numbers, and what would be added, kept as yours or left out. Once you agree, it calls apply_setup with the preview’s digest. The tool’s instructions tell Claude to ask you first and not to apply a file when there is no one to ask. The result carries a receipt_id, and undo_setup takes the import back. A setup import never makes a scenario active. See ALLOCAIT.md. Change my Equities band to 44% to 67%. Claude calls save_class_rule for Equities with band_min_pct: 44 and band_max_pct: 67. Every other rule in the scenario stays as it is, and the result carries a restore_point_id. Undo that last rule change. Claude calls restore_rules with the restore_point_id from the change. If it’s a new chat, get_rules lists the latest restore points.

​

Next steps