Version 2.2.4 - Add developer preferences memory file and update documentation
This commit is contained in:
@ -16,6 +16,7 @@ Detailed workflow documentation is available in the `.ai-workflows/` directory:
|
||||
|
||||
- **@.ai-workflows/bug-fixing.md**: Guidelines for identifying and fixing bugs
|
||||
- **@.ai-workflows/code-review.md**: Standards for reviewing code changes
|
||||
- **@.ai-workflows/dev-prefs-memory.md**: Persistent memory of developer preferences
|
||||
- **@.ai-workflows/feature-development.md**: Process for developing new features
|
||||
- **@.ai-workflows/folder-structure.md**: Documentation of the plugin's folder structure and naming conventions
|
||||
- **@.ai-workflows/local-env-vars.md**: Local development environment paths and URLs
|
||||
@ -75,6 +76,16 @@ Before releasing:
|
||||
|
||||
Local environment variables and paths are documented in **@.ai-workflows/local-env-vars.md**.
|
||||
|
||||
## Developer Preferences
|
||||
|
||||
AI assistants should maintain a record of developer preferences in **@.ai-workflows/dev-prefs-memory.md**. When you learn about a new preference through user feedback or conversation:
|
||||
|
||||
1. Check if the preference is already documented
|
||||
2. If not, add it to the appropriate section in the dev-prefs-memory.md file
|
||||
3. Reference these preferences in future interactions
|
||||
|
||||
This ensures consistency across coding sessions and reduces the need for developers to repeatedly explain their preferences.
|
||||
|
||||
## Common Tasks
|
||||
|
||||
For detailed instructions on common tasks like creating releases, adding features, fixing bugs, and testing previous versions, see **@.ai-workflows/release-process.md**.
|
||||
|
Reference in New Issue
Block a user