3 ms·
+1 on all of this, it is similar to the pattern I see emerging as well. For example I have open-sourced (let's be honest, it's just my personal tooling of taste
by woud420 26d ago
+1 on all of this, it is similar to the pattern I see emerging as well. For example I have open-sourced (let's be honest, it's just my personal tooling of taste) a repo on gh to try and formalize these things. I'd rather not share out of mostly imposter syndrome but essentially it's a scaffolding tool ala "create-react-app" for the stack I generally use.
Part of that is to create standardized "docs/{architecture, decisions, contracts, operations}" folders that my harness recognizes in my repos to have a better sense of where was it.
Glad others are converging towards similar ideas!
- verdverm 26d agoI was solving your problem.before LLMs with my personal developers Swiss army knife (hof gen/CUE+templates). I'm somewhat keen to see how I can capture the agent markdown I want in many places, like project init, in CUE via embed and modules I can import and version, skipping the need for a markdown dependency cycle management system. https://github.com/hofstadter-io/hof https://github.com/hofstadter-io/hof (sharing because it has sloppy parts and that/I.S. shouldn't stop you from sharing!)