Claude Code – Everything you can configure that the docs don't tell you
buildingbetter.tech
Claude Code – Everything you can configure that the docs don't tell you
1–10 of 76 posts
Re: Claude Code – Everything you can configure that the docs don't tell you
#2What’s up with scrolling on that page?! I was locked into a page region several times until I finally gave up. Safari/Orion iOS current
Re: Claude Code – Everything you can configure that the docs don't tell you
#3That example classifier is horrendous. A simple substring search for ls/cat/echo/etc?
Re: Claude Code – Everything you can configure that the docs don't tell you
#4Related from then:
The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
Re: Claude Code – Everything you can configure that the docs don't tell you
#5What’s up with scrolling on that page?! I was locked into a page region several times until I finally gave up. Safari/Orion iOS current
Maybe programmed with Claude Code?
Re: Claude Code – Everything you can configure that the docs don't tell you
#6claude package has ten new versions published per week, and one new model every few months, one should definitely not rely on some undocumented tricks around it: it'll change, it'll break deep ultra-specific configurations
Re: Claude Code – Everything you can configure that the docs don't tell you
#7claude package has ten new versions published per week, and one new model every few months, one should definitely not rely on some undocumented tricks around it: it'll change, it'll break deep ultra-specific configurations
in my experience, "undocumented tricks" break as often as documented features
like when they removed "clear context and execute plan" option after releasing 1M opus because "context window is not a problem anymore"
Re: Claude Code – Everything you can configure that the docs don't tell you
#8claude package has ten new versions published per week, and one new model every few months, one should definitely not rely on some undocumented tricks around it: it'll change, it'll break deep ultra-specific configurations
in my experience, "undocumented tricks" break as often as documented features like when they removed "clear context and execute plan" option after releasing 1M opus because "context window is not a problem anymore"
I so miss that clear context and execute plan mode! Now i have to keep clearing it manually again.
Re: Claude Code – Everything you can configure that the docs don't tell you
#9Some of these things are documented. For example the model in frontmatter in skills is documented here: https://code.claude.com/docs/en/skills#frontmatter-reference
(It's not easy to find though, and lots of other docs doesn't mention it or link to this)
Re: Claude Code – Everything you can configure that the docs don't tell you
#10claude package has ten new versions published per week, and one new model every few months, one should definitely not rely on some undocumented tricks around it: it'll change, it'll break deep ultra-specific configurations
This is true, but also "temporal hacks" can make or break "cutting edge" workflows. I don't re-architect my claude instructions every release. But some releases justify examining your existing instructions and making sure they still fit the current model. And it has made a noticeable difference.