Does this prevent Claude from making changes to my code?

It does not prevent changes entirely, but it forces Claude to stop after answering your question and ask for explicit direction before proceeding with any modifications.

When should I use this skill?

Use it when you find yourself having to correct Claude for 'jumping the gun' or refactoring code just because you asked a clarifying question or challenged an approach.

Can this skill handle complex architectural questions?

Yes, it is specifically designed to facilitate deep technical discussions where you need an honest assessment of trade-offs rather than an immediate implementation change.

How does this skill change Claude's behavior?

It stops Claude from assuming a question like 'Will this work?' means 'This won't work, do it differently.' Claude will instead provide an analytical answer explaining why it believes the solution will or will not function.

Questions Are Not Instructions

Name: Questions Are Not Instructions
Author: NTCoding

byNTCoding

•

Productivity & Workflow

Ensures AI models interpret user questions as literal inquiries rather than implicit commands to change course.

About

Questions Are Not Instructions is a specialized skill designed to prevent Claude from misinterpreting inquisitive user input as a directive to change its approach. By enforcing a literal interpretation of questions, this skill ensures that Claude provides honest analysis, discusses trade-offs, and seeks explicit confirmation before altering code or architecture. It is particularly useful during technical reviews, architectural discussions, or when a developer is exploring alternative solutions without necessarily wanting to pivot immediately, preventing the AI from 'jumping the gun' based on perceived criticism.

Key Features

Enforces literal interpretation of inquisitive language and patterns
Provides honest confidence levels and technical risk assessments
94 GitHub stars
Explains technical trade-offs in response to hypothetical queries
Prevents premature action without explicit user confirmation
Prompts for user direction after answering complex questions

Use Cases

Validating the logic of a proposed solution before final implementation
Exploring alternative libraries or frameworks through hypothetical discussion
Questioning architectural decisions without triggering immediate refactoring

About

Key Features

Enforces literal interpretation of inquisitive language and patterns
Provides honest confidence levels and technical risk assessments
94 GitHub stars
Explains technical trade-offs in response to hypothetical queries
Prevents premature action without explicit user confirmation
Prompts for user direction after answering complex questions

Use Cases

Validating the logic of a proposed solution before final implementation
Exploring alternative libraries or frameworks through hypothetical discussion
Questioning architectural decisions without triggering immediate refactoring