myaidev-method 0.2.5 → 0.2.7

package/src/templates/gemini/commands/myai-mintlify-publish.toml

@@ -0,0 +1,67 @@
+prompt = """
+Publish markdown/MDX content to Mintlify documentation site with automatic navigation updates: {{args}}
+
+Invoke the Mintlify publishing agent to transform content, update mint.json, and deploy via git.
+
+## Task
+Add content to Mintlify documentation and update navigation configuration.
+
+## Process
+
+1. **Read the markdown/MDX file** from the path provided
+2. **Validate frontmatter** for Mintlify compatibility
+3. **Copy file to docs directory**
+4. **Update mint.json navigation** if --nav-section is specified
+5. **Commit and push** via git workflow
+
+## Parameters
+
+When parsing {{args}}, look for:
+- File path (required): Path to markdown or MDX file
+- --nav-section: Add to navigation section (e.g., "API Reference")
+- --project: Mintlify project path (default: current directory)
+- --branch: Git branch name (default: main)
+- --no-push: Commit but don't push
+- --dry-run: Validate without publishing
+
+## Examples
+
+Basic publish:
+```
+myai-mintlify-publish "getting-started.mdx"
+```
+
+With navigation:
+```
+myai-mintlify-publish "api-users.md" --nav-section "API Reference"
+```
+
+Custom project:
+```
+myai-mintlify-publish "guide.md" --project ~/docs --branch develop
+```
+
+## Prerequisites
+
+Requires Mintlify project with:
+- mint.json configuration file
+- Git repository initialized
+- Proper directory structure
+
+## Navigation Update
+
+When --nav-section is specified:
+1. Parse mint.json
+2. Find or create navigation section
+3. Add new page reference
+4. Maintain alphabetical order (optional)
+5. Save updated mint.json
+
+## Git Workflow
+
+1. Check project status
+2. Add new file and mint.json (if updated)
+3. Commit with descriptive message
+4. Push to remote (unless --no-push)
+5. Report deployment status
+"""

package/src/templates/gemini/commands/myai-payloadcms-publish.toml

@@ -0,0 +1,59 @@
+prompt = """
+Publish markdown content to PayloadCMS headless CMS: {{args}}
+
+Invoke the PayloadCMS publishing agent to convert markdown to Lexical format and publish to your PayloadCMS instance.
+
+## Task
+Convert and publish markdown content to PayloadCMS.
+
+## Process
+
+1. **Read the markdown file** from the path provided
+2. **Parse frontmatter** and extract metadata
+3. **Convert markdown to Lexical format** (PayloadCMS rich text format)
+4. **Load PayloadCMS configuration** from `.env`:
+   - PAYLOADCMS_URL
+   - PAYLOADCMS_API_KEY or login credentials
+5. **Create or update document** in specified collection
+6. **Report publishing status** with document ID and URL
+
+## Parameters
+
+When parsing {{args}}, look for:
+- File path (required): Path to markdown file
+- --status: draft (default) or published
+- --collection: Target collection name (default: posts)
+- --id: Update existing document by ID
+- --dry-run: Validate without publishing
+- --verbose: Show detailed progress
+
+## Examples
+
+Publish as draft:
+```
+myai-payloadcms-publish "my-article.md"
+```
+
+Publish to production:
+```
+myai-payloadcms-publish "article.md" --status published --collection blog-posts
+```
+
+Update existing:
+```
+myai-payloadcms-publish "updated.md" --id 67890
+```
+
+## Prerequisites
+
+Configure PayloadCMS credentials using the configure command first.
+
+## Output
+
+Success message with:
+- Document ID
+- Collection name
+- Status (draft/published)
+- Admin panel URL
+- Preview URL (if available)
+"""

package/src/templates/gemini/commands/myai-sparc-workflow.toml

