oracle-prompt-design

Designing Oracle prompts for code review requires defining project context, framing specific questions, and establishing evidence attachment logic. This structured approach ensures contextual relevance and efficient validation by providing the necessary code and debugging data.

When designing a prompt for design critique, include files that provide direct evidence for the question asked while excluding irrelevant data. Proper attachment management ensures the review process remains efficient and focused on the specific design context.

Yes, this approach structures prompts specifically for second-model validation by ensuring contextual relevance and structured data attachments. It guides you through defining project context and evidence attachment logic for effective automated validation.

Yes, providing user-defined project context is required before generating a prompt. The prompt design process depends on user-defined project context, specific question framing, and evidence attachment logic to ensure precise and contextually relevant automated reviews.

The best way to structure prompts for debugging complex code is to attach relevant evidence files and frame specific questions within the broader project context. This structured data attachment ensures the review model receives the precise information needed for effective debugging.