Move Development Guidelines and Resources before roadmap

Reorganized document structure:

Before:
1. Vision
2. Phase 1-7
3. Development Guidelines
4. Resources

After:
1. Vision
2. Development Guidelines
3. Resources
4. Phase 1-7

Benefits:
- Guidelines available as reference from the start
- Performance budgets visible before implementation
- Testing strategy known upfront
- Resources accessible throughout all phases
- More logical flow for developers starting the project

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Claude 2025-10-27 16:48:03 +00:00
parent 4bca034ba4
commit 90e7e70ea0
No known key found for this signature in database

64
PLAN.md
View file

@ -19,6 +19,39 @@ A **local-first, cross-platform tasks application** inspired by Google Tasks. Bu
--- ---
## Development Guidelines
### Testing Strategy
- **Unit tests**: Data models and business logic
- **Integration tests**: Storage layer operations
- **E2E tests**: Critical user flows
- **Performance tests**: Startup time, large datasets
- **Platform tests**: Verify each platform build
### Performance Budgets
- **Cold start**: < 200ms on desktop, < 500ms on mobile
- **First render**: < 100ms
- **Task creation**: < 50ms
- **Sync operation**: < 2s for typical dataset (< 1000 tasks)
- **Memory usage**: < 50MB on mobile, < 100MB on desktop
### Version Scheme
Semantic versioning: `0.1.0 → 1.0.0`
### CI/CD
GitHub Actions for all platforms
---
## Resources
- [Bevy Documentation](https://bevyengine.org/)
- [egui Documentation](https://docs.rs/egui/)
- [WebDAV RFC 4918](https://datatracker.ietf.org/doc/html/rfc4918)
- [Google Tasks API](https://developers.google.com/tasks) (for importer reference)
---
## Phase 1: Core Library & CLI MVP ## Phase 1: Core Library & CLI MVP
**Goal**: Build and validate the backend with a functional CLI **Goal**: Build and validate the backend with a functional CLI
@ -716,37 +749,6 @@ If you want game-like polish after Phase 7:
--- ---
## Development Guidelines
### Testing Strategy
- **Unit tests**: Data models and business logic
- **Integration tests**: Storage layer operations
- **E2E tests**: Critical user flows
- **Performance tests**: Startup time, large datasets
- **Platform tests**: Verify each platform build
### Performance Budgets
- **Cold start**: < 200ms on desktop, < 500ms on mobile
- **First render**: < 100ms
- **Task creation**: < 50ms
- **Sync operation**: < 2s for typical dataset (< 1000 tasks)
- **Memory usage**: < 50MB on mobile, < 100MB on desktop
### Version Scheme
Semantic versioning: `0.1.0 → 1.0.0`
### CI/CD
GitHub Actions for all platforms
---
## Resources
- [Bevy Documentation](https://bevyengine.org/)
- [egui Documentation](https://docs.rs/egui/)
- [WebDAV RFC 4918](https://datatracker.ietf.org/doc/html/rfc4918)
- [Google Tasks API](https://developers.google.com/tasks) (for importer reference)
## License ## License
To be determined. To be determined.