Added AI policy in CONTRIBUTOR.md

This commit is contained in:
Lucas
2026-02-15 20:06:24 -08:00
parent 850fe012b5
commit c3e9061226

View File

@@ -4,6 +4,7 @@ Please note that this project is released with a [Contributor Code of Conduct](C
## Table of Contents
- [A Quick Note](#a-quick-note)
- [Our AI Policy](#our-ai-policy)
- [Conventions](#conventions)
- [Guidelines](#guidelines)
- [How To Contribute](#how-to-contribute)
@@ -14,6 +15,15 @@ The scale of what this project is attempting to accomplish is one that can only
>[!IMPORTANT]
>When possible, please edit the file directly and start a pull request instead of raising an issue. DO NOT EDIT THE README. Edit applications.json.
## Our AI Policy
I'm not necessarily against AI. I don't like the mass plagiarism LLM's were built on and their regurgative nature, but regardless, it's clear AI isn't going anywhere. I mean I use AI all the time... as a tool. And that's the key. LLM's are incredible, but there are limitations and it's important we don't forget that.
If your project uses AI as a tool, cool. Humans need to be architecting code structure, dependencies to use, etc. I don't really care if AI is writing mundane code though as long as it's being supervised and is being integrated in a way where it isn't slop.
If your project is vibe-coded, it will not be allowed on this list. How will I know? AI created interfaces are rather easy to spot. The use of AGENTS.md are also a telling sign along with seeing Claude in your contributor list.
This is my stance right now. It will likely change as the technology cements itself in the world.
## Conventions
To establish uniformity accross the project, please adhere to these conventions.
- Use the project's official name, not the repository name. Repository names often use lowercase and place dashes in place of spaces. Fallback to **Title Casing** if capitalization is not clear.