Welcome to the monorepo! This guide will help you understand how to work effectively within our structured development environment.
By the end of this guide, you'll understand:
- How our development workflow operates
- The two main operation modes for different types of tasks
- How to structure your work for maximum efficiency
- Where to find help when you need it
Our development process uses two distinct operation modes:
- Plan-First Mode - For analysis, investigation, and planning
- Immediate Implementation Mode - For fixes, features, and direct implementation
Familiarize yourself with how our code is organized:
- Monorepo Structure - High-level organization
Ensure you have the right tools configured:
- Development Tools - Required tooling
- GitHub Integration - GitHub workflow setup
- Receive a task (issue, feature request, bug report)
- Choose the right operation mode based on the task type
- Follow the appropriate workflow (planning vs. implementation)
- Validate your changes using our testing and formatting pipeline
- Submit your work through our GitHub workflow
- Always format your code - Our CI pipeline requires proper formatting
- Test your changes - Run validation before submitting
- Follow naming conventions - Consistency helps everyone
- Keep changes focused - Small, focused changes are easier to review
- Check the documentation - Most questions are answered here
- Review similar issues - Look at how similar problems were solved
- Ask the team - Don't hesitate to reach out for guidance
- Quick Commands - Essential commands you'll use daily
- Troubleshooting - Solutions to common problems
- Rule Index - Complete reference to all guidelines
Once you're comfortable with the basics:
- Dive deeper into operation modes - Master the planning and implementation workflows
- Explore the GitHub workflow - Learn our issue and PR process
- Understand the validation pipeline - Ensure your code meets quality standards
- Review best practices - Learn proven approaches for common scenarios
- Start with Plan-First Mode when you're unsure - it's better to plan than to implement incorrectly
- Use the validation commands frequently - catch issues early
- Keep commits focused - one logical change per commit
- Read the error messages - they usually tell you exactly what to fix
Ready to dive deeper? Check out the Operation Modes guide to learn how to approach different types of development tasks.