Course demonstrating bringing systems together #17
Description
Is your course suggestion related to a problem? Please describe.
I'm doing a little mapping from experiences with other tools (as a user this space and making professional developer tools in other spaces), but a really common challenge that I've seen happens in the following scenario:
You've done the tutorials, you've read the docs, you've reviewed the code -- you can build a prompt task agent, and tookit agent, a pipeline, custom tools. And the pieces make sense -- you're a competent user. But now you want to put these pieces together into something where there is some flow control and logic around them... make them all work together. At this point, specific needs tend to be very application-specific, so there usually aren't any tutorials. But that is unfortunate because now you need to start making your own design decisions at sort of a macro level and you have no guidance.
My observation is that there are usually ways to approach this application-specific integration layer that have good synergy with your tools and ways that will result in a constant fight and struggle against them. And that a lot of community/user pain comes from people going with the latter -- and that it keeps happening until there is enough critical mass in the user base that people start publishing a lot of tutorials and sharing best practices and teaching courses on your software at university.
Describe the course you'd like
I think it could be something simple. Maybe start with the Kiwi Chat Agent and add a Toolkit Agent that can respond with data about something (maybe there is something thematically relevant that could be pulled from the web -- All Blacks team stats, New Zealand economic data, idk). But show how you could build a system where you chat with the chat agent in a free-form way, but supplement that chat with the data from the other agent. Almost any real-world case is going to much more complex and maybe if this were all you were going to do, you're sort of over-engineering for the result. But you would demonstrate how to have systems communicating under-the-hood while providing the end-user with a cohesive experience. Most importantly for learning, the project would act as a framework to discuss the sort of design-thinking that a Griptape user would have when approaching their own application — it acts as a means to communicate best-practice as they apply to that more abstract design.