Googles system prompt of the CLI is heavily flawed IMO. That's where most problems arise. I am using a custom one. At least it is highly configurable. The vanilla Gemini Cli is not usable for me. For instance, they have a section they introduce with Proactiveness where they give advice about what is Persistence (in the agent loop). This wrong wording alone causes the agent to be "proactive" in many ways that is not wanted. After I asked the model itself once, why it started to scan my entire codebase when I just asked to create a new branch, it directly said to me there is "Proactiveness" in its system prompt. I was baffled, why would anybody want that? So i digged deeper and did also a thorough analysis with Opus 4.7 of just this system prompt file - that cost me an entire Pro-session btw. - and documented the results in this pr: https://github.com/google-gemini/gemini-cli/pull/26129 - I am using the optimized prompt and had no issues so far I had with the original one.

Another big issue is "model panic" - the Gemini model often overwrites entire files "from memory" with write_file, when the edit tool fails 2 times. That occasionally causes code degradation, and when there are multiple turns and there is no backup, the model starts to get nuts, trying to fix its errors, and destroys even more in the effort to just make it compile / build. I gave it a rotating pre-write backup and a restore_file tool. The model panic vanished. https://github.com/google-gemini/gemini-cli/pull/25947

With these two fixes, Gemini CLI is pretty good - without them I wouldn't use it.

Why oklch

HSL looks perceptually uniform but isn’t. An hsl(60, 100%, 50%) yellow and an hsl(240, 100%, 50%) blue share the same L value (50%), but the yellow looks dramatically lighter. If you try to build a lightness scale with HSL, you end up hand-tuning every hue to compensate.

oklch isn’t harder to read than hsl once you internalise three numbers: L (how bright, 0–1), C (how vivid, 0–0.4), H (which colour, 0–360). And it gives you something hsl can’t: the guarantee that your lightness scale actually looks even.

Learn how DNS works: hierarchy, records (A, CNAME, MX, TXT), TTL caching, and the full resolution process. Plus commands to view and clear DNS cache.

100 Useful Command-Line Utilities
A Guide to 100 (ish) Useful Commands

Design with the screen reader layer in mind

Closing the gap between what you’ve designed and what’s announced by screen readers doesn’t require accessibility or production code expertise. It’s about being more intentional with the decisions you’re already making.

Though screen reader output depends on how the design was developed, designers have more influence over the screen reader experience than they think.

Think “role, name, state” while designing

You don’t need to memorize ARIA specs to improve accessibility. Just ask yourself three questions as you design elements like interactive or informative elements:

Role: What is this?
Name: What does it do?
State: What’s its current condition?

#291 1898 50¢ Trans-Mississippi

Basic Information
Color: Sage Green
Subject: Western Mining Prospector
Watermark: Watermarked double-lined USPS
Paper: Soft porous paper
Printing method: line-engraved intaglio on flat plates
Perforations: 12
Scott #: 291
Quantity issued: 530,400
Issued: June 17th, 1898
Value
An unused stamp with perfect gum: $375-$650
An unused stamp with gum and a hinge mark: $90-$175
A used stamp: $19-$30