Global search & replace .ai-assistant.md to AGENTS.md and .ai-workflows to .agents

.agents/bug-fixing.md

@@ -16,7 +16,7 @@ git checkout -b fix/bug-description
 
 Use a descriptive name that clearly indicates what bug is being fixed. If there's an issue number, include it in the branch name (e.g., `fix/123-plugin-activation-error`).
 
-For more detailed git workflow guidelines, see **@.ai-workflows/git-workflow.md**.
+For more detailed git workflow guidelines, see **@.agents/git-workflow.md**.
 
 ### 2. Understand the Bug
 
@@ -111,7 +111,7 @@ After fixing a bug and confirming it works, determine the appropriate version in
 
 This approach is more time-efficient as it allows you to focus on fixing the bug without worrying about version updates until the fix is confirmed working.
 
-For detailed guidelines on time-efficient development and testing, see **@.ai-workflows/incremental-development.md**.
+For detailed guidelines on time-efficient development and testing, see **@.agents/incremental-development.md**.
 
 ## Testing Previous Versions
 

.agents/code-quality-checks.md

@@ -147,7 +147,7 @@ I ran PHPCS and got the following errors. Can you help me fix them?
 [Paste error output here]
 ```
 
-For more AI assistance guidelines, see the [AI Assistant Guide](./../.ai-assistant.md).
+For more AI assistance guidelines, see the [AI Assistant Guide](./../AGENTS.md).
 
 ## Conclusion
 

.agents/dev-prefs-memory.md

@@ -31,9 +31,9 @@ This document serves as a persistent memory for developer preferences establishe
 
 ### Documentation
 
-- Prefer token-efficient documentation in `.ai-assistant.md` that references `.ai-workflows/` files
-- Document the release workflow in `.ai-assistant.md` and `.ai-workflows/release-process.md`
-- Store environment variable documentation in `.ai-workflows/local-env-vars.md`
+- Prefer token-efficient documentation in `AGENTS.md` that references `.agents/` files
+- Document the release workflow in `AGENTS.md` and `.agents/release-process.md`
+- Store environment variable documentation in `.agents/local-env-vars.md`
 - Maintain consistent documentation across readme.txt, README.md, and CHANGELOG.md
 
 ### Asset Organization

.agents/feature-development.md

@@ -16,7 +16,7 @@ git checkout -b feature/descriptive-name
 
 Use a descriptive name that clearly indicates what the feature is about. If there's an issue number, include it in the branch name (e.g., `feature/123-update-source-selector`).
 
-For more detailed git workflow guidelines, see **@.ai-workflows/git-workflow.md**.
+For more detailed git workflow guidelines, see **@.agents/git-workflow.md**.
 
 ### 2. Implement the Feature
 
@@ -44,7 +44,7 @@ Update relevant documentation to reflect the new feature:
   - Add screenshots or examples if applicable
 - Remember that any feature addition will require a version increment in all relevant files
 
-For detailed guidelines on maintaining wiki documentation, see **@.ai-workflows/wiki-documentation.md**.
+For detailed guidelines on maintaining wiki documentation, see **@.agents/wiki-documentation.md**.
 
 ### 4. Testing
 
@@ -100,7 +100,7 @@ git tag -a v{MAJOR}.{MINOR+1}.0-stable -m "Stable version {MAJOR}.{MINOR+1}.0"
 
 **IMPORTANT**: Don't update version numbers during initial development and testing. Only create a version branch and update version numbers when the feature is confirmed working.
 
-For detailed guidelines on time-efficient development and testing, see **@.ai-workflows/incremental-development.md**.
+For detailed guidelines on time-efficient development and testing, see **@.agents/incremental-development.md**.
 
 ### 7. Push to Remote (Optional for Collaboration)
 
@@ -173,7 +173,7 @@ When developing features in a workspace with multiple repositories:
    - Adapt the feature to fit the current repository's needs and architecture
    - Document the inspiration source in code comments
 
-For detailed guidelines on working in multi-repository workspaces, see **@.ai-workflows/multi-repo-workspace.md**.
+For detailed guidelines on working in multi-repository workspaces, see **@.agents/multi-repo-workspace.md**.
 
 ## Feature Types and Implementation Guidelines
 

.agents/folder-structure.md

@@ -8,7 +8,7 @@ This document outlines the folder structure of the plugin and explains the purpo
 - **includes/** - Contains core plugin functionality and classes
 - **languages/** - Contains translation files
 - **scripts/** - Contains build and deployment scripts
-- **.ai-workflows/** - Contains documentation for AI assistants
+- **.agents/** - Contains documentation for AI assistants
 - **.github/** - Contains GitHub-specific files like workflows
 - **.wordpress-org/** - Contains WordPress.org assets like banners and screenshots
 

.agents/git-workflow.md

@@ -186,7 +186,7 @@ When preparing for a release:
    - Update version numbers
    - Update changelogs
    - Create tag
-   - See **@.ai-workflows/release-process.md** for complete details
+   - See **@.agents/release-process.md** for complete details
 
 ## Contributing to External Repositories
 
@@ -233,7 +233,7 @@ Monitor the PR for feedback from maintainers and be prepared to make additional
 - Review code thoroughly before approving
 - Test changes locally when possible
 - Provide constructive feedback
-- See **@.ai-workflows/code-review.md** for detailed code review guidelines
+- See **@.agents/code-review.md** for detailed code review guidelines
 
 ### Suggested Improvements
 

.agents/wiki-documentation.md

@@ -127,7 +127,7 @@ When working in a multi-repository workspace, it's critical to ensure that wiki
    - If referencing functionality from another repository, clearly indicate that it's external
    - Use phrases like "unlike Repository X, this plugin does not include..."
 
-For detailed guidelines on working in multi-repository workspaces, see **@.ai-workflows/multi-repo-workspace.md**.
+For detailed guidelines on working in multi-repository workspaces, see **@.agents/multi-repo-workspace.md**.
 
 ## Best Practices