Rules First, Questions Second: Turn an AI Portfolio Review Into Something You Can Compare Month to Month

Most people ask an AI to “review my portfolio” and take whatever comes back. This approach does it differently: one short rules block up front, then narrow questions one at a time. The answers are easier to check and easier to compare month to month.

A Reddit user on r/PromptEngineering ran this test, and the details are useful. They connected Claude read-only to a portfolio tracker (a demo portfolio of about €660k, nine positions plus cash) and typed only “Review my portfolio.”

The key idea

The first answer wasn’t flattering, and the concentration call was fair: two chip stocks made up around 80% of the portfolio. The real problems were somewhere else:

  • It answered in dollars while the tracker shows euros, so no number could be checked without converting it first.
  • It drifted into advice (“you may want to decide whether to grow them or consolidate them”).
  • It mixed data (a dividend rating of 34/100) with its own opinion (“look weak”) without saying which was which.

None of that is about intelligence. It’s about the model having no rules for what kind of answer you want.

Old way vs. new way

The old way: one big prompt, or a vague one-liner. The model picks the currency, the tone, the level of advice and the format. Next month it may pick differently, so you can’t compare the two reports.

The new way: a short rules block as the first message, then six narrow questions, one message each. The rules stay fixed. Only the questions change the output.

Here is the rules block from the post:

Describe my portfolio plainly, in euros, using only the data returned by [tool]. No praise, no reassurance, and no recommendations to buy, sell or hold. Flag concentration and anything that changed compared to last month. If data is missing, say so instead of guessing.

Each sentence fixes one of the failures above. “In euros” fixes the currency. “No recommendations” stops the advice drift. “Only the data returned by [tool]” keeps the model grounded in your numbers.

The line that did the most work

The author says “If data is missing, say so instead of guessing” mattered most. With it in place, Claude:

  • Explained why the tech weighting moved from 85.46% to 87.33%: VOO was counted as one fund in one view and spread across its sectors in the other.
  • Declined to convert last year’s dividend without an exchange rate for that specific day.
  • Added a “what I can’t separate” section on currency moves vs. price moves.

A model that admits a gap is far more useful than one that fills it with a confident guess.

How to copy it 🧭

  1. Write your rules block once. Cover the currency, the data source, what’s banned (advice, praise), what to flag, and what to do when data is missing. Keep it to a few sentences.
  2. Send it as the first message of a fresh chat. Don’t bury it inside a question.
  3. Ask narrow questions, one per message. The post used six: allocation by sector and holding; share of the top 5 and the largest sector; what helped and hurt the return this year; contributions vs. market movement this month; dividends this month vs. the same month last year; and one holding in detail.
  4. Save the same rules and questions for next month. Same inputs, same format, so differences in the output reflect your portfolio and not the model’s mood.
  5. Spot-check one number against the source. Every time.

Why the spot-check stays 🔍

The author is honest about a slip. Claude described the remaining 5.51% as “three stocks and two cash balances” when it was four stocks. The percentage was right and the sentence was wrong. Also, the sector weight came out as 87.33% while the dashboard shows 87.3%, which is just rounding, but you only learn that by checking.

Rules reduce errors. They don’t remove them. One check per month is cheap insurance.

One caveat

This is a way to describe a portfolio, not to decide what to do with it. The rules block deliberately bans buy, sell and hold advice. Decisions stay with you.

Your turn

The author asked a good question at the end: do you use one long prompt for recurring reports, or a short rules block plus narrow follow-ups? For anything you’ll run more than once, I’d go with the second. Take a report you already ask an AI for every month, write a four-sentence rules block for it, and split it into single-question messages. Run it twice and compare the outputs side by side. That comparison is the whole point!

4 rules that turned an AI portfolio review from a one-off answer into something I can compare month to month
by u/TieTraditional5532 in PromptEngineering

Scroll to Top