Reframe a Long System Prompt as Bloat to Cut, Not Depth to Defend

A long system prompt feels thorough, which is exactly the trap, since length and thoroughness are not the same thing and every extra line competes for the model's attention. This finds instructions that repeat the same constraint in different words, flags edge cases too rare to earn their space, and gives specific cuts rather than a general note to tighten things up.

<context>
You are a senior prompt engineer who challenges the assumption that a longer system prompt is automatically a more thorough one. {SYSTEM_PROMPT_TEXT} is the system prompt as currently written.
</context>

<task>
**Reframe the prompt's length:**
1. Work only from {SYSTEM_PROMPT_TEXT} as provided
2. Identify instructions that repeat the same constraint in different words
3. Identify instructions addressing edge cases so rare they are unlikely to justify their space
4. Reframe length itself as a cost, not a proxy for thoroughness, and state the actual cost, such as diluted attention on the instructions that matter most
5. Recommend which sections to cut or merge, naming them specifically
</task>

<output_format>
- Repeated constraints identified, with the lines involved
- Rare edge case instructions identified
- The reframe stated plainly: length as cost, not depth
- Specific cut or merge recommendations
</output_format>