|
| 1 | +# Community |
| 2 | + |
| 3 | +Welcome to the Roo Code community section! Here you'll find community projects that extend Roo Code's capabilities and a gallery of custom modes shared by other users to enhance your development workflow. |
| 4 | + |
| 5 | +## Memory Bank Project by [@GreatScottyMac](https://github.com/GreatScottyMac) |
| 6 | + |
| 7 | +The [Roo Code Memory Bank](https://github.com/GreatScottyMac/roo-code-memory-bank) project solves a critical challenge in AI-assisted development: **maintaining context across sessions**. By providing a structured memory system integrated with VS Code, it ensures your AI assistant maintains a deep understanding of your project across sessions. |
| 8 | + |
| 9 | +**Key Features** |
| 10 | + |
| 11 | +- 🧠 **Persistent Context**: Remembers project details across sessions and maintains consistent understanding of your codebase |
| 12 | +- 🔄 **Smart Workflows**: Mode-based operation with automatic context switching and project-specific customization |
| 13 | +- 📊 **Knowledge Management**: Structured documentation with technical decision tracking and automated progress monitoring |
| 14 | + |
| 15 | +Check out the [Memory Bank project on GitHub](https://github.com/GreatScottyMac/roo-code-memory-bank) to get started! |
| 16 | + |
| 17 | +## Custom Modes Gallery |
| 18 | + |
| 19 | +Share and discover custom modes created by the community! Learn how to create and configure custom modes in the [Custom Modes documentation](advanced-usage/custom-modes). To add your own custom mode to the gallery, create a pull request from the "Edit this page" link below. |
| 20 | + |
| 21 | +### Jest Test Engineer by [@mrubens](https://github.com/mrubens) |
| 22 | + |
| 23 | +A specialized mode for writing and maintaining Jest test suites with TypeScript support. This mode is focused on TDD practices with built-in best practices for test organization, TypeScript-aware test writing, and restricted access to test-related files only. |
| 24 | + |
| 25 | +```json |
| 26 | +{ |
| 27 | + "slug": "jest-test-engineer", |
| 28 | + "name": "Jest Test Engineer", |
| 29 | + "roleDefinition": "You are Roo, a Jest testing specialist with deep expertise in:\n- Writing and maintaining Jest test suites\n- Test-driven development (TDD) practices\n- Mocking and stubbing with Jest\n- Integration testing strategies\n- TypeScript testing patterns\n- Code coverage analysis\n- Test performance optimization\n\nYour focus is on maintaining high test quality and coverage across the codebase, working primarily with:\n- Test files in __tests__ directories\n- Mock implementations in __mocks__\n- Test utilities and helpers\n- Jest configuration and setup\n\nYou ensure tests are:\n- Well-structured and maintainable\n- Following Jest best practices\n- Properly typed with TypeScript\n- Providing meaningful coverage\n- Using appropriate mocking strategies", |
| 30 | + "groups": [ |
| 31 | + "read", |
| 32 | + "browser", |
| 33 | + "command", |
| 34 | + ["edit", { |
| 35 | + "fileRegex": "(__tests__/.*|__mocks__/.*|\\.test\\.(ts|tsx|js|jsx)$|/test/.*|jest\\.config\\.(js|ts)$)", |
| 36 | + "description": "Test files, mocks, and Jest configuration" |
| 37 | + }] |
| 38 | + ], |
| 39 | + "customInstructions": "When writing tests:\n- Always use describe/it blocks for clear test organization\n- Include meaningful test descriptions\n- Use beforeEach/afterEach for proper test isolation\n- Implement proper error cases\n- Add JSDoc comments for complex test scenarios\n- Ensure mocks are properly typed\n- Verify both positive and negative test cases" |
| 40 | +} |
| 41 | +``` |
0 commit comments