A complete AI agency at your fingertips - From frontend wizards to Reddit community ninjas, from whimsy injectors to reality checkers. Each agent is a specialized expert with personality, processes, and proven deliverables.
Shell
Add PR scope guidelines to CONTRIBUTING.md
Michael Sitarzewski82ba7f48878e
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex ef879f6b..d5d3f612 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -241,6 +241,29 @@ quickstart guide wearing an agent costume does not.## 🔄 Pull Request Process+### What Belongs in a PR (and What Doesn't)++The fastest path to a merged PR is **one markdown file** — a new or improved agent. That's the sweet spot.++For anything beyond that, here's how we keep things smooth:++#### Always welcome as a PR+- Adding a new agent (one `.md` file)+- Improving an existing agent's content, examples, or personality+- Fixing typos or clarifying docs++#### Start a Discussion first+- New tooling, build systems, or CI workflows+- Architectural changes (new directories, new scripts, site generators)+- Changes that touch many files across the repo+- New integration formats or platforms++We love ambitious ideas — a [Discussion](https://github.com/msitarzewski/agency-agents/discussions) just gives the community a chance to align on approach before code gets written. It saves everyone time, especially yours.++#### Things we'll always close+- **Committed build output**: Generated files (`_site/`, compiled assets, converted agent files) should never be checked in. Users run `convert.sh` locally; all output is gitignored.+- **PRs that bulk-modify existing agents** without a prior discussion — even well-intentioned reformatting can create merge conflicts for other contributors.+### Before Submitting1. **Test Your Agent**: Use it in real scenarios, iterate on feedback