# Contributing

Thanks for considering a contribution! This course gets better when learners share what worked for them.

## Easy ways to help

- 🐛 **Fix a typo or broken link** — open a PR directly
- 💡 **Suggest a better example** — open an issue first, then PR
- 📚 **Add a "real-world prompt"** to the [prompt cookbook](./09-resources/prompt-cookbook.md)
- 🌍 **Translate a module** — open an issue so we can coordinate
- 🛠️ **Add a new project** to Module 08 — keep it under ~150 lines, with clear setup

## Style guidelines

- **Be concrete.** Show, don't tell. Real prompts > generic advice.
- **Be honest.** Note tradeoffs and limits, not just the happy path.
- **Date-sensitive content.** If you reference a specific model version or price, link to the official source so future readers can verify.
- **Code must run.** Every code example should work as written, with the documented setup.

## How to submit a PR

1. Fork the repo
2. Create a branch: `git checkout -b fix-typo-module-3`
3. Make your change
4. Commit with a clear message: `git commit -m "Fix typo in module 3 XML example"`
5. Push and open a PR against `main`

For substantial additions, open an issue first so we can discuss direction before you spend time writing.

## Code of Conduct

Be kind. Disagree with ideas, not people. We're all learning.

This project is governed by the [Code of Conduct](./CODE_OF_CONDUCT.md). By participating, you agree to uphold it.