For three years I let an app hand me a number — 1,750 calories — with the explanatory power of a fortune cookie. I'd hit it on disciplined days and ignore it on the rest, and the reason I ignored it so easily was that I never understood it. Why 1,750? Why not 1,600, or 2,000? Why was the protein target so aggressively high that I felt like I was eating chicken in my sleep? A number you don't understand is a number you won't respect, and I did not respect that number.
What I wanted wasn't a different target. It was the working. I wanted to see the equation that produced my life's nutritional homework, the way a maths teacher makes you show your steps so you actually learn the thing instead of copying the answer.
Watching the calculation happen
I ran my stats through the Macro and Meal Targets From Your Stats, With the Maths Shown prompt, and I used Gemini 2.5 Pro on purpose — it's genuinely good at laying out tables and step-by-step numeric reasoning without losing the thread. It started with my BMR using the Mifflin-St Jeor equation, with my actual numbers plugged into it, not a hidden formula. Then it multiplied by my activity factor to land on a TDEE of 1,980. Then — and this was the bit that flipped a switch — it subtracted a modest 300-calorie deficit for fat loss and explained that 300 is conservative enough to be sustainable, which is exactly why I'd failed every aggressive crash before.
- Seeing the BMR equation with my own numbers made the target feel like a fact about my body, not an arbitrary app guess
- The macro table explained my 150g protein as 1.8 g/kg of bodyweight 'to preserve muscle in a deficit' — finally, a reason
- It showed the calorie arithmetic: 150g protein x 4 kcal = 600 calories, leaving the rest for carbs and fat
- The note that metabolism varies 10-15% between people stopped me obsessing over a daily 50-calorie miss
The sample day was the part I keep
The section I actually use day to day is the sample meal table, because it answered the question apps never do: what does this look like on a plate? Greek yogurt and berries at breakfast, a chicken-and-rice bowl for lunch, salmon and veg for dinner, cottage cheese as the evening snack, with a totals row that landed within spitting distance of my targets. It was deliberately unglamorous — no twelve-container meal-prep fantasy — which is the only kind of plan a person with a job actually keeps.
The 'hitting protein' strategies quietly fixed my biggest practical problem. I'd been treating chicken breast as my only protein source, which is a fast track to hating food. The prompt suggested front-loading protein at breakfast, keeping cottage cheese and edamame as default snacks, and anchoring each meal around a protein source first. None of it was exotic. All of it was stuff I could buy at a normal shop on a normal Tuesday.
The safety rail I didn't expect to need
Here's a detail that turned me from impressed to genuinely trusting. When my partner ran her stats through the same prompt — she's smaller than me and was tempted toward an aggressive cut — the output flagged that her proposed target was creeping toward the floor and explicitly recommended she not drop below the threshold without talking to a dietitian. It refused to just hand over a dangerously low number because she'd asked for fast results. A calorie app would have cheerfully obliged and let her under-eat. The prompt has that guardrail baked in, and watching it actually fire on a real person was the moment I stopped thinking of this as a clever calculator and started thinking of it as the closest free thing to a sensible nutritionist who won't enable your worst impulses.
Why Gemini was the right tool for this specific job
I want to be precise about why I reach for Gemini 2.5 Pro here rather than just using whatever's open. This prompt is fundamentally a structured-numbers task: a multi-step calculation, then two formatted tables, then a totals row that has to actually add up. That's squarely in Gemini's wheelhouse — it lays out clean Markdown tables, keeps the arithmetic consistent across the macro table and the sample-day table, and doesn't lose the thread halfway through a multi-step formula. I've run the same prompt through chattier models that gave me lovely prose and a sample day whose calories didn't reconcile with the target three paragraphs earlier. For something where the whole value is in the numbers being right and legible, the model that's best at tables wins.
Why understanding beat willpower
I've now hit my targets for eight straight weeks, which is roughly eight times longer than any previous streak. The change wasn't more discipline. It was comprehension. When you understand that your deficit is 300 calories because that's the sustainable rate, and your protein is 150g because that's what protects your muscle while you lose fat, the targets stop being a cage and start being a tool. I pair this with my Weekly Training Block From Your Goal, Gear, and Real Schedule prompt so the food and the training are pointed at the same goal instead of quietly contradicting each other — there is nothing more demoralising than eating in a deficit while running a muscle-gain program and wondering why neither is working.
If you've been blindly obeying a calorie app and resenting it, grab the Macro and Meal Targets From Your Stats, With the Maths Shown prompt on Prompt Dock and run your own numbers through it. Watch the equation. Understand the why. The fastest way to start respecting a target is to see exactly where it came from — and then it's not the app's number anymore. It's yours.