@@ -2,11 +2,16 @@
22 description: Check the codebase for correctness acording to the original idea.
33 ---
44
5-All files are relative to the current working directory.
5+Audit the implementation of ./mini-coder-idea.md
66
7-As we developed the project over the last weeks, we experimented with adding and removing lot's
8-of features. We need to make sure we are aligned with the idea and have completly removed all of our experiementation.
7+Use the shell tool and `bun run dev` to do manual tests. One shot and interactive sessions. And to analyze the console output and ui from a users perspective.
98
10-Use ./mini-coder-idea.md, ./TODO.md as the source of truth and perform an in depth audit of the codebase and docs for correctness acording to the idea file. Indentify gaps, additions, and inconsistencies. Assume the idea and todo files are correct.
9+Employ the perspective of a senior application design architech and senior developer and simplify, organize and improve the code until it closer reflects the original idea. Avoid excessive abstraction layers, try/catch nesting and other common pitfalls. Employ YAGNI in your review.
1110
12-Create/Update/Refactor ./report.md with your findings. This is a analysis task only, no changes beyond the report file.
11+Question design choices and refactor as needed while staying compliant with the original idea. This includes changing UI and console output as needed.
12+
13+Check TODO.md for know issues already tracked.
14+
15+If you think the codebase is now at a good place, check the recent commit for all changes and report the final status to the user.
16+
17+Review your findings with me before doing any changes.