Yet Another Yolo Is Amazing Post
My problem with YOLO is that I have Shiny_Object_Deficiency_Syndrome – So I get extrmely distracted in the middle of any Composer sessions and wind up branching into various offshoot from original project, and start building three things in parallel.
–
So that you’re seeing my YOLO doing, is its taking this prompt:
And doing:
This is WONDERFULLY FUN and fullfilling.
I am creating a central repo of the tooling I have it create - so I can start using a library from a repo as my toolbelt for various things and have all the composers pull from it and update the DB for the directory of Called the “Aipyri”…
I want to submit .currsor rules into the db, and tell it what rules set to use in the .env.
I am making a bot do a complete project setup - and so Im building a bunch of project setup infra…
Is anyone else doing similar? What are your thoughts on best practice - are there tools already built that one may share here?
I am going to have SpecStory @gregce keep a running prompt db - where it will dump specstories into postgress and uuid the comments and then I will have the composer bots ingest the Composer Convos in as I go to refine my overall workflow and history and catalog of aircanery.
Anyway - just wanted to share my enthusiasm.