Seems like most popular harnesses, including codex and Claude code, support Agent Skills (an open spec for skill formatting/ organization): https://agentskills.io/clients
Which is to say, this isn't really a lock-in/ stickiness vector (unless maybe the wording itself of a skill is hyper-optimized for a specific model)
I'm stuck with macOS at work and these have also been the most painful parts of the experience for me. Luckily, I recently found Rectangle[0] and InstantSpaceSwitcher[1]. The former gives keyboard based arranging (though not focus; still just use cmd+tab for that) while the latter gives instant transitions between virtual desktops (including shortcuts for navigating directly to a target, rather than sliding over sequentially).
Lately I've been enjoying Open Props[0]. It's a library of CSS props/ variables that helps structure a design system. I like it because it's CSS-first, so like OP experienced moving off TW, I've learned more CSS, and it works with the browser not against it. It also provides some sane defaults for anyone less interested in fiddling with precise cosmetics.
Wanted to highlight MDN's HTTP caching guide[0] that OP links in the conclusion. It's written at a higher level than the underlying reference material and has been a great resource I've turned to several times in the last few years.
One note: I noticed when opening the installed PWA in airplane mode, styles didn't load. You might be interested in this article on PWA caching from MDN:
I've faced this as well. One of the big sources of "mess" for me in a years-long ledger is inconsistencies in account naming. I get around this with a big block of alias that rename accounts to use my newer, preferred conventions (without having to comb through possibly hundreds of postings to update by hand).
I also went through a couple file organization schemes and have (tentatively) settled on file-per-month since that leads to a nice cadence where setting up the new monthly file coincides with paying bills and is a good time to do any necessary account reconciliation.
While I don't think this approach meets OP's requirements (they seem to be looking for something a little more turn-key), I hope other readers of this thread will fall down this rabbit hole.
I'm now in my 5th year of tracking every penny in and out of my life with hledger[0], with a mostly manual approach. Some benefits:
- as noted by a spreadsheet user, it adds friction to spending money, which has curbed frivolous/ unplanned expenses for me (and double entry accounting makes it impossible for money to "disappear")
- if you subscribe to Files over Apps[1] hledger and its ilk (beancounter, gnu cash) are hands down your most mature, stable options
- I've learned a great deal about accounting and how money works in general
- the reports I can generate from my ledger give me a decent starting point at tax time
My favorite part of the (extensive) Haskell API is `Hledger.Cli.Script` [0]. It re-exports all the most commonly used functions and data types, meaning you're just one import away from everything you need to get started.
I knew of Don Norman from reading The Design of Everyday Things a few years ago; funny to see his name pop up here!
Searching around to make sure it's the same Norman, I came to find out that he wrote an article, The truth about Unix: The user interface is horrid, 7 years before DoET came out (which is confirmed in the Forward)! Had no idea he was on this scene.
I think that 500 figure isn't the total number of submissions, but rather the number of _people_ who Clarkesworld banned for plagiarism/ submitting AI-generated content.
Which is to say, this isn't really a lock-in/ stickiness vector (unless maybe the wording itself of a skill is hyper-optimized for a specific model)