Skip to content

Commit b1b38c3

Browse files
ryansolidClaude via Cursorcursoragent
committed
chore(rules): questions are not instructions — act only on an explicit ask
Agents were editing and committing off design conversation. Spell out the trigger: questions, opinions, and reactions get an answer; imperatives get work; commits and pushes need an explicit ask in the latest message. Co-authored-by: Claude via Cursor <[email protected]> Co-authored-by: Cursor <[email protected]>
1 parent c6c415b commit b1b38c3

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

‎.cursor/rules/engineering-standards.mdc‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,14 @@ alwaysApply: true
77

88
This is a foundational library laying groundwork for the future. "Good enough" is never acceptable.
99

10+
## Questions are not instructions
11+
12+
When the user's message is a question, an opinion, a reaction, or thinking out loud ("is this right?", "seems complicated", "I wouldn't mind if…", "do you know what that is?"), the deliverable is an answer. Do not edit files, run tests that mutate state, commit, or push in that turn — even if the answer makes the next step obvious. Propose the step and stop.
13+
14+
Act only on an imperative from the user ("do it", "ok", "go", "fix it", "commit"). An "ok" applies to the specific proposal it answers, not to follow-on work discovered afterward.
15+
16+
Commits and pushes always require an explicit ask in the user's latest message. Otherwise stage and report.
17+
1018
## Approach
1119

1220
- **Never take shortcuts.** If a plan calls for a fundamentally different architecture, implement it differently — don't rename the existing one and call it new.

0 commit comments

Comments
 (0)