Repository navigation
docs(AI): Implement a formal AI policy - #15
Merged
Merged
Conversation
mOctave
added
documentation
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.
Documentation / Policy
This PR addresses the issue of vibecoding.
Checklist
Summary
This PR adds a much fuller and slightly more permissive AI Policy that can also be accessed through a symlink at AGENTS.md to make it enforceable for contributors using AI agents.
Usage examples
Automatic. Try to prompt an AI agent to make stuff and it should refer you to the AI policy and refuse to make changes. Try to ask it for help understanding stuff and it should explain it.
Testing
Tested with Cursor, seemed to respect it mostly.
Performance Impact
N/A