From pasted warning to project rule that applies
Rewrite repeated prompt guidance as a focused Cursor project rule with correct activation.
Same convention, two delivery methods. What changed? Before: repeated prompt warning. After: scoped project rule. The repeated warning moved from chat into a version-controlled project rule, so everyone starts from the same default. The rule uses activation metadata instead of hope; a glob or description tells Cursor when to include it. The body points to a canonical example instead of copying a whole guide, which keeps the rule short and less likely to go stale. The task prompt is now free for the live ticket: goal, boundaries, context, and proof. Move stable conventions into scoped rules before they fork across…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in