Thank you for your interest in contributing to this awesome list! Your contributions help make this resource more valuable for the entire specification-driven development community.
- Fork this repository
- Clone your fork locally
- Create a branch for your contribution
- Add your resource following the guidelines below
- Submit a pull request with a clear description
- Relevance: The resource must be directly related to specification-driven development, API-first design, contract testing, BDD, or related methodologies
- Quality: Resources should be well-maintained, documented, and actively used by the community
- Uniqueness: Avoid duplicates; check existing entries before adding
- Open Source Preferred: While not required for learning resources, open source tools are preferred
**[Project Name](https://github.com/user/repo)** - Brief description of what the project does and its key features. **[Resource Name](https://example.com)** - Brief description of the resource and why it's valuable.- Must be actively maintained
- Should have significant community adoption
- Include frameworks for OpenAPI, BDD, Contract Testing, etc.
- Academic papers, books, or comprehensive guides
- Core concepts and methodologies
- Historical or foundational resources
- Tools and frameworks for building AI agents
- Specification-driven agent development
- Multi-agent systems and frameworks
- Model Context Protocol server implementations
- Tools that work with MCP
- Registries and collections
- Extensions, plugins, and tools for popular IDEs
- Language servers for specifications
- Development environment integrations
- High-quality technical articles
- Tutorials and how-to guides
- Industry insights and best practices
- Forums, discussion groups, and communities
- Conferences and events
- Professional networks
- Check for duplicates - Search existing entries to avoid duplicates
- Add to appropriate section - Place your entry in the most relevant section
- Maintain alphabetical order - Within each section, keep entries sorted alphabetically
- Write clear descriptions - Keep descriptions concise but informative
- Test links - Ensure all links work correctly
- Update table of contents - If adding new sections, update the TOC
- Use present tense
- Be concise but informative
- Highlight key features or benefits
- Avoid marketing language
- Use HTTPS when available
- Link to the primary/official source
- For GitHub projects, link to the main repository
- Commercial products without free tiers (exceptions for exceptional learning resources)
- Abandoned projects (no activity for 2+ years)
- Duplicate tools that serve the same purpose as existing entries
- Low-quality or incomplete resources
- Self-promotional content without clear community value
If you're unsure about whether a resource fits or need help with formatting:
- Open an issue to discuss before submitting a PR
- Look at existing entries for formatting examples
- Ask questions in your pull request description
Please be respectful and constructive in all interactions. This project follows the principles of open source collaboration and welcomes contributors from all backgrounds.
All contributors will be acknowledged. Your GitHub profile will be linked in the contributors section if your PR is merged.
Thank you for helping make this resource awesome! 🚀