-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teach Wasp AI to use Wasp starter templates (or parts of them) #1943
Comments
Mention of it here: #1420 (comment) . |
suggestion (as a follow up to the other thread) : Maybe the way to go would be to expose some specific endpoints and create an ecosystem for users to pre-build components on the basis of a (compatible - strict) given scheme, after testing the pre-builds, could go into a structured prompt that inserts them into the architecture leaving the ai to deal with only the moving parts. IMHO the best use for the AI is to change the interface and generate images, whereas we should leave anything development as modular as possible so to leverage form the existing wasp framework? |
@cocobeach I think I get what you mean! We would ideally have an ecosystem of "building blocks" that then AI could use to build the codebase. |
Well it's funny you should mention that, I have been looking at 2 frameworks lately, both quite promising and departing from the usual UI of the "devins".
|
BTW I love the wasp studio for visualisation and it gave me an idea related to the building blocks above: From what I understand creating an opensaas, as an example of top level wasp-app, gives the ability to create from within the opensaas application a nested wasp:new application, correct? |
Ok this is a wild idea :D! I am not sure I am picking it up completely: you are suggesting we make a new Wasp app (potentially using open-saas) that is basically a visual editor where you can create Wasp apps by choosing building blocks and connecting them together? If so, yeah that makes sense! A visual builder for Wasp apps. This is something that could indeed be monetized likely, and makes sense as one of the steps to take in the (a bit further) future! |
Pretty much yes, why reinventing then wheel and build another interface when you app builds interfaces automatically and is already modular, second leg would be: why having the AI build a simple script with barely nothing in it, when it can start on the basis of an already existing SAAS? Let me know if you want me to alpha test something for you. |
*I sent you a DM on discord to show you what I am doing and how we could tie up both things together. |
It would be a big deal if Wasp AI (Mage) could use the starting templates, for example using open-saas. Or parts of those. Right now, it has its own very basic starting template it uses and it relies on it. Using other templates would require a change in how Mage works, so this could be quite an undertaking, since this part is now quite hardcoded.
The text was updated successfully, but these errors were encountered: