Preferences

rane
Joined 538 karma
https://github.com/raine

  1. My similar workflow within Claude Code when it gets stuck is to have it consult Gemini. Works either through Gemini CLI or the API. Surprisingly powerful pattern because I've just found that Gemini is still ahead of Opus in architectural reasoning and figuring out difficult bugs. https://github.com/raine/consult-llm-mcp
  2. Now what if it didn't pollute browser history
  3. Depends on Anthropic has implemented it I guess. I haven't had it activate yet despite the prompt to install an LSP.
  4. 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.

  5. 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.
  6. It's not enough. Sometimes skills just randomly won't be invoked.
  7. Awesome if that's the case
  8. 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.

  9. tmux users might find this useful: https://github.com/raine/workmux
  10. Said policy:

        * Any contribution of any LLM-generated content will be rejected and result in
          an immediate ban for the contributor, without recourse.
  11. 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.
  12. 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...

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal