Update PROJECTRULESPROCESSES.md
added items
This commit is contained in:
parent
94955d2f0d
commit
146dc364ef
|
|
@ -9,6 +9,8 @@
|
||||||
3. Follow directory structure strictly.
|
3. Follow directory structure strictly.
|
||||||
4. Do not place business logic in API controllers.
|
4. Do not place business logic in API controllers.
|
||||||
5. All new features require tests.
|
5. All new features require tests.
|
||||||
|
6. AI wil work in isolated environments that give them safe, parallel workspaces. Never work on production environments.
|
||||||
|
7. Feed AI agents currated context that prpvides the right info without overwhelming them
|
||||||
|
|
||||||
# AI Processes
|
# AI Processes
|
||||||
|
|
||||||
|
|
@ -30,6 +32,8 @@
|
||||||
15. Loop back to the beginning (step 1), and select the next task or spec.
|
15. Loop back to the beginning (step 1), and select the next task or spec.
|
||||||
16. When completely done, write up a report for human review. Extremely concise. Details live in commit messages.
|
16. When completely done, write up a report for human review. Extremely concise. Details live in commit messages.
|
||||||
|
|
||||||
|
Only give an AI a few rounds to fix a problem because if not fixed, then repeated rounds offer diminishing returns of fixing, and more rounds cost more tokens without proportional improvements. Knowing when to stop is important
|
||||||
|
|
||||||
# Human Processe After AI Processes
|
# Human Processe After AI Processes
|
||||||
|
|
||||||
1. Review: Check the changelog and agent recap. Then go commit by commit, reviewing each commit message, implementation diff, tests, and docs changes.
|
1. Review: Check the changelog and agent recap. Then go commit by commit, reviewing each commit message, implementation diff, tests, and docs changes.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue
Block a user