@@ -0,0 +1,47 @@
+prompt = """
+You are the SPARC Workflow Orchestrator for systematic software development.
+
+Execute the complete 5-phase SPARC development workflow for: {{args}}
+
+## SPARC Methodology
+
+**S**pecification - Define requirements and system boundaries
+**P**seudocode - Plan implementation approach
+**A**rchitecture - Design system structure, APIs, and data models
+**R**efinement - Implement, test, and review code quality
+**C**ompletion - Document and deliver production-ready software
+
+## Workflow Execution
+
+Execute all 5 phases sequentially:
+
+### Phase 1: Architecture (🏗️)
+Design system architecture, API specifications, data models, and technology stack.
+Output: `.myaidev-method/sparc/architecture.md`
+
+### Phase 2: Implementation (💻)
+Implement production-ready code following SOLID principles and Clean Code standards.
+Output: `.myaidev-method/sparc/code-output/`
+
+### Phase 3: Testing (🧪)
+Create comprehensive test suites with 80%+ critical path coverage.
+Output: `.myaidev-method/sparc/test-results/`
+
+### Phase 4: Review (👁️)
+Analyze code quality, security (OWASP Top 10), and performance.
+Output: `.myaidev-method/sparc/review-report.md`
+
+### Phase 5: Documentation (📚)
+Generate API docs, user guides, and architecture documentation.
+Output: `.myaidev-method/sparc/documentation/`
+
+## Quality Standards
+
+- **SOLID Principles**: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion
+- **Clean Code**: DRY, KISS, YAGNI
+- **Security**: OWASP Top 10 compliance
+- **Testing**: 80%+ critical path coverage, 60%+ overall
+- **Performance**: <200ms API responses, <50ms database queries
+
+Execute the complete workflow and provide comprehensive outputs for each phase.
+"""

package/src/templates/gemini/commands/myai-wordpress-admin.toml

@@ -0,0 +1,143 @@
+prompt = """
+Launch the WordPress administrator for comprehensive site management, security analysis, and performance optimization: {{args}}
+
+Execute WordPress administration operations based on the specified action.
+
+## Available Operations
+
+### Security Operations
+- `security-scan` - Comprehensive security assessment and vulnerability check
+- `malware-check` - Scan for malicious code and suspicious files
+- `user-audit` - Review user accounts, roles, and permissions
+- `plugin-security` - Check plugins and themes for known vulnerabilities
+- `ssl-check` - Verify SSL/TLS certificate and security configuration
+- `file-permissions` - Audit file and directory permissions
+
+### Performance Operations
+- `speed-test` - Analyze site performance and Core Web Vitals
+- `database-optimize` - Clean and optimize WordPress database
+- `cache-setup` - Configure and optimize caching strategies
+- `image-optimize` - Analyze and optimize media files
+- `resource-monitor` - Check server resource usage and optimization
+
+### Health Operations
+- `health-check` - Comprehensive WordPress site health assessment
+- `error-analysis` - Review and analyze error logs
+- `uptime-check` - Monitor site availability and response times
+- `backup-verify` - Validate backup integrity and restore capabilities
+- `update-check` - Check for WordPress, plugin, and theme updates
+
+### Administration Operations
+- `user-manage` - User and role management operations
+- `plugin-manage` - Plugin installation, updates, and management
+- `content-cleanup` - Remove spam, unused content, and optimize database
+- `settings-optimize` - Configure optimal WordPress settings
+- `staging-deploy` - Manage staging environment operations
+
+## Usage Examples
+
+### Security Assessment
+```
+myai-wordpress-admin security-scan
+myai-wordpress-admin malware-check
+myai-wordpress-admin user-audit --role administrator
+```
+
+### Performance Optimization
+```
+myai-wordpress-admin speed-test --detailed
+myai-wordpress-admin database-optimize --cleanup-revisions
+myai-wordpress-admin cache-setup --type redis
+```
+
+### Site Health Monitoring
+```
+myai-wordpress-admin health-check --comprehensive
+myai-wordpress-admin error-analysis --last-24h
+myai-wordpress-admin uptime-check --setup-monitoring
+```
+
+### Administrative Tasks
+```
+myai-wordpress-admin plugin-manage --update-all --check-security
+myai-wordpress-admin content-cleanup --remove-spam --optimize-db
+myai-wordpress-admin settings-optimize --performance-focus
+```
+
+## Process Flow
+
+1. **Initialize WordPress Connection**
+   - Validate connection to WordPress
+   - Check SSH access if configured
+   - Verify administrative permissions
+
+2. **Execute Operation**
+   - Parse operation parameters from arguments
+   - Execute requested administrative task
+   - Monitor progress
+
+3. **Security & Safety Checks**
+   - Create backups before destructive operations
+   - Validate permissions before changes
+   - Log all administrative actions
+
+4. **Generate Report**
+   - Provide detailed findings and analysis
+   - Include actionable recommendations
+   - Create priority-based action items
+
+5. **Follow-up Actions**
+   - Suggest monitoring setup
+   - Recommend maintenance schedules
+   - Provide next steps guidance
+
+## Required Environment Variables
+
+```bash
+WORDPRESS_URL=https://your-wordpress-site.com
+WORDPRESS_USERNAME=admin-username
+WORDPRESS_APP_PASSWORD=application-password
+
+# Optional SSH access for server-level operations
+SSH_HOST=server-ip-address
+SSH_USERNAME=server-username
+SSH_KEY_PATH=/path/to/private/key
+```
+
+## Safety Features
+
+- **Backup Creation**: Automatic backup before major changes
+- **Permission Validation**: Verify admin rights before operations
+- **Staging Support**: Test changes in staging environment first
+- **Rollback Capability**: Provide undo procedures for changes
+- **Audit Logging**: Track all administrative actions
+
+## Output Format
+
+Structured reports with:
+- **Executive Summary**: High-level findings and status
+- **Critical Issues**: Immediate attention required
+- **Warnings**: Items requiring near-term resolution
+- **Recommendations**: Optimization suggestions
+- **Action Items**: Specific tasks with priorities
+- **Technical Details**: Logs, metrics, and detailed analysis
+
+## Security Considerations
+
+This command has extensive administrative capabilities. Ensure:
+- Strong authentication credentials
+- Limited access to authorized personnel
+- Regular audit of administrative actions
+- Backup verification before major changes
+- Staging environment testing when possible
+
+## Integration Notes
+
+- Works with WordPress REST API
+- Optional SSH integration for server-level access
+- Supports both managed and self-hosted WordPress
+- Compatible with major security and performance plugins
+- Provides recommendations for popular caching solutions
+
+Always prioritize site security and stability. When in doubt, create backups and test in staging environments first.
+"""

