Instruction file imported from MAPotokina/RoamFit (
.cursor/rules/workflow.mdc). Copyright stays with the author.
Development Workflow
Reference: Follow vision.md for technical architecture and conventions.md for code standards.
Workflow Rules
- Follow the plan strictly - Work through tasklist.md iterations sequentially
- One iteration at a time - Complete each iteration fully before moving to the next
- Get approval before implementation - Propose solution with code snippets, wait for approval
- Test after implementation - Verify iteration test criteria before marking complete
- Update progress - Mark tasks and update progress table after completion
- Commit after each iteration - Commit changes with clear message
Step-by-Step Process
Before Starting an Iteration
- Read the iteration goal and tasks in tasklist.md
- Review relevant sections in vision.md and conventions.md
- Propose solution with:
- Code snippets showing approach
- File structure changes
- Key implementation details
- Wait for approval before implementing
During Implementation
- Implement approved solution
- Follow code conventions from conventions.md
- Keep it simple (KISS principle)
- Write minimal code that works
After Implementation
- Run the test specified in the iteration
- Verify functionality works as expected
- Wait for confirmation from user
- Update tasklist.md:
- Mark completed tasks with
[x] - Update progress table status (⏳ → 🚧 → ✅)
- Update test status
- Mark completed tasks with
- Commit to repository:
- Clear commit message:
feat: Complete iteration X - [description] - Include relevant files only
- Clear commit message:
Moving to Next Iteration
- Agree on next iteration with user
- Repeat process from "Before Starting an Iteration"
Important Notes
- No skipping iterations - Each builds on the previous
- No over-engineering - MVP first, simplest solution
- Test before marking complete - Verify iteration test criteria
- Ask questions if requirements are unclear
- Reference vision.md for architecture decisions
Commit Message Format
feat: Complete iteration X - [Brief description]
- [List key changes]
- [Any important notes]
Example:
feat: Complete iteration 3 - LLM utilities with logging
- Added call_llm() and call_vision() wrapper functions
- Implemented logging to logs/llm_calls.log
- Added error handling with single retry