Which document?
Other
If a SKILL.md — which skill?
No response
Which section?
No response
Type of issue
Missing information — a gap that leaves a reader without an answer
What is wrong or missing?
This is a very elegant coding assistant system, kudos!
I would hover created this as a discussion topic but that is not working in this project.
I have a bunch of existing projects with PRDs, often broken down into more formal specs.
Before this project I had not heard of “Clean Architecture”. From context, I assume it is formal system rather than just a judgement call :) To that end, I think it would be beneficial to link to resources on this.
Similarly this project talks about domains and layers, but assumes the reader has a nuanced understanding of these terms. Of course you can’t explain everything, but referencing the models you are working from can be inviting and help people align quickly.
So back to my existing projects, I see how this can be configured to fit in with my project standards very cleanly. However, I’m unclear how I could migrate my existing collection of PRDs, specs and tests to create context files in this system.
Q1: I’m curious how you would perform a context migration to lattice?
I suspect my specs are the right thing to convert to context, however these are organized by category rather than feature. My categories have variable levels of decomposition, I tend to focus on a spec for a category being less than about 300 lines, so when they get larger I tend to split them along natural (to me) areas of focus. If I’m adding a feature that affects several categories, I might just add a new feature that is cross cutting or I might reorganize existing specs to accommodate the new complexity.
Q2: I’m curious how lattice handles (or should handle) both the inherent complexity when a feature (or enhancement) affects multiple contexts?
Q3: And, how lattice handles (or should handle) tasks related to maintenance (reorganizzation) of the context store?
What should it say instead?
No response
Which document?
Other
If a SKILL.md — which skill?
No response
Which section?
No response
Type of issue
Missing information — a gap that leaves a reader without an answer
What is wrong or missing?
This is a very elegant coding assistant system, kudos!
I would hover created this as a discussion topic but that is not working in this project.
I have a bunch of existing projects with PRDs, often broken down into more formal specs.
Before this project I had not heard of “Clean Architecture”. From context, I assume it is formal system rather than just a judgement call :) To that end, I think it would be beneficial to link to resources on this.
Similarly this project talks about domains and layers, but assumes the reader has a nuanced understanding of these terms. Of course you can’t explain everything, but referencing the models you are working from can be inviting and help people align quickly.
So back to my existing projects, I see how this can be configured to fit in with my project standards very cleanly. However, I’m unclear how I could migrate my existing collection of PRDs, specs and tests to create context files in this system.
Q1: I’m curious how you would perform a context migration to lattice?
I suspect my specs are the right thing to convert to context, however these are organized by category rather than feature. My categories have variable levels of decomposition, I tend to focus on a spec for a category being less than about 300 lines, so when they get larger I tend to split them along natural (to me) areas of focus. If I’m adding a feature that affects several categories, I might just add a new feature that is cross cutting or I might reorganize existing specs to accommodate the new complexity.
Q2: I’m curious how lattice handles (or should handle) both the inherent complexity when a feature (or enhancement) affects multiple contexts?
Q3: And, how lattice handles (or should handle) tasks related to maintenance (reorganizzation) of the context store?
What should it say instead?
No response