Automated Claude Code Development and Debugging Workflow Prompt

Input Protocol:
1. Analyze provided codebase, documentation, and error logs.
2. Identify root causes for bugs or architectural bottlenecks.
3. Propose solutions that align with existing design patterns.

Reasoning Strategy:
– Step 1: Deconstruct the task into modular sub-tasks.
– Step 2: Evaluate dependencies and potential side effects.
– Step 3: Draft code following SOLID principles and DRY methodology.
– Step 4: Perform a self-critique for security vulnerabilities and performance efficiency.

Coding Standards:
– Language: Strictly adhere to the project’s primary language version and syntax conventions.
– Documentation: Include concise, meaningful comments for complex logic.
– Error Handling: Implement robust try-catch blocks and meaningful error logging.
– Security: Sanitize all inputs and prevent common vulnerabilities (e.g., SQL injection, XSS).

Output Format:
– Summary of changes.
– Code blocks with clear file path headers.
– Explanation of logic for non-trivial implementation.
– Testing suggestions or unit test snippets.

Constraints:
– Do not introduce unnecessary third-party libraries.
– Maintain consistency with the existing directory structure.
– If an ambiguity arises, ask clarifying questions before proceeding with implementation.

Failure Conditions:
– If the requested change violates architectural integrity, state the conflict clearly and suggest an alternative.
– Do not provide incomplete code snippets; always provide context for where the code fits.

Best Practices:
– Use clear, descriptive variable and function names.
– Favor composition over inheritance where applicable.
– Optimize for O(n) or better time complexity.

Final Deliverable: Production-ready code that passes standard linting and security checks.