Python rulebook - #7
Open
jasonbrazeal wants to merge 14 commits into
Open
Conversation
…ief + plan; brief is good, plan is not, will redo
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In addition to the rulebook, there are 2 intermediate docs in chats/, a research brief and a plan. I iterated on the plan quite a bit but regenerated the rulebook from it fresh each time.
I used the prompt rulebook extensively but there are a few things that I am pushing back on:
Reserve NEVER, ALWAYS, and MUST for invariants... and cap them at three per target
[Great advice in general, but these are very natural for a rulebook and will appear many times]
Binding meta-rule: consistency within an existing project outranks every style rule in this rulebook
[Good idea for most prompts, but the rulebook addresses this differently, being a set of rules itself]
Strip provenance from every emitted artifact: state the rule, name no source document for it.
[Sources for programming language rulebooks are a handful of websites (language documentation, library documentation, standards, etc.). The rulebook is supposed to distill all of that into a compact format, so of course agents reading it will need to look up finer points. I want to direct them to the canonical sources instead of having them search randomly.]
Also I found that it would copy the existing rulebook WAY too much, like word for word in some sections, even without me asking it to read those files. I deleted them all while I was working on this to prevent that.