Merge pull request Expensify#85129 from Expensify/andrew-ai

Add AI Etiquette document

Author: roryabraham

contributingGuides/AI_ETIQUETTE.md

@@ -0,0 +1,44 @@
+# AI Etiquette
+
+AI is a great tool for drafting, searching, summarizing, and exploring. Humans must own judgment, accountability, and quality.
+
+---
+
+## You Own What You Post
+
+If you submit a message, pull request, comment, or code with AI assistance, you are fully accountable for it. Before posting anything AI helped produce, you should be able to explain it without AI's help and feel confident putting your name behind it.
+
+## Avoid AI Slop
+
+"AI slop" is AI generated content copied and pasted with minimal to no human review. Use AI for brainstorming, research, and drafting, but treat it as a starting point, not the final result. Add your own context and nuance before sharing.
+
+## Don't Trust AI Blindly
+
+AI confidently says things that sound correct but are wrong. Always verify claims against source material. It's your job to understand and validate any AI-generated information you act on or share.
+
+## When AI Isn't Enough
+
+If a task can be fully automated with no human review, it should be automated for everyone, not done manually with AI. Our [AI Reviewers](/contributingGuides/philosophies/AI-REVIEWER.md) are an example: they do a first pass on code review, but they don't replace human review. You should still apply your own judgment when reviewing code, writing updates, or making decisions.
+
+---
+
+## Best Practices
+
+### Don't
+
+- Paste AI output directly without adding your own value
+- Submit AI-generated code you haven't tested, debugged, and confirmed follows our [coding standards](./STYLE.md)
+- Submit AI-generated code you don't fully understand
+- Post poorly formatted AI output or long walls of text without distilling the key points
+- Blame AI for mistakes. The mistake is yours regardless of the source
+- Use AI to generate responses during live conversations instead of engaging directly
+
+### Do
+
+- Use AI to summarize, draft, research, and explore
+- Review and edit all AI output before sharing. Put it in your own voice and make sure it's accurate
+- Verify AI claims against source information
+- Review all AI-generated code and content before asking others to review it
+- Verify AI-written PR descriptions and add context needed to explain the change
+- Provide evidence of manual testing on PRs, especially when test steps were AI-generated
+- Invest time in learning to write effective prompts and recognize quality output

contributingGuides/CONTRIBUTING.md

@@ -211,6 +211,9 @@ This helps future investigators understand the history and current status of err
 ### Important note about JavaScript Style
 - Read our official [JavaScript and React style guide](https://github.com/Expensify/App/blob/main/contributingGuides/STYLE.md). Please refer to our Style Guide before asking for a review.
 
+### Using AI tools
+- If you use AI tools (Copilot, Cursor, ChatGPT, etc.) to help write code or PR descriptions, please read our [AI Etiquette guide](https://github.com/Expensify/App/blob/main/contributingGuides/AI_ETIQUETTE.md). You are accountable for all AI output you submit.
+
 ### For external agencies that Expensify partners with
 Follow all the above above steps and processes. When you find a job you'd like to work on:
 - Post “I’m from [agency], I’d like to work on this job”