Standardize Markdown bullet points to use asterisks instead of hyphens

.ai-assistant.md

@@ -6,50 +6,51 @@ This guide helps AI assistants understand the project structure, workflows, and
 
 This workspace may contain multiple repository folders. Always focus ONLY on the current repository you're working in and avoid hallucinating functionality from other repositories in the workspace.
 
-- **Current Repository**: wp-plugin-starter-template-for-ai-coding
-- **Repository Purpose**: A comprehensive starter template for WordPress plugins with best practices for AI-assisted development
-- **Repository Scope**: All code changes, documentation, and functionality discussions should be limited to THIS repository only
+* **Current Repository**: wp-plugin-starter-template-for-ai-coding
+* **Repository Purpose**: A comprehensive starter template for WordPress plugins with best practices for AI-assisted development
+* **Repository Scope**: All code changes, documentation, and functionality discussions should be limited to THIS repository only
 
 ## Project Overview
 
-- **Plugin Name**: WordPress Plugin Starter Template
-- **Plugin Slug**: wp-plugin-starter-template
-- **Text Domain**: wp-plugin-starter-template
-- **Namespace**: WPALLSTARS\PluginStarterTemplate
-- **Version**: 0.1.1
-- **Requires WordPress**: 5.0+
-- **Requires PHP**: 7.0+
-- **License**: GPL-2.0+
+* **Plugin Name**: WordPress Plugin Starter Template
+* **Plugin Slug**: wp-plugin-starter-template
+* **Text Domain**: wp-plugin-starter-template
+* **Namespace**: WPALLSTARS\PluginStarterTemplate
+* **Version**: 0.1.10
+* **Requires WordPress**: 5.0+
+* **Requires PHP**: 7.0+
+* **License**: GPL-2.0+
 
 ## Repository Structure
 
-- **wp-plugin-starter-template.php**: Main plugin file with plugin headers
-- **includes/**: Core plugin functionality
-  - **plugin.php**: Main plugin class that initializes everything
-  - **core.php**: Core functionality class
-  - **updater.php**: Update mechanism for multiple sources
-- **admin/**: Admin-specific functionality
-  - **lib/**: Admin classes
-  - **css/**: Admin stylesheets
-  - **js/**: Admin JavaScript files
-- **languages/**: Translation files
-- **.github/workflows/**: GitHub Actions workflows
-- **.ai-workflows/**: Documentation for AI assistants
-- **.wiki/**: Wiki documentation templates
+* **wp-plugin-starter-template.php**: Main plugin file with plugin headers
+* **includes/**: Core plugin functionality
+  * **plugin.php**: Main plugin class that initializes everything
+  * **core.php**: Core functionality class
+  * **updater.php**: Update mechanism for multiple sources
+* **admin/**: Admin-specific functionality
+  * **lib/**: Admin classes
+  * **css/**: Admin stylesheets
+  * **js/**: Admin JavaScript files
+* **languages/**: Translation files
+* **.github/workflows/**: GitHub Actions workflows
+* **.ai-workflows/**: Documentation for AI assistants
+* **.wiki/**: Wiki documentation templates
 
 ## Coding Standards
 
 This project follows the [WordPress Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/):
 
-- Use 4 spaces for indentation, not tabs (this is a project-specific override of WordPress standards)
-- Follow WordPress naming conventions:
-  - Class names: `Class_Name`
-  - Function names: `function_name`
-  - Variable names: `$variable_name`
-- Use proper DocBlocks for all classes, methods, and functions
-- Ensure all user-facing strings are translatable
-- Validate and sanitize all inputs
-- Escape all outputs
+* Use 4 spaces for indentation, not tabs (this is a project-specific override of WordPress standards)
+* Follow WordPress naming conventions:
+  * Class names: `Class_Name`
+  * Function names: `function_name`
+  * Variable names: `$variable_name`
+* Use proper DocBlocks for all classes, methods, and functions
+* Ensure all user-facing strings are translatable
+* Validate and sanitize all inputs
+* Escape all outputs
+* Use asterisks (*) for bullet points in all Markdown files, not hyphens (-)
 
 ### Code Quality Tools
 
@@ -76,10 +77,10 @@ This project uses several automated code quality tools to ensure high standards:
    ```
 
 5. **Continuous Integration Tools**: The project integrates with several code quality tools:
-   - **CodeRabbit**: AI-powered code review tool
-   - **CodeFactor**: Continuous code quality monitoring
-   - **Codacy**: Code quality and static analysis
-   - **SonarCloud**: Code quality and security analysis
+   * **CodeRabbit**: AI-powered code review tool
+   * **CodeFactor**: Continuous code quality monitoring
+   * **Codacy**: Code quality and static analysis
+   * **SonarCloud**: Code quality and security analysis
 
 Always run PHPCS and PHPCBF locally before committing code to ensure it meets the project's coding standards.
 
@@ -103,15 +104,17 @@ When working in a multi-repository workspace, follow these guidelines to avoid c
 
 6. **Verify Before Implementation**: Before implementing or documenting a feature, verify that it actually exists in the current repository by checking the codebase.
 
+7. **Consistent Markdown Formatting**: Always use asterisks (*) for bullet points in Markdown files, not hyphens (-).
+
 ## Internationalization (i18n)
 
 All user-facing strings should be translatable:
 
-- Use `__()` for simple strings
-- Use `_e()` for echoed strings
-- Use `esc_html__()` for escaped strings
-- Use `esc_html_e()` for escaped and echoed strings
-- Always use the plugin's text domain: `wp-plugin-starter-template`
+* Use `__()` for simple strings
+* Use `_e()` for echoed strings
+* Use `esc_html__()` for escaped strings
+* Use `esc_html_e()` for escaped and echoed strings
+* Always use the plugin's text domain: `wp-plugin-starter-template`
 
 Example:
 ```php
@@ -120,26 +123,27 @@ echo esc_html__('This is a translatable string', 'wp-plugin-starter-template');
 
 ## Security Best Practices
 
-- Validate and sanitize all inputs
-- Escape all outputs
-- Use nonces for form submissions
-- Use capability checks for user actions
-- Follow the principle of least privilege
+* Validate and sanitize all inputs
+* Escape all outputs
+* Use nonces for form submissions
+* Use capability checks for user actions
+* Follow the principle of least privilege
 
 ## Documentation
 
-- Keep code comments up-to-date
-- Update README.md and readme.txt when adding new features
-- Update wiki documentation in the `.wiki/` directory
-- Update changelog in both CHANGELOG.md and readme.txt
+* Keep code comments up-to-date
+* Update README.md and readme.txt when adding new features
+* Update wiki documentation in the `.wiki/` directory
+* Update changelog in both CHANGELOG.md and readme.txt
+* Use asterisks (*) for bullet points in all Markdown files
 
 ## Git Workflow
 
-- Create feature branches from `main`
-- Use descriptive branch names (e.g., `feature/add-settings-page`)
-- Make atomic commits with clear messages
-- Create pull requests for review
-- Tag releases with version numbers (e.g., `v1.0.0`)
+* Create feature branches from `main`
+* Use descriptive branch names (e.g., `feature/add-settings-page`)
+* Make atomic commits with clear messages
+* Create pull requests for review
+* Tag releases with version numbers (e.g., `v1.0.0`)
 
 ## Developer Preferences