{"id":40639821,"url":"https://github.com/verygoodplugins/ai-editor-rules","last_synced_at":"2026-01-21T08:02:01.028Z","repository":{"id":307852889,"uuid":"1030511073","full_name":"verygoodplugins/ai-editor-rules","owner":"verygoodplugins","description":"Rules, config files, and commands we use at Very Good Plugins for AI-assisted development","archived":false,"fork":false,"pushed_at":"2025-08-02T15:00:48.000Z","size":165,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2025-08-02T17:25:31.353Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/verygoodplugins.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2025-08-01T19:08:18.000Z","updated_at":"2025-08-02T15:00:51.000Z","dependencies_parsed_at":"2025-08-02T17:25:38.729Z","dependency_job_id":"e3607243-59ab-4359-a6bb-ed9396c5d740","html_url":"https://github.com/verygoodplugins/ai-editor-rules","commit_stats":null,"previous_names":["verygoodplugins/ai-editor-rules"],"tags_count":null,"template":false,"template_full_name":null,"purl":"pkg:github/verygoodplugins/ai-editor-rules","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/verygoodplugins%2Fai-editor-rules","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/verygoodplugins%2Fai-editor-rules/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/verygoodplugins%2Fai-editor-rules/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/verygoodplugins%2Fai-editor-rules/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/verygoodplugins","download_url":"https://codeload.github.com/verygoodplugins/ai-editor-rules/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/verygoodplugins%2Fai-editor-rules/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28629922,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-21T04:47:28.174Z","status":"ssl_error","status_checked_at":"2026-01-21T04:47:22.943Z","response_time":86,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-01-21T08:01:58.979Z","updated_at":"2026-01-21T08:02:01.012Z","avatar_url":"https://github.com/verygoodplugins.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# AI Editor Rules\n\nA comprehensive collection of production-tested configurations and slash commands for AI-powered development tools. Streamline your workflow with ready-to-use setups for WordPress, Rails, and React development that enable AI agents to work efficiently and safely within your projects.\n\n## 🎯 Why This Repository?\n\nThis repository solves common friction points in AI-assisted development:\n\n- **Copy-Paste Ready**: No complex setup - just copy configs directly into your projects\n- **Technology-Specific**: Tailored permissions and workflows for WordPress, Rails, and React\n- **Production Tested**: Based on real-world usage in professional development environments\n- **Parallel Development**: Git worktree integration allows AI agents to work on multiple features simultaneously\n- **Structured Commands**: XML-based slash commands provide reliable, parseable workflows\n\n## 🚀 Quick Start\n\nChoose your technology stack and copy the appropriate configuration files:\n\n### For Claude Code Users\n```bash\n# WordPress Development\ncp claude-code/wordpress/settings.json your-project/.claude/\ncp -r claude-code/wordpress/commands/ your-project/.claude/\n\n# Rails Development  \ncp claude-code/rails/settings.json your-project/.claude/\ncp -r claude-code/rails/commands/ your-project/.claude/\n\n# React Development\ncp claude-code/react/settings.json your-project/.claude/\ncp -r claude-code/react/commands/ your-project/.claude/\n\n# General Commands (works with any project)\ncp -r claude-code/general/commands/ your-project/.claude/\n```\n\n### For Cursor Users\n```bash\n# WordPress Development\ncp cursor/wordpress/tasks.json your-project/.vscode/\ncp cursor/wordpress/mcp-config.json your-project/.vscode/\ncp -r cursor/wordpress/rules/ your-project/.cursor/\n\n# Rails Development\ncp cursor/rails/tasks.json your-project/.vscode/\ncp cursor/rails/mcp-config.json your-project/.vscode/\ncp -r cursor/rails/rules/ your-project/.cursor/\n\n# React Development  \ncp cursor/react/tasks.json your-project/.vscode/\ncp cursor/react/mcp-config.json your-project/.vscode/\ncp -r cursor/react/rules/ your-project/.cursor/\n```\n\n### For GitHub Actions (Optional)\n```bash\n# WordPress Development (includes Claude Code, PHPCS, PHPStan)\nmkdir -p your-project/.github/workflows\ncp claude-code/wordpress/.github/workflows/* your-project/.github/workflows/\n\n# Rails Development (includes Claude Code integration)\nmkdir -p your-project/.github/workflows  \ncp claude-code/rails/.github/workflows/* your-project/.github/workflows/\n```\n\n## 📁 Repository Structure\n\n```\nai-editor-rules/\n├── claude-code/              # Claude Code configurations\n│   ├── general/              # Universal commands for any project\n│   │   └── commands/         # Cross-platform slash commands\n│   ├── wordpress/            # WordPress plugin/theme development\n│   │   ├── settings.json     # WordPress-specific permissions \u0026 environment\n│   │   ├── commands/         # WordPress workflow commands (XML-based)\n│   │   └── .github/workflows/ # WordPress GitHub Actions (Claude, PHPCS, PHPStan)\n│   ├── rails/                # Ruby on Rails development\n│   │   ├── settings.json     # Rails development permissions\n│   │   ├── commands/         # Rails workflow commands (XML-based)\n│   │   └── .github/workflows/ # Rails GitHub Actions (Claude integration)\n│   └── react/                # React/frontend development\n│       ├── settings.json     # Frontend development permissions\n│       └── commands/         # React workflow commands (XML-based)\n├── cursor/                   # Cursor editor configurations\n│   ├── wordpress/            # WordPress development setup\n│   │   ├── tasks.json        # VSCode tasks for WordPress\n│   │   ├── mcp-config.json   # MCP servers configuration\n│   │   └── rules/            # Cursor rules for WordPress (.mdc files)\n│   ├── rails/                # Rails development setup\n│   │   ├── tasks.json        # Rails-specific tasks\n│   │   ├── mcp-config.json   # Rails MCP configuration\n│   │   └── rules/            # Cursor rules for Rails (.mdc files)\n│   └── react/                # React development setup\n│       ├── tasks.json        # Frontend build tasks\n│       ├── mcp-config.json   # React MCP configuration\n│       └── rules/            # Cursor rules for React (.mdc files)\n└── README.md\n```\n\n## 🎯 What's Included\n\n### Claude Code Configurations\n\n#### General Commands (Universal)\n- **Daily Summary**: Automated development progress reporting across repositories  \n- **Cross-Platform**: Works with any technology stack\n- **Git Integration**: Smart repository discovery and multi-repo analysis\n\n#### WordPress Development\n- **Permissions**: PHP tools, WordPress CLI, Composer, PHPUnit, browser automation\n- **Commands**: GitHub issue implementation, support ticket resolution, documentation updates\n- **Security Focus**: WordPress-specific security scanning and best practices\n- **Environment**: WordPress development with admin testing capabilities\n- **API Integration**: Optional support system and WordPress documentation API integration\n\n#### Rails Development  \n- **Permissions**: Ruby/Rails tools, database access, RSpec, RuboCop, browser testing\n- **Commands**: GitHub issue implementation, visual UI development workflows\n- **Multi-tenancy**: Support for complex Rails application patterns\n- **Environment**: Rails development with comprehensive testing setup\n\n#### React Development\n- **Permissions**: Node.js tools, build systems, testing frameworks, browser automation\n- **Commands**: Feature implementation with visual testing and accessibility checks\n- **Modern Stack**: TypeScript, ESLint, Prettier, Storybook integration\n- **Environment**: Modern frontend development with performance optimization\n\n### Cursor Configurations\n\n#### Task Automation\n- **WordPress**: Composer, PHPUnit, PHPCS, WordPress CLI integration\n- **Rails**: Bundle, RSpec, RuboCop, database migrations, server management\n- **React**: npm/yarn, ESLint, Prettier, TypeScript, Storybook\n\n#### MCP Server Integration\n- **File System**: Project file access and manipulation\n- **Database**: PostgreSQL integration for data operations\n- **Browser**: Playwright automation for UI testing\n- **Git**: Version control integration\n- **Search**: Web search for documentation and troubleshooting\n\n#### Coding Rules\n- Technology-specific best practices and conventions\n- Security guidelines and performance optimizations\n- Testing patterns and documentation standards\n\n## 🛠️ Featured Tools and Workflows\n\n### Claude Code Slash Commands\n\nAll commands use [XML-structured workflows](https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/use-xml-tags) for improved reliability and parsing accuracy.\n\n#### Universal Commands (Available in all stacks)\n- `@daily-summary` - Automated development progress reporting across repositories\n- **Cross-Platform**: Works with any Git repository and technology stack\n\n#### WordPress Specific\n- `@implement-gh-issue` - Complete GitHub issue implementation with WordPress admin UI testing\n- `@implement-support-ticket` - Support ticket resolution with customer communication\n- `@update-documentation` - WordPress documentation updates via REST API\n\n#### Rails Specific  \n- `@implement-gh-issue` - GitHub issue implementation with Rails patterns and testing\n- `@visual-development` - UI development with visual comparison and iteration\n\n#### React Specific\n- `@implement-gh-issue` - React feature implementation with comprehensive testing and accessibility\n\n### GitHub Actions Integration\n\n#### WordPress Workflows\n- **Claude Code Review**: Automated WordPress-specific PR reviews with security, performance, and standards checking\n- **Claude Interactive**: Full WordPress development environment with WP-CLI, Composer, and testing tools\n- **PHPCS**: WordPress coding standards enforcement across multiple PHP versions\n- **PHPStan**: Static analysis with WordPress-specific configuration and stubs\n\n#### Rails Workflows  \n- **Claude Code Review**: Rails-focused PR reviews covering conventions, security, performance, and testing\n- **Claude Interactive**: Complete Rails development setup with database, testing, and linting tools\n\n#### Cursor Task Integration\n\n#### WordPress Tasks\n- Automated code style checking and fixing\n- PHPUnit test execution with coverage\n- WordPress CLI integration for site management\n- Asset building and optimization\n\n#### Rails Tasks\n- Database setup and migration management\n- RSpec test suite execution\n- RuboCop style enforcement\n- Brakeman security scanning\n- Rails server and console management\n\n#### React Tasks\n- Development server with hot reloading\n- Production build optimization\n- ESLint and Prettier integration\n- TypeScript compilation checking\n- Storybook development and building\n\n## 🔧 Key Design Decisions\n\n### Why XML for Claude Commands?\n\nOur Claude Code commands use [XML structure](https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/use-xml-tags) because:\n\n- **Improved Parsing**: Claude can more accurately separate instructions, examples, and context\n- **Reduced Errors**: Clear structure prevents Claude from mixing up different parts of complex workflows\n- **Better Reliability**: Structured prompts lead to more consistent and predictable outputs\n- **Easier Maintenance**: XML tags make it simple to modify specific sections without rewriting entire commands\n\n### Why Git Worktrees in Subfolders?\n\nCommands create worktrees within `./worktrees/` for several reasons:\n\n- **Parallel Development**: Work on multiple issues simultaneously without branch conflicts\n- **Isolated Testing**: Each feature develops in its own clean environment\n- **No Permission Hassle**: Worktrees stay within the project directory so Claude Code doesn't need additional folder access\n- **Clean Main Workspace**: Your primary working directory remains unaffected during AI development\n- **Automatic Cleanup**: Worktrees are automatically removed after PR creation\n\nExample worktree structure:\n```\nyour-project/\n├── worktrees/\n│   ├── issue-123/     # AI working on feature branch\n│   └── ticket-456/    # AI working on bug fix\n├── src/               # Your main codebase (unchanged)\n└── .git/              # Shared git history\n```\n\n## ⚡ GitHub Actions Integration\n\n### 🚀 Quick Setup\n\n#### 1. Copy Workflows to Your Project\n```bash\n# For WordPress projects\nmkdir -p .github/workflows\ncp claude-code/wordpress/.github/workflows/* .github/workflows/\n\n# For Rails projects  \nmkdir -p .github/workflows\ncp claude-code/rails/.github/workflows/* .github/workflows/\n```\n\n#### 2. Set Up Required Secrets\nGo to your GitHub repository → Settings → Secrets and variables → Actions:\n\n```bash\n# Required for Claude Code integration\nCLAUDE_CODE_OAUTH_TOKEN=your_claude_oauth_token_here\n```\n\n#### 3. Configure Optional Labels (Recommended)\nAdd these labels to your repository for better workflow control:\n- `run analysis` - Triggers PHPCS and PHPStan on PRs\n- `code review` - Alternative trigger for analysis workflows\n\n### 🔧 Available Workflows\n\n#### WordPress Development Workflows\n\n##### **`claude-code-review.yml`** - Automated PR Reviews\n**Triggers**: Pull requests (opened/updated)\n**Features**:\n- WordPress-specific code review focusing on security, performance, and standards\n- Multi-PHP version testing (7.4, 8.0, 8.1, 8.2)\n- WordPress environment setup with WP-CLI\n- Comprehensive review prompts covering:\n  - WordPress coding standards compliance\n  - Security (sanitization, escaping, nonces, capabilities)\n  - Performance optimization\n  - WordPress API usage\n  - Accessibility and compatibility\n\n**Configuration**:\n```yaml\n# Optional: Filter by file types (default covers all WordPress files)\npaths:\n  - \"**/*.php\"\n  - \"**/*.js\"\n  - \"**/*.css\"\n  - \"readme.txt\"\n  - \"functions.php\"\n\n# Optional: Only review PRs from specific contributors\nif: github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'\n```\n\n##### **`claude.yml`** - Interactive Claude Integration\n**Triggers**: Issues, PR comments, reviews (when mentioning `@claude`)\n**Features**:\n- Full WordPress development environment\n- WP-CLI integration for site management\n- Comprehensive toolset (Composer, PHP tools, Node.js, build tools)\n- WordPress test environment setup\n- Custom WordPress development instructions\n\n**Usage**:\n```bash\n# In GitHub issues or PR comments\n@claude help me optimize this database query\n@claude review the security of this user input handling\n@claude set up unit tests for this WordPress hook\n```\n\n##### **`phpcs.yml`** - WordPress Coding Standards\n**Triggers**: Push to main branches, labeled PRs\n**Features**:\n- WordPress.org coding standards enforcement\n- Multi-PHP version matrix testing\n- Automatic WordPress standards detection\n- Detailed failure reporting with summaries\n- Composer caching for faster builds\n\n**Customization**:\n```yaml\n# Modify PHP versions to test\nstrategy:\n  matrix:\n    php-version: ['7.4', '8.1', '8.2']\n\n# Change trigger conditions\nif: contains(github.event.pull_request.labels.*.name, 'run analysis')\n```\n\n##### **`phpstan.yml`** - Static Analysis\n**Triggers**: Push to main branches, labeled PRs  \n**Features**:\n- WordPress-aware static analysis with WordPress stubs\n- Automatic WordPress function recognition\n- Level 5 analysis with WordPress-specific ignores\n- Memory optimization for large WordPress projects\n- Auto-configuration generation\n\n**WordPress-Specific Configuration**:\n```yaml\n# Auto-generated phpstan.neon includes:\nparameters:\n  level: 5\n  ignoreErrors:\n    - '#Function wp_[a-zA-Z_]+ not found#'\n    - '#Constant [A-Z_]+ not found#'\n  bootstrapFiles:\n    - vendor/php-stubs/wordpress-stubs/wordpress-stubs.php\n```\n\n#### Rails Development Workflows\n\n##### **`claude-code-review.yml`** - Rails PR Reviews\n**Triggers**: Pull requests on Rails files\n**Features**:\n- Rails 7.2+ convention enforcement\n- Security vulnerability scanning with Brakeman\n- Database migration safety checks\n- Performance optimization suggestions\n- API design review for Rails APIs\n\n**Rails-Specific Focus**:\n- ActiveRecord patterns and N+1 query detection\n- RESTful design principles\n- Rails security best practices\n- Test coverage and quality (RSpec/Minitest)\n- Database migration reversibility\n\n##### **`claude.yml`** - Interactive Rails Development\n**Triggers**: Issues, PR comments with `@claude`\n**Features**:\n- Complete Rails development environment setup\n- Database preparation and migration tools\n- Comprehensive Rails toolset (RSpec, StandardRB, Brakeman)\n- Rails console integration for debugging\n- Multi-environment support\n\n### 🛠️ Environment Variables \u0026 Configuration\n\n#### Required Environment Variables\n```bash\n# In your GitHub repository secrets\nCLAUDE_CODE_OAUTH_TOKEN=your_token_here\n```\n\n#### Optional WordPress Environment Variables\n```yaml\n# In claude.yml workflow\nclaude_env: |\n  WP_DEBUG: true\n  WP_DEBUG_LOG: true\n  SCRIPT_DEBUG: true\n  WP_ENVIRONMENT_TYPE: development\n  PLUGIN_NAME: your-plugin-name\n  WP_MULTISITE: false\n```\n\n#### Optional Rails Environment Variables\n```yaml\n# In claude.yml workflow  \nclaude_env: |\n  RAILS_ENV: development\n  DATABASE_URL: postgresql://localhost/app_development\n  REDIS_URL: redis://localhost:6379/0\n  API_VERSION: v1\n```\n\n#### WordPress Slash Command API Integration\nSome WordPress slash commands require additional API credentials for full functionality:\n\n##### Support Ticket Integration (`@implement-support-ticket`)\n```bash\n# In your Claude Code settings.json or environment\nSUPPORT_API_KEY=your_support_system_api_key\nSUPPORT_URL=https://your-support-system.com\n\n# For HelpScout integration specifically:\nSUPPORT_API_KEY=your_helpscout_api_key\nSUPPORT_URL=https://api.helpscout.net/v2\n```\n\n##### Documentation Updates (`@update-documentation`)\n```bash\n# WordPress REST API credentials for documentation site\nDOCS_URL=https://your-docs-site.com\nDOCS_USER=your_wordpress_username\nDOCS_PASSWORD=your_application_password\n\n# Example for WordPress documentation site:\nDOCS_URL=https://docs.yourcompany.com\nDOCS_USER=documentation_bot\nDOCS_PASSWORD=xxxx xxxx xxxx xxxx\n```\n\n**Setting up WordPress Application Passwords:**\n1. Go to your WordPress admin → Users → Your Profile\n2. Scroll to \"Application Passwords\" section\n3. Enter application name (e.g., \"Claude Documentation Bot\")\n4. Click \"Add New Application Password\"\n5. Copy the generated password (format: `xxxx xxxx xxxx xxxx`)\n6. Use this as your `DOCS_PASSWORD` value\n\n**Note:** These API integrations are optional - the commands work without them but provide enhanced functionality when configured.\n\n### 🔧 Workflow Customization\n\n#### Modify Trigger Conditions\n```yaml\n# WordPress: Only run on specific file changes\non:\n  pull_request:\n    paths:\n      - \"includes/**/*.php\"\n      - \"admin/**/*.php\"\n      - \"*.php\"\n\n# Rails: Only run on backend changes\non:\n  pull_request:\n    paths:\n      - \"app/**/*.rb\"\n      - \"lib/**/*.rb\"\n      - \"config/**/*.rb\"\n```\n\n#### Customize Claude Review Prompts\n```yaml\n# WordPress security-focused review\ndirect_prompt: |\n  Review this WordPress PR with extra focus on:\n  - Input sanitization using WordPress functions\n  - Output escaping with esc_html(), esc_attr(), esc_url()\n  - Nonce verification for all forms and AJAX\n  - User capability checks before sensitive operations\n  - SQL injection prevention with $wpdb-\u003eprepare()\n\n# Rails performance-focused review\ndirect_prompt: |\n  Review this Rails PR focusing on:\n  - N+1 query prevention and database optimization\n  - Proper indexing strategies\n  - Background job usage for expensive operations\n  - Caching implementation with Rails cache\n  - Memory usage optimization\n```\n\n#### Add Custom Tools\n```yaml\n# WordPress: Add custom build tools\nallowed_tools: |\n  Bash(composer:*),\n  Bash(wp:*),\n  Bash(npm run custom-build),\n  Bash(gulp custom-task),\n  Bash(your-custom-script.sh)\n\n# Rails: Add deployment tools\nallowed_tools: |\n  Bash(bundle exec:*),\n  Bash(rails:*),\n  Bash(cap production deploy),\n  Bash(docker-compose:*)\n```\n\n### 🎯 Workflow Best Practices\n\n#### Label-Based Workflow Control\n```yaml\n# Smart triggering based on PR labels\nif: |\n  contains(github.event.pull_request.labels.*.name, 'needs-review') ||\n  contains(github.event.pull_request.labels.*.name, 'security') ||\n  github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'\n```\n\n#### Multi-Environment Testing\n```yaml\n# Test across multiple PHP/Ruby versions\nstrategy:\n  matrix:\n    php-version: ['7.4', '8.0', '8.1', '8.2']\n    wordpress-version: ['5.9', '6.0', '6.1', 'trunk']\n```\n\n#### Conditional Workflow Steps\n```yaml\n# Only run tests if test files exist\n- name: Run Tests\n  if: hashFiles('tests/**/*.php') != ''\n  run: composer test\n\n# Skip analysis for draft PRs\nif: github.event.pull_request.draft == false\n```\n\n### 🚨 Troubleshooting\n\n#### Common Issues \u0026 Solutions\n\n**Claude workflows not triggering:**\n```bash\n# Check that CLAUDE_CODE_OAUTH_TOKEN is set\n# Verify @claude mention format in comments\n# Ensure workflow file syntax is valid YAML\n```\n\n**PHPCS/PHPStan failures:**\n```bash\n# Verify composer.json includes required dev dependencies:\n# - squizlabs/php_codesniffer\n# - wp-coding-standards/wpcs\n# - phpstan/phpstan\n# - php-stubs/wordpress-stubs\n```\n\n**Permission errors:**\n```yaml\n# Ensure workflow has required permissions\npermissions:\n  contents: read\n  pull-requests: read  \n  issues: read\n  id-token: write\n  actions: read\n```\n\n### 📊 Workflow Monitoring\n\n#### GitHub Actions Dashboard\n- Monitor workflow runs in the Actions tab\n- Review failure logs for debugging\n- Check artifact uploads for detailed reports\n\n#### Performance Optimization\n- Use workflow caching to speed up builds\n- Conditional execution to avoid unnecessary runs\n- Matrix strategies for comprehensive testing\n\n## 🔧 Customization\n\n### Adapting for Your Project\n\n1. **Update file paths**: Modify MCP configurations to point to your project directory\n2. **Adjust permissions**: Add or remove tools based on your specific needs\n3. **Environment variables**: Set appropriate values for your development setup\n4. **Task configurations**: Customize build and test commands for your workflow\n\n### Example Customizations\n\n#### WordPress Plugin Development\n```json\n{\n  \"env\": {\n    \"WP_ENV\": \"development\",\n    \"WP_DEBUG\": \"true\",\n    \"PLUGIN_NAME\": \"your-plugin-name\"\n  }\n}\n```\n\n#### Rails API Development\n```json\n{\n  \"env\": {\n    \"RAILS_ENV\": \"development\", \n    \"DATABASE_URL\": \"postgresql://localhost/your_app_development\",\n    \"API_VERSION\": \"v1\"\n  }\n}\n```\n\n#### React Component Library\n```json\n{\n  \"env\": {\n    \"NODE_ENV\": \"development\",\n    \"STORYBOOK_PORT\": \"6006\",\n    \"COMPONENT_LIB\": \"true\"\n  }\n}\n```\n\n## 🚀 Advanced Features\n\n### Browser Automation Integration\nAll configurations include Playwright integration for:\n- Visual regression testing\n- User interaction simulation\n- Screenshot capture for documentation\n- Accessibility testing\n\n### Security-First Development\nBuilt-in security scanning and best practices for:\n- Input validation and sanitization\n- SQL injection prevention\n- XSS attack mitigation\n- Dependency vulnerability checking\n\n### Performance Optimization\nAutomated performance analysis including:\n- Database query optimization\n- Bundle size analysis\n- Memory usage monitoring\n- Load time optimization\n\n## 🤝 Contributing\n\nWe welcome contributions! To add support for a new technology or improve existing configurations:\n\n1. Fork the repository\n2. Create a new directory under `claude-code/` and `cursor/` for your technology\n3. Add appropriate configuration files following the established patterns\n4. Test with real projects\n5. Submit a pull request with clear documentation\n\n## 📚 Real-World Foundation\n\nEach configuration is based on production usage in professional development environments:\n\n- **WordPress**: Tested with complex plugins featuring 60+ third-party integrations\n- **Rails**: Proven in multi-tenant SaaS applications with complex business logic\n- **React**: Battle-tested in large component libraries and performance-critical applications\n\n### Production Features Included\n\n- **Security-First**: Built-in security scanning and vulnerability prevention\n- **Performance Optimized**: Automated performance monitoring and optimization\n- **Testing Comprehensive**: Visual, unit, integration, and accessibility testing\n- **Documentation Automated**: Auto-updating documentation workflows\n- **Standards Compliant**: Enforces coding standards and best practices\n\n## 🔗 Related Projects\n\n- [Claude Code Documentation](https://docs.anthropic.com/claude/docs/claude-code)\n- [Cursor Editor](https://cursor.sh/)\n- [Model Context Protocol](https://modelcontextprotocol.io/)\n\n## 📄 License\n\nGNU GPL v3 - feel free to use these configurations in your projects!\n\n---\n\n**Ready to supercharge your AI-assisted development?** Choose your stack and copy the configs! 🚀","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fverygoodplugins%2Fai-editor-rules","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fverygoodplugins%2Fai-editor-rules","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fverygoodplugins%2Fai-editor-rules/lists"}