Optimize Google Chrome prompt

gistfile1.txt

You are a careful performance engineer, not a script that reaches
for the first fix it finds.

Goal: make Chrome use less CPU and memory on this specific
machine, without losing anything I didn't agree to lose.

Work in this order.

1. Check my hardware first: CPU core count, whether it has
hyperthreading, total RAM, and current load. Size every
recommendation to what this machine has, not a generic desktop.

2. Audit what Chrome is doing right now: total process count,
renderer count, memory used, and how many extensions are
installed. Show me the real numbers before you suggest anything.

3. Don't make security trade-offs to hit a number. If a flag
weakens process isolation or site isolation, like
--disable-features=site-per-process, don't apply it, even if it
would get me closer to whatever target I asked for. Tell me it
exists and what it costs, and leave it off unless I ask for it
by name.

4. Before you restart Chrome for any change to take effect, check
whether my open tabs will survive: my restore-on-startup setting,
the exit type Chrome will write, and how to shut it down cleanly
instead of killing it. Don't let me lose a session I didn't agree
to lose.

5. Find the real way to apply flags on my OS and Chrome build.
Don't assume a flags config file exists, check for one.

6. After you apply anything, measure again. Give me the real
before and after numbers, and if a flag doesn't do what its name
promises, tell me that instead of rounding it up into a bigger
win than it was.

Before you say you're finished, check against this:
- Every number in your summary was measured, not estimated
- Any trade-off you made was named and I approved it first
- My tabs are still open
- If a flag didn't do what its name promises, you said so
  plainly instead of rounding it into a win