docs: add CONTRIBUTING.md and AGENTS.md (#134)

* docs: add CONTRIBUTING.md and AGENTS.md

Add contribution guidelines covering conventional commits, issue references,
visual evidence for changes, draft PR workflow, and code quality standards.
Add AGENTS.md to ensure AI tools follow contribution guidelines.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

* docs: improve CONTRIBUTING.md structure and link from README

- Reorganize CONTRIBUTING.md with clearer section structure
- Add Contributing section to README.md linking to CONTRIBUTING.md
- List key contribution topics (commit conventions, PR workflow, code quality)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

* Slight readme updates

---------

Co-authored-by: Claude <[email protected]>

Author: BigLep

AGENTS.md

@@ -0,0 +1,10 @@
+# AI Agent Guidelines
+
+When using AI agents (such as Claude Code, Cursor, or similar tools) to contribute to this project, please ensure the agent follows all guidelines outlined in [CONTRIBUTING.md](./CONTRIBUTING.md).
+
+This includes:
+- Using conventional commits
+- Referencing GitHub issues in PRs
+- Including visual evidence for user-facing changes
+- Keeping PRs in draft until ready for review
+- Writing concise, self-documenting code

CONTRIBUTING.md

@@ -0,0 +1,36 @@
+# Contributing to filecoin-pin
+
+Thank you for your interest in contributing! Please follow these guidelines when submitting changes.
+
+## Use Conventional Commits
+
+All commits, especially PR titles, should follow the [Conventional Commits](https://www.conventionalcommits.org/) specification:
+
+- `feat:` - New features
+- `fix:` - Bug fixes
+- `docs:` - Documentation changes
+- `chore:` - Maintenance tasks
+- `refactor:` - Code refactoring
+- `test:` - Test additions or changes
+- `ci:` - CI/CD changes
+
+Example: `feat: add support for batch uploads`
+
+## Reference GitHub Issues
+
+Always reference the related GitHub issue in your PR description using keywords like `Fixes #123` or `Closes #456`.
+
+### Include Visual Evidence
+
+For user-facing changes or CLI flows, include:
+- Screenshots for UI changes
+- Terminal output for CLI commands
+- Before/after comparisons when relevant
+
+## Draft PRs
+
+Leave your PR in draft status until it's ready for maintainer review. This helps maintainers prioritize their time.
+
+## Code Quality
+
+Keep comments concise and favor self-documenting code when possible. Use clear variable names, function names, and code structure to make your intent obvious.

README.md

@@ -203,6 +203,10 @@ npm run lint:fix         # Fix formatting
 
 ## Community and Support
 
+### Contributing
+
+Interested in contributing? Please read our [Contributing Guidelines](CONTRIBUTING.md) for information on commit conventions, PR workflows, etc.
+
 ### Get Help
 
 - **Issues**: Found a bug or have a feature request? [Open an issue](https://github.com/filecoin-project/filecoin-pin/issues) in this repository