i) Who am I? ii) What is our design philosophy and tenets? iii) Go through the repo and ensure the architecture and codebase adheres to our design philosophy and tenets.
I also use similar questions for different situations, and different ones for different projects. So, to avoid writing these questions every time, I created commands for each question.
There is also a "/capture" command that analyzes the dialogue and suggests what to save from it, what commands and rules to create.
The "/insights" command not only analyzes the current dialogue, but also suggests ideas for creating new commands and rules.
If you have asked the same question several times in the dialogue, these commands will suggest creating new commands specifically for these questions.
Comments
I also use similar questions for different situations, and different ones for different projects. So, to avoid writing these questions every time, I created commands for each question. There is also a "/capture" command that analyzes the dialogue and suggests what to save from it, what commands and rules to create. The "/insights" command not only analyzes the current dialogue, but also suggests ideas for creating new commands and rules. If you have asked the same question several times in the dialogue, these commands will suggest creating new commands specifically for these questions.