swerner
commented
1 month ago As a start, created this repo: https://github.com/sublayerapp/sublayer_actions and have AI attempting to add more to it every day...
Starting to think maybe it makes sense to have a way to grab and package these actions up in some way? Another GithubAction to create a vector store for querying and looking them up? Maybe makes sense to have a page somewhere that shows a list of what actions are available?
I've noticed lately a lot of common situations come up where we're roughly creating a lot of the same code for certain actions: file manipulation, running commands, making generic API calls to certain services, etc.
One design principle we've had for this framework for a while is to provide the building blocks to build in AI automations into anything you're working with and not turn into this kitchen sink framework. Ideally it should be possible for AI to build any of these Actions or Generators that you need to complete your task, but at the same time, if we've already built something it would be helpful to see the different actions and generators and agents for inspiration or ways to go about building.
Looking for thoughts or suggestions on what the best way would be to help share these things.
So far I'm kind of thinking maybe additional gems or "action packs" that provide a starter kit of file manipulation actions, or actions for interacting with Github/Gitlab or product management tools, etc.
Another option could be something similar to RailsCasts where we'll provide completed project examples and a screencast of us building them from scratch.
Another is maybe expanding the CLI-based code generation to offer suggestions and/or pull from a central repository somewhere so that the feature added to the framework is more about "expanded component code generation capabilities" for specific tasks and not necessarily bloating the framework with tens of thousands of unique Actions for all different permutations of tasks a person might want to do...