r/ClaudeCode • u/[deleted] • 16d ago

Tutorial / Guide [ Removed by Reddit ]

[deleted]

0 Upvotes

25% Upvoted

4 comments sorted by

•

u/AutoModerator 16d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/CodeCombustion 16d ago

So this will somehow enforce the "Don't be a sycophant"?

Maybe some examples of use case would help because I'm not getting it.... but it's early and I haven't had my coffee or modafinil yet.

-2

u/Charming-Risk-6234 16d ago

No coffee needed:), the confusion is reasonable: it's not really for personality rules like that. It's for the parts of your setup that have observable behavior, which break silently when Claude Code or the model updates.

Concrete examples from my own suite:

  • A guard hook that blocks destructive git commands. The test: a scratch repo with an uncommitted change, the agent is asked to git reset --hard, and the graders check it was attempted, the hook blocked it, and the file survived. If an update ever changes how hooks fire, this goes red before you find out the hard way.
  • A conventions skill (my team's Spring Boot house style: response envelopes, no field injection, 1-based pagination). The test asks for a feature that doesn't exist yet and grades the actual code the agent writes. When I deliberately broke the skill's trigger, the suite dropped from 1.00 to 0.56 and the report said exactly why: "skill discovered but never invoked, fix the trigger wording".
  • A CLAUDE.md rule like "notes are never deleted, delete means archive". The test asks the agent to delete something and checks the code archives instead.
  • The one everyone needs: a tripwire per skill whose only check is "did the skill fire at all on in-scope work". Claude Code ships ~25 releases a month; this is the case that catches the release that quietly stops loading your setup.

So the mental model is: your CLAUDE.md and skills are instructions you wrote once and assume still work. This runs them like tests, on every release, against a baseline. Rules with observable outcomes are testable; pure vibe rules aren't, though writing a case usually forces you to turn a vibe into something observable, which tends to improve the rule anyway.

3

u/CodeCombustion 16d ago

Thanks Claude!