Best Practices
Naming Conventions
Follow consistent naming conventions for packages and workspaces.
Package Names
Format
Use lowercase with underscores:
# ✓ Good
company_auth
company_ui_components
my_flutter_utils
# ✗ Bad
CompanyAuth # No camelCase
company-auth # No hyphens
Auth # Too genericPrefixing
Use consistent prefixes:
# Company prefix
acme_auth
acme_ui
acme_analytics
# Team prefix
mobile_auth
mobile_ui
# Feature prefix
payments_stripe
payments_paypalWorkspace Names
# Good workspace names
frontend-team
mobile-engineering
project-alpha
# Bad workspace names
ws1
test
tempBest Practices
- Be descriptive - Clear purpose
- Be consistent - Same prefix pattern
- Be concise - Short but meaningful
- Avoid conflicts - Don't use Flutter SDK names
- Document - Explain naming in README