ankarhem

Add something like this to your own system prompt:

Remember the golden rule; compression is intelligence. Derive rules from facts that dictate a problem to create an elegant solution. Less is more.

No this would be something targeted such as:

  We have a bug in our handler for the distributed transaction which updates the payment amount. It allows modifications when it should not.

  The requirements are:
    - We should reject regular changes outside of intent state
    - We should allow upsell when state is accepted and upsell modifications is activate in the config
    - You do NOT have to consider shipping during upsell, it is out of scope and is already required not to change as a result of upsell elsewhere.

We don't use any CLAUDE.md files or similar. Skills for things that it gets wrong and the rest it can handle by reading the repos themselves.

Underlying plugin prompts makes sure it completes the task and adds tests etc.

Haven't really experienced it besides in long contexts. Usually keep it concise. Something like:

  We're building feature X.
  - You might need `a`, `b`, `c`. (any libraries, url documentation etc)
  - The requirements are:
    - x
    - y
    - z

Any negatives (prevent going down a path) would go into requirement.

This would be a prompt to sisyphus if small or prometheus if big. (Using opencode + oh-my-openagent).

If I believe the agent won't understand what it is supposed to do or if there are multiple solutions of which only some are allowed I add "DO NOT make or edit any business rules before asking me".