← Back to context

Comment by ivan_gammel

3 hours ago

I have instructions to combine style of Brooks, Steven King and Economist Style Guide, while avoiding anything that may put wrong emphasis („genuinely“, „load-bearing“) does not contribute anything meaningful („X rather than Y“). The output is quite good* so far even on Opus 4.7-5, when it concerns product requirements. The key is to identify the pattern and focus on the meaning of the undesirable language.

* chemistry + regulations + infosec domains

I've tried controlling it via fine-tuning Claude.md and in-session messages/instructions. It always results in failure and then "Yes, guardrails are already there. I still failed" and it feels like "I am like this. Deal with it". I've even tried languages that avoids negatives e.g. "Don't.." "never.." etc. Nope. Just doesn't work.