@ddd1345 , you’re right that user-defined rules can’t override Cursor’s built-in instructions at the architectural level. The workarounds I mentioned can help models prioritize your directives in practice, but they don’t change the underlying hierarchy, which is the core issue for your workflow.
Your two proposals (a user-accessible system prompt layer at the same priority level, or the option to disable built-in instructions) are clear and specific. Others have described similar needs — this feature request covers the same ground.
We’re noting your feedback and passing it on to the relevant team for consideration.