Now what if it didn't pollute browser history

You don't want to run tests after every file change, because that will distract Claude from finishing whatever it's doing and add noise to the context window. Of course the tests will be broken if Claude hasn't finished the full change yet.

Running tests makes most sense on the Stop hook event, but personally I've found CLAUDE.md instruction of "Run `just check` after changes" to be effective enough. The Stop hook has the issue that it will run the checks every time Claude stops responding, even after without any changes.

Won't the LSP distract Claude too? I am trying to think of ways to make Claude faster at iterating by reducing tool calls. That always seems to be a bottleneck when it's doing tons of back-and-forth with tool calls.

Depends on Anthropic has implemented it I guess. I haven't had it activate yet despite the prompt to install an LSP.

Exactly. This is why the workflow of consulting Gemini/Codex for architecture and overall plan, and then have Claude implement the changes is so powerful.

It's not enough. Sometimes skills just randomly won't be invoked.

Have used Alfred for 10+ years at this point. Some colleagues are hyped about Raycast, but to me the pricing model is a joke. Pay (monthly) for AI - how about I bring my own API key? Pay (again, monthly) for unlimited clipboard history - lol. Free plan, "Free, forever". Yeah, until it isn't.

Alfred isn't the shiniest thing anymore but it's stood the time remarkably well, something I value very highly for tools as central to my workflow as Alfred.

You can use bring you own key for free

Awesome if that's the case

tmux users might find this useful: https://github.com/raine/workmux

Said policy:

    * Any contribution of any LLM-generated content will be rejected and result in
      an immediate ban for the contributor, without recourse.

So far not impressed with CC's ability to invoke skills automatically.

I made a skill with the unambiguous description: "Use when creating or editing bash scripts"

Yet, Claude does not invoke the skill when asked to write a bash script.

https://gist.github.com/raine/528f97375e125cf97a8f8b415bfd80...

Hah, yeah that's a total miss there.

Maybe it messed that up because writing bash scripts is so core to how Claude Code works? Much of the existing system prompt (and I bet a lot of the fine-tuning data) is about how to use the Bash tool.

For good measure, I tried:

    description: CRITICAL: Use when writing bash scripts

Surprisingly no effect either. I would've thought adding "CRITICAL" would somehow promote that instruction in the sea of context.

Try writing it like this: "Use it when creating a bash script or editing a bash script"

I tried. Claude Code can't enable a disabled MCP on the fly.

In the AI image generation scene, is there anything solid yet in the way of generating vector illustrations for apps?