Add comprehensive GitHub Copilot agent instructions

Author: mekarpeles

.github/agents/README.md

@@ -0,0 +1,81 @@
+# GitHub Copilot Agent Instructions
+
+This directory contains instructions and guidelines for GitHub Copilot agents working on Open Library tasks.
+
+## Files
+
+### [open-library-instructions.md](open-library-instructions.md)
+Comprehensive development instructions covering:
+- Repository structure and architecture
+- Initial setup and Docker configuration
+- Building assets (JS, CSS, Vue, Lit components)
+- Running tests (Python, JavaScript, i18n)
+- Linting and code quality checks
+- Internationalization (i18n) workflows
+- Development workflow best practices
+- Common troubleshooting scenarios
+- Full reference documentation
+
+**Use this file** for detailed, step-by-step guidance when working on Open Library tasks.
+
+### [quick-reference.md](quick-reference.md)
+Condensed quick reference guide with:
+- Essential commands at a glance
+- Common workflows
+- Typical issue solutions
+- Key file structure
+- Quick reminders
+
+**Use this file** for quick command lookups during development.
+
+## Purpose
+
+These instructions are designed to:
+1. **Reduce repeated work** - Agents no longer need to discover basic setup/build/test procedures
+2. **Standardize processes** - Ensure consistent development practices across all agent tasks
+3. **Speed up development** - Provide instant access to verified commands and workflows
+4. **Improve quality** - Include linting, testing, and verification steps in all workflows
+
+## Usage for Agents
+
+When starting work on an Open Library issue:
+
+1. Read the issue description carefully
+2. Consult [open-library-instructions.md](open-library-instructions.md) for setup if needed
+3. Follow the "Typical Task Workflow for Agents" section
+4. Use [quick-reference.md](quick-reference.md) for quick command lookups
+5. Always run tests and linters before submitting changes
+
+## Usage for Contributors
+
+These instructions are also valuable for human contributors! They provide:
+- Clear setup instructions
+- Common command reference
+- Troubleshooting guidance
+- Best practices
+
+## Maintenance
+
+These instructions should be updated when:
+- Docker configuration changes
+- New build processes are added
+- Testing procedures are modified
+- New linting tools are introduced
+- Common issues are discovered
+
+## Additional Resources
+
+- [Docker README](../../docker/README.md) - Detailed Docker setup and troubleshooting
+- [CONTRIBUTING.md](../../CONTRIBUTING.md) - General contribution guidelines
+- [Frontend Guide](https://github.com/internetarchive/openlibrary/wiki/Frontend-Guide) - Frontend development details
+- [Testing Guide](https://github.com/internetarchive/openlibrary/wiki/Testing) - Comprehensive testing documentation
+- [Wiki](https://github.com/internetarchive/openlibrary/wiki) - Full project documentation
+
+## Feedback
+
+If you find issues with these instructions or have suggestions for improvements:
+1. Open an issue on GitHub
+2. Submit a PR with updates
+3. Discuss in community calls
+
+These instructions are living documents that should evolve with the project!