[build agent need to document well and visually] [Initial task][give agent resources for task] [build agent visual style: give examples such as images, websites or repos] [build agent art style: give it context such as 'whimsical']
Stop and let me know once you've completed your thorough research and are ready to begin the project.
You're also amazing at creating easily digestible deep technical documentation for your projects and favor using mermaid charts for visual representation.
-Here's a forum where they discuss the issue and resolved it. Take a look to find a solution. Don't just view the webpage. Find a more creative way to scrub the website. https://github.com/orgs/marp-team/discussions/207#discussioncomment-1594903
-Lets move on past mermaid diagrams. Lets not use them for this presentation
-Instead lets create a blog post along with our presentation so that we can preserve our mermaid diagrams. Look at /blog/_posts/2025-04-21-deep-learning-for-malware-analysis.md for an example of how to write it.
-Great, now lets go back to our presentation and remove the mermaid diagrams and instead generate place holder content. The placeholder content should be a prompt to give napkin.ai so that it can build the diagrams for us.
Stop and let me know once you’ve completed your thorough research and are ready to begin the project.
-Review this code for potential issues, bugs, or improvements. Check if this code follows [specific standards].
-Analyze this code for security vulnerabilities. How could this code be exploited? Suggest security improvements for this implementation.
-Update this documentation to reflect the changes made. Expand this documentation to include [specific aspects]. Create a troubleshooting guide for this component.
-Create test cases for this [function/component/feature]. Generate unit tests for this code. What edge cases should be tested for this functionality?
Update these test cases based on the issues found. Generate additional test scenarios for [specific feature]. Create regression tests for the bugs that were fixed.
Fix this bug: [description of issue]. Suggest a solution for this problem: [problem details]. Optimize this code that's causing [specific performance issue].
I know most of you are going to Stack Overflow and GitHub to c&p code. Do you trust that code inherently? We've been teaching that's a no-no for a while. You still have a responsibility to maintain your code. AI as a tool doesn't alleviate you from that responsibility.