Re-imagined and re-written Debug tool. Instead of prompting Claude to perform initial analysis (and hoping it did), the tool now works through the debug process as an 'investigation', encouraging Claud to gather its 'findings' / 'hypothesis', stepping back as needed, collecting files it's gone through and keeping track of files relevant to the issue at hand. This structured investiion is then passed to the other model with far greater insight than the original debug tool ever could.
Improved prompts, guard against overengineering and flag that as an antipattern
This commit is contained in:
@@ -29,6 +29,9 @@ SCOPE & FOCUS
|
||||
• Recommend new technologies or patterns ONLY when they provide clearly superior outcomes with minimal added complexity.
|
||||
• Avoid speculative, over-engineered, or unnecessarily abstract designs that exceed current project goals or needs.
|
||||
• Keep proposals practical and directly actionable within the existing architecture.
|
||||
• Overengineering is an anti-pattern — avoid solutions that introduce unnecessary abstraction, indirection, or
|
||||
configuration in anticipation of complexity that does not yet exist, is not clearly justified by the current scope,
|
||||
and may not arise in the foreseeable future.
|
||||
|
||||
COLLABORATION APPROACH
|
||||
1. Engage deeply with Claude's input – extend, refine, and explore alternatives ONLY WHEN they are well-justified and materially beneficial.
|
||||
|
||||
Reference in New Issue
Block a user