package/src/templates/gemini/commands/myai-wordpress-publish.toml

@@ -0,0 +1,77 @@
+prompt = """
+Publish the specified markdown file to WordPress using the WordPress REST API: {{args}}
+
+## Task
+Read and publish markdown content to WordPress as draft or live post.
+
+## Process
+
+1. **Read the markdown file** from the path provided in the arguments
+2. **Parse the frontmatter** to extract:
+   - title
+   - meta_description (use as excerpt)
+   - slug
+   - tags
+   - category
+   - use_gutenberg (optional, default: false)
+
+3. **Load WordPress configuration** from `.env` file:
+   - WORDPRESS_URL
+   - WORDPRESS_USERNAME
+   - WORDPRESS_APP_PASSWORD
+   - WORDPRESS_USE_GUTENBERG (optional, default: false)
+
+4. **Convert content format** if Gutenberg is enabled:
+   - If use_gutenberg is true or WORDPRESS_USE_GUTENBERG is true
+   - Convert HTML to Gutenberg block format using patterns:
+     * `<!-- wp:paragraph --><p>content</p><!-- /wp:paragraph -->`
+     * `<!-- wp:heading {"level":2} --><h2>title</h2><!-- /wp:heading -->`
+
+5. **Create categories and tags** if they don't exist using WordPress REST API
+
+6. **Publish the post** using the WordPress REST API:
+   - Authenticate with Basic Auth (username:app_password)
+   - POST to `/wp-json/wp/v2/posts`
+   - Include title, content, status, categories, tags
+
+7. **Report the result** including:
+   - Post ID
+   - Preview URL
+   - Edit URL in WordPress admin
+   - Format used (Classic or Gutenberg)
+
+## Parameters
+
+When parsing {{args}}, look for:
+- File path (required): Path to markdown file
+- --status: draft (default), publish, pending, private
+- --gutenberg: Use Gutenberg block format (default: false)
+- --classic: Force classic editor format (overrides defaults)
+
+## Error Handling
+
+If WordPress credentials are not configured:
+- Guide user to set up environment variables
+- Provide instructions for creating Application Password
+
+If file doesn't exist or isn't readable:
+- Report clear error message
+- Suggest checking file path
+
+## Success Response
+
+```
+✅ Successfully published to WordPress!
+- Post ID: [id]
+- Status: [draft/published]
+- Preview: [preview_url]
+- Edit: [admin_edit_url]
+```
+
+## Authentication
+
+Use WordPress REST API with Application Password authentication:
+- Create Base64 encoded credentials: base64(username:app_password)
+- Add Authorization header: "Basic [encoded_credentials]"
+- All API calls use HTTPS
+"""