Instruction file imported from Bzcasper/prompt-optimizer-develop (
.cursor/rules/workflows/ai-development-workflow-v4.0-backup.mdc). Copyright stays with the author.
AI Development Workflow
Practical operation process for workspace usage and document management.
๐ Start New Task
1. Query Background Information
- Check
docs/archives/README.mdto find related historical experience - Check
docs/developer/todo.mdto understand current development task status - Check
docs/developer/project-structure.mdto understand project structure - Reference other docs documents as needed (mainly for reference, not mandatory)
2. Check workspace Status
- Confirm whether workspace is clean (should only have template files)
- If workspace is messy, execute cleanup process first
- Ensure workspace uses standard template structure
3. Set Up New Task (in workspace)
- Replace template content in
scratchpad.md:### [New Feature Name] - [Start Date] **Goal**: [Specific goal description] **Status**: In Progress #### Planned Steps [ ] 1. Requirements Analysis [ ] 2. Technical Solution Design [ ] 3. Feature Implementation [ ] 4. Testing Verification [ ] 5. Documentation Update - Add urgent and important tasks in
todo.md
๐ Iterative Development
Development Loop (Repeat Execution)
- Record Progress - Update progress records in
scratchpad.md - Implement Features - Write code, run tests
- Record Discoveries - Write important experience to
experience.md - Update Status - Mark completed steps
[x] - Manage Tasks - Update task status in
todo.md
Reference Documents (View as Needed)
- Check
docs/developer/general-experience.mdto obtain general experience - Check technical documents under
docs/developer/ - Check relevant
docs/archives/directories for specialized experience
โ Complete Task
1. Summarize Work
Add in scratchpad.md:
### Completion Summary
- What features were implemented
- What problems were encountered
- How they were solved
2. Archiving Decision (Simple Judgment)
Ask yourself 4 questions:
- Is the function completed? โ Yes โ Archive
- Is there important experience? โ Yes โ Archive
- Is workspace too messy? โ Yes โ Organize
- Are there unfinished tasks? โ Yes โ Transfer to developer/todo.md
๐ Archiving Operations
Quick Archiving Process
- Create Directory -
docs/archives/[next number]-[feature name]/ - Extract Content - Extract relevant content from workspace files
- Create Documents - README.md (overview) + specific implementation documents
- Update Index - Add entry in archives/README.md
- Transfer Tasks - Transfer unfinished tasks to developer/todo.md
- Transfer Experience - Transfer general experience to developer/general-experience.md
- Reset workspace - Completely reset using template
workspace Deep Cleanup Process
- Analyze Content - Identify completed tasks, unfinished tasks, general experience, specialized experience
- Archive by Function - Archive related content to corresponding archives directories
- Task Transfer - Organize unfinished tasks by functional modules and priorities into developer/todo.md
- Experience Extraction - Extract general experience to developer/general-experience.md
- Template Reset - Delete all workspace files, copy template files from workspace-template
๐ Daily Maintenance
Query History
- First look at
docs/archives/README.mdto find feature points - Then look at specific directory README.md to understand overview
- Finally look at implementation.md and experience.md for details
Keep Clean
- Check workspace status weekly, clean up expired content promptly
- Archive immediately after completing important tasks
- Regularly transfer unfinished tasks to developer/todo.md
- Use template reset to keep workspace clean
๐งน Workspace Organization Best Practices
Organization Trigger Conditions
- workspace files exceed 200 lines
- Contain more than 3 completed tasks
- Mix content from multiple different functions
- Preparing to start new important tasks
Organization Step Template
- Content Analysis - Identify completed, in-progress, planned content
- Function Classification - Group content by feature points
- Create Archives - Create archives directories for completed features
- Task Transfer - Organize unfinished tasks by priority into developer/todo.md
- Experience Extraction - Organize general experience into developer/general-experience.md
- Template Reset - Completely reset workspace using standard template
Organization Quality Check
- โ workspace contains only 3 template files
- โ All historical tasks correctly archived
- โ Unfinished tasks transferred to developer/todo.md
- โ archives/README.md index updated
- โ Cross-reference links correct
๐ Workflow Self-Improvement
Improvement Principles
- Keep Simple - Avoid excessive expansion, control within 200 lines
- Practice-Based - Adjust processes based on actual execution experience
- Regular Assessment - Assess workflow effectiveness once after each feature process ends
Improvement Triggers
Consider updating this workflow when the following situations occur:
- Discover unreasonable or missing process steps
- workspace usage patterns change
- Archiving decision standards need adjustment
- New best practices emerge
Improvement Records
Record workflow improvement ideas in docs/developer/general-experience.md, integrate into this document regularly.
๐ ๏ธ Practical Tool Commands
workspace Template Reset
# Windows
del docs\workspace\*.md
copy docs\workspace-template\*.md docs\workspace\
ren docs\workspace\scratchpad-template.md scratchpad.md
ren docs\workspace\todo-template.md todo.md
ren docs\workspace\experience-template.md experience.md
Quick Check workspace Status
- File count should be 3 (scratchpad.md, todo.md, experience.md)
- Content should be template format, containing placeholders like
[ไปปๅกๅ็งฐ],[ๆฅๆ], etc. - If it contains specific task content, it means cleanup is needed
Self-Iterative Version: v4.0 Update Time: 2025-07-01 Features: Optimized based on actual organization experience, added deep cleanup process and practical tools
AI Development Workflow
Practical operation process for workspace usage and document management.
๐ Start New Task
1. Query Background Information
- Check
docs/archives/README.mdto find related historical experience - Check
docs/developer/todo.mdto understand current development task status - Check
docs/developer/project-structure.mdto understand project structure - Reference other docs documents as needed (mainly for reference, not mandatory)
2. Check workspace Status
- Confirm whether workspace is clean (should only have template files)
- If workspace is messy, execute cleanup process first
- Ensure workspace uses standard template structure
3. Set Up New Task (in workspace)
- Replace template content in
scratchpad.md:### [New Feature Name] - [Start Date] **Goal**: [Specific goal description] **Status**: In Progress #### Planned Steps [ ] 1. Requirements Analysis [ ] 2. Technical Solution Design [ ] 3. Feature Implementation [ ] 4. Testing Verification [ ] 5. Documentation Update - Add urgent and important tasks in
todo.md
๐ Iterative Development
Development Loop (Repeat Execution)
- Record Progress - Update progress records in
scratchpad.md - Implement Features - Write code, run tests
- Record Discoveries - Write important experience to
experience.md - Update Status - Mark completed steps
[x] - Manage Tasks - Update task status in
todo.md
Reference Documents (View as Needed)
- Check
docs/developer/general-experience.mdto obtain general experience - Check technical documents under
docs/developer/ - Check relevant
docs/archives/directories for specialized experience
โ Complete Task
1. Summarize Work
Add in scratchpad.md:
### Completion Summary
- What features were implemented
- What problems were encountered
- How they were solved
2. Archiving Decision (Simple Judgment)
Ask yourself 4 questions:
- Is the function completed? โ Yes โ Archive
- Is there important experience? โ Yes โ Archive
- Is workspace too messy? โ Yes โ Organize
- Are there unfinished tasks? โ Yes โ Transfer to developer/todo.md
๐ Archiving Operations
Quick Archiving Process
- Create Directory -
docs/archives/[next number]-[feature name]/ - Extract Content - Extract relevant content from workspace files
- Create Documents - README.md (overview) + specific implementation documents
- Update Index - Add entry in archives/README.md
- Transfer Tasks - Transfer unfinished tasks to developer/todo.md
- Transfer Experience - Transfer general experience to developer/general-experience.md
- Reset workspace - Completely reset using template
workspace Deep Cleanup Process
- Analyze Content - Identify completed tasks, unfinished tasks, general experience, specialized experience
- Archive by Function - Archive related content to corresponding archives directories
- Task Transfer - Organize unfinished tasks by functional modules and priorities into developer/todo.md
- Experience Extraction - Extract general experience to developer/general-experience.md
- Template Reset - Delete all workspace files, copy template files from workspace-template
๐ Daily Maintenance
Query History
- First look at
docs/archives/README.mdto find feature points - Then look at specific directory README.md to understand overview
- Finally look at implementation.md and experience.md for details
Keep Clean
- Check workspace status weekly, clean up expired content promptly
- Archive immediately after completing important tasks
- Regularly transfer unfinished tasks to developer/todo.md
- Use template reset to keep workspace clean
๐งน Workspace Organization Best Practices
Organization Trigger Conditions
- workspace files exceed 200 lines
- Contain more than 3 completed tasks
- Mix content from multiple different functions
- Preparing to start new important tasks
Organization Step Template
- Content Analysis - Identify completed, in-progress, planned content
- Function Classification - Group content by feature points
- Create Archives - Create archives directories for completed features
- Task Transfer - Organize unfinished tasks by priority into developer/todo.md
- Experience Extraction - Organize general experience into developer/general-experience.md
- Template Reset - Completely reset workspace using standard template
Organization Quality Check
- โ workspace contains only 3 template files
- โ All historical tasks correctly archived
- โ Unfinished tasks transferred to developer/todo.md
- โ archives/README.md index updated
- โ Cross-reference links correct
๐ Workflow Self-Improvement
Improvement Principles
- Keep Simple - Avoid excessive expansion, control within 200 lines
- Practice-Based - Adjust processes based on actual execution experience
- Regular Assessment - Assess workflow effectiveness once after each feature process ends
Improvement Triggers
Consider updating this workflow when the following situations occur:
- Discover unreasonable or missing process steps
- workspace usage patterns change
- Archiving decision standards need adjustment
- New best practices emerge
Improvement Records
Record workflow improvement ideas in docs/developer/general-experience.md, integrate into this document regularly.
๐ ๏ธ Practical Tool Commands
workspace Template Reset
# Windows
del docs\workspace\*.md
copy docs\workspace-template\*.md docs\workspace\
ren docs\workspace\scratchpad-template.md scratchpad.md
ren docs\workspace\todo-template.md todo.md
ren docs\workspace\experience-template.md experience.md
Quick Check workspace Status
- File count should be 3 (scratchpad.md, todo.md, experience.md)
- Content should be template format, containing placeholders like
[ไปปๅกๅ็งฐ],[ๆฅๆ], etc. - If it contains specific task content, it means cleanup is needed
Self-Iterative Version: v4.0 Update Time: 2025-07-01 Features: Optimized based on actual organization experience, added deep cleanup process and practical tools