myaidev-method 0.2.4 → 0.2.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/USER_GUIDE.md +389 -8
- package/bin/cli.js +165 -30
- package/package.json +1 -1
- package/src/lib/ascii-banner.js +100 -0
- package/src/templates/claude/commands/myai-deploy-dev.md +500 -0
- package/src/templates/claude/commands/myai-deploy-prod.md +837 -0
- package/src/templates/claude/commands/myai-deploy-staging.md +331 -0
- package/src/templates/claude/commands/myai-git-hotfix.md +957 -0
- package/src/templates/claude/commands/myai-git-pr.md +200 -0
- package/src/templates/claude/commands/myai-git-release.md +806 -0
- package/src/templates/claude/commands/myai-git-sync.md +796 -0
- package/src/templates/codex/commands/myai-astro-publish.md +51 -0
- package/src/templates/codex/commands/myai-configure.md +185 -0
- package/src/templates/codex/commands/myai-content-writer.md +73 -0
- package/src/templates/codex/commands/myai-coolify-deploy.md +159 -0
- package/src/templates/codex/commands/myai-deploy-dev.md +379 -0
- package/src/templates/codex/commands/myai-deploy-prod.md +431 -0
- package/src/templates/codex/commands/myai-deploy-staging.md +275 -0
- package/src/templates/codex/commands/myai-dev-architect.md +69 -0
- package/src/templates/codex/commands/myai-dev-code.md +82 -0
- package/src/templates/codex/commands/myai-dev-docs.md +83 -0
- package/src/templates/codex/commands/myai-dev-review.md +85 -0
- package/src/templates/codex/commands/myai-dev-test.md +84 -0
- package/src/templates/codex/commands/myai-docusaurus-publish.md +42 -0
- package/src/templates/codex/commands/myai-git-hotfix.md +512 -0
- package/src/templates/codex/commands/myai-git-pr.md +196 -0
- package/src/templates/codex/commands/myai-git-release.md +516 -0
- package/src/templates/codex/commands/myai-git-sync.md +517 -0
- package/src/templates/codex/commands/myai-mintlify-publish.md +42 -0
- package/src/templates/codex/commands/myai-payloadcms-publish.md +42 -0
- package/src/templates/codex/commands/myai-sparc-workflow.md +185 -0
- package/src/templates/codex/commands/myai-wordpress-admin.md +143 -0
- package/src/templates/codex/commands/myai-wordpress-publish.md +66 -0
- package/src/templates/gemini/commands/myai-astro-publish.toml +76 -0
- package/src/templates/gemini/commands/myai-configure.toml +188 -0
- package/src/templates/gemini/commands/myai-content-writer.toml +76 -0
- package/src/templates/gemini/commands/myai-coolify-deploy.toml +138 -0
- package/src/templates/gemini/commands/myai-deploy-dev.toml +379 -0
- package/src/templates/gemini/commands/myai-deploy-prod.toml +438 -0
- package/src/templates/gemini/commands/myai-deploy-staging.toml +275 -0
- package/src/templates/gemini/commands/myai-dev-architect.toml +64 -0
- package/src/templates/gemini/commands/myai-dev-code.toml +75 -0
- package/src/templates/gemini/commands/myai-dev-docs.toml +76 -0
- package/src/templates/gemini/commands/myai-dev-review.toml +78 -0
- package/src/templates/gemini/commands/myai-dev-test.toml +77 -0
- package/src/templates/gemini/commands/myai-docusaurus-publish.toml +63 -0
- package/src/templates/gemini/commands/myai-git-hotfix.toml +953 -0
- package/src/templates/gemini/commands/myai-git-pr.toml +196 -0
- package/src/templates/gemini/commands/myai-git-release.toml +802 -0
- package/src/templates/gemini/commands/myai-git-sync.toml +792 -0
- package/src/templates/gemini/commands/myai-mintlify-publish.toml +67 -0
- package/src/templates/gemini/commands/myai-payloadcms-publish.toml +59 -0
- package/src/templates/gemini/commands/myai-sparc-workflow.toml +47 -0
- package/src/templates/gemini/commands/myai-wordpress-admin.toml +143 -0
- package/src/templates/gemini/commands/myai-wordpress-publish.toml +77 -0
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
# Astro Content Publisher
|
|
2
|
+
|
|
3
|
+
Publish markdown content to Astro static site with content collections support and git workflow: $ARGUMENTS
|
|
4
|
+
|
|
5
|
+
Invoke the Astro publishing agent to transform frontmatter, validate schemas, and deploy via git.
|
|
6
|
+
|
|
7
|
+
## Usage Examples
|
|
8
|
+
|
|
9
|
+
```bash
|
|
10
|
+
/myai-astro-publish "article.md"
|
|
11
|
+
/myai-astro-publish "post.md" --collection blog
|
|
12
|
+
/myai-astro-publish "page.md" --pages
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
## Options
|
|
16
|
+
|
|
17
|
+
- `--collection <name>` - Target content collection (default: blog)
|
|
18
|
+
- `--pages` - Publish to pages directory instead
|
|
19
|
+
- `--project <path>` - Astro project path
|
|
20
|
+
- `--branch <name>` - Git branch (default: main)
|
|
21
|
+
- `--no-push` - Commit but don't push
|
|
22
|
+
- `--dry-run` - Validate without publishing
|
|
23
|
+
|
|
24
|
+
## Prerequisites
|
|
25
|
+
|
|
26
|
+
Astro project with astro.config.mjs and git repository.
|
|
27
|
+
|
|
28
|
+
## Examples
|
|
29
|
+
|
|
30
|
+
### Publish to content collection
|
|
31
|
+
```
|
|
32
|
+
/myai-astro-publish "my-article.md" --collection blog
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
### Publish to pages
|
|
36
|
+
```
|
|
37
|
+
/myai-astro-publish "about.md" --pages
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
### Custom project
|
|
41
|
+
```
|
|
42
|
+
/myai-astro-publish "post.md" --project ~/my-site --branch staging
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
## Frontmatter Transformation
|
|
46
|
+
|
|
47
|
+
Automatically converts:
|
|
48
|
+
- `date` → `pubDate` (ISO 8601 format)
|
|
49
|
+
- `status: published` → `draft: false`
|
|
50
|
+
- `excerpt` → `description`
|
|
51
|
+
- `image` → `heroImage`
|
|
@@ -0,0 +1,185 @@
|
|
|
1
|
+
# MyAI Method Configuration
|
|
2
|
+
|
|
3
|
+
Configure MyAI Method settings: $ARGUMENTS
|
|
4
|
+
|
|
5
|
+
Configure MyAI Method settings including WordPress credentials, content defaults, and agent management.
|
|
6
|
+
|
|
7
|
+
## Available Configurations
|
|
8
|
+
|
|
9
|
+
### wordpress
|
|
10
|
+
Interactive WordPress setup - no manual .env file creation needed!
|
|
11
|
+
|
|
12
|
+
**Process:**
|
|
13
|
+
1. **Collect WordPress site URL**
|
|
14
|
+
- Prompt: "Enter your WordPress site URL (e.g., https://yoursite.com):"
|
|
15
|
+
- Validate URL format and accessibility
|
|
16
|
+
- Test basic connectivity
|
|
17
|
+
|
|
18
|
+
2. **Get WordPress username**
|
|
19
|
+
- Prompt: "Enter your WordPress admin username:"
|
|
20
|
+
- Validate username format
|
|
21
|
+
|
|
22
|
+
3. **Guide through Application Password creation**
|
|
23
|
+
- Show step-by-step instructions:
|
|
24
|
+
* "Go to your WordPress Admin → Users → Your Profile"
|
|
25
|
+
* "Scroll down to 'Application Passwords' section"
|
|
26
|
+
* "Enter a name like 'MyAI Dev Method' and click 'Add New'"
|
|
27
|
+
* "Copy the generated password (it looks like: xxxx xxxx xxxx xxxx)"
|
|
28
|
+
- Prompt: "Paste your Application Password here:"
|
|
29
|
+
- Validate password format
|
|
30
|
+
|
|
31
|
+
4. **Test connection**
|
|
32
|
+
- Verify credentials by making test API call
|
|
33
|
+
- Show success/failure message with troubleshooting tips
|
|
34
|
+
|
|
35
|
+
5. **Save configuration**
|
|
36
|
+
- Create/update `.env` file automatically
|
|
37
|
+
- Set proper file permissions (600)
|
|
38
|
+
- Show confirmation of saved settings
|
|
39
|
+
|
|
40
|
+
6. **Optional SSH setup**
|
|
41
|
+
- Ask: "Do you want to set up SSH for advanced WordPress administration? (y/n)"
|
|
42
|
+
- If yes, prompt for SSH details:
|
|
43
|
+
* SSH host/IP
|
|
44
|
+
* SSH username
|
|
45
|
+
* SSH key path (optional)
|
|
46
|
+
- Test SSH connection if credentials provided
|
|
47
|
+
|
|
48
|
+
**Success message:**
|
|
49
|
+
```
|
|
50
|
+
✅ WordPress integration configured successfully!
|
|
51
|
+
- Site: [URL]
|
|
52
|
+
- User: [username]
|
|
53
|
+
- Connection: ✅ Verified
|
|
54
|
+
- Available commands: /myai-wordpress-admin, /myai-wordpress-publish
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
### defaults
|
|
58
|
+
Configure default content settings:
|
|
59
|
+
- Default word count
|
|
60
|
+
- Default post status
|
|
61
|
+
- Default tone
|
|
62
|
+
- Default audience
|
|
63
|
+
|
|
64
|
+
### agents
|
|
65
|
+
List and manage available agents:
|
|
66
|
+
- **List**: Show all installed agents with descriptions and capabilities
|
|
67
|
+
- **Status**: Check agent configuration validity and tool availability
|
|
68
|
+
- **Edit**: Open agent files for customization
|
|
69
|
+
- **Backup**: Create backups before modifying agents
|
|
70
|
+
- **Restore**: Restore agents from backups
|
|
71
|
+
- **Validate**: Test agent YAML frontmatter and prompt structure
|
|
72
|
+
- **Tools**: Show what tools each agent has access to
|
|
73
|
+
|
|
74
|
+
## WordPress REST API Integration
|
|
75
|
+
|
|
76
|
+
WordPress integration uses the native WordPress REST API with Application Passwords:
|
|
77
|
+
|
|
78
|
+
1. **Authentication**: HTTP Basic Auth with Application Passwords
|
|
79
|
+
2. **Content Creation**: Direct API calls using WebFetch and curl tools
|
|
80
|
+
3. **Gutenberg Support**: Manual conversion to Gutenberg block format when needed
|
|
81
|
+
4. **No MCP Required**: Uses native Claude Code tools for all operations
|
|
82
|
+
|
|
83
|
+
## WordPress Setup Example
|
|
84
|
+
|
|
85
|
+
```bash
|
|
86
|
+
# User runs the command
|
|
87
|
+
/myai-configure wordpress
|
|
88
|
+
|
|
89
|
+
# System prompts and responses:
|
|
90
|
+
? Enter your WordPress site URL: https://myblog.com
|
|
91
|
+
✓ URL format valid, testing connection...
|
|
92
|
+
✓ WordPress site accessible
|
|
93
|
+
|
|
94
|
+
? Enter your WordPress admin username: john_admin
|
|
95
|
+
✓ Username format valid
|
|
96
|
+
|
|
97
|
+
# System shows instructions
|
|
98
|
+
📝 Create Application Password:
|
|
99
|
+
1. Go to https://myblog.com/wp-admin/profile.php
|
|
100
|
+
2. Scroll to "Application Passwords"
|
|
101
|
+
3. Enter name: "MyAI Dev Method"
|
|
102
|
+
4. Click "Add New"
|
|
103
|
+
5. Copy the generated password
|
|
104
|
+
|
|
105
|
+
? Paste your Application Password: abcd efgh ijkl mnop
|
|
106
|
+
✓ Password format valid, testing connection...
|
|
107
|
+
✓ WordPress API connection successful!
|
|
108
|
+
|
|
109
|
+
? Set up SSH for advanced features? (y/n): y
|
|
110
|
+
? SSH host/IP: myblog.com
|
|
111
|
+
? SSH username: john
|
|
112
|
+
? SSH key path (press enter for default): /home/user/.ssh/id_rsa
|
|
113
|
+
✓ SSH connection tested successfully
|
|
114
|
+
|
|
115
|
+
✅ Configuration saved to .env
|
|
116
|
+
✅ File permissions set to 600 (secure)
|
|
117
|
+
|
|
118
|
+
WordPress integration ready! Available commands:
|
|
119
|
+
• /myai-wordpress-admin health-check
|
|
120
|
+
• /myai-wordpress-publish filename.md
|
|
121
|
+
• /myai-content-writer "topic" --publish_to_wordpress true
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
## Agent Management Examples
|
|
125
|
+
|
|
126
|
+
```bash
|
|
127
|
+
# List all available agents
|
|
128
|
+
/myai-configure agents --list
|
|
129
|
+
|
|
130
|
+
# Show detailed agent status
|
|
131
|
+
/myai-configure agents --status
|
|
132
|
+
|
|
133
|
+
# Check specific agent configuration
|
|
134
|
+
/myai-configure agents --validate content-writer
|
|
135
|
+
|
|
136
|
+
# Create backup before editing
|
|
137
|
+
/myai-configure agents --backup wordpress-admin
|
|
138
|
+
|
|
139
|
+
# Edit agent (opens file in editor)
|
|
140
|
+
/myai-configure agents --edit content-writer
|
|
141
|
+
|
|
142
|
+
# Restore agent from backup
|
|
143
|
+
/myai-configure agents --restore content-writer
|
|
144
|
+
|
|
145
|
+
# Show agent tool permissions
|
|
146
|
+
/myai-configure agents --tools wordpress-admin
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
## Agent Operations
|
|
150
|
+
|
|
151
|
+
### List Operation
|
|
152
|
+
Shows:
|
|
153
|
+
- Agent name and description
|
|
154
|
+
- File location
|
|
155
|
+
- Available tools
|
|
156
|
+
- Last modified date
|
|
157
|
+
- Configuration status (valid/invalid)
|
|
158
|
+
|
|
159
|
+
### Status Operation
|
|
160
|
+
Checks:
|
|
161
|
+
- YAML frontmatter validity
|
|
162
|
+
- Required fields presence
|
|
163
|
+
- Tool availability in Claude Code
|
|
164
|
+
- File permissions
|
|
165
|
+
- Syntax errors
|
|
166
|
+
|
|
167
|
+
### Validate Operation
|
|
168
|
+
Performs:
|
|
169
|
+
- YAML syntax validation
|
|
170
|
+
- Required field verification
|
|
171
|
+
- Tool permission verification
|
|
172
|
+
- Prompt structure analysis
|
|
173
|
+
- Best practice recommendations
|
|
174
|
+
|
|
175
|
+
### Backup/Restore Operations
|
|
176
|
+
- Creates timestamped backups in `.claude/backups/`
|
|
177
|
+
- Maintains backup history
|
|
178
|
+
- Safe restoration with confirmation prompts
|
|
179
|
+
- Backup before any modifications
|
|
180
|
+
|
|
181
|
+
## Security
|
|
182
|
+
|
|
183
|
+
- Never display passwords in plain text
|
|
184
|
+
- Use environment variables for sensitive data
|
|
185
|
+
- Validate URLs and credentials before saving
|
|
@@ -0,0 +1,73 @@
|
|
|
1
|
+
# Professional Content Writer
|
|
2
|
+
|
|
3
|
+
Create comprehensive, well-researched content based on the provided topic: $ARGUMENTS
|
|
4
|
+
|
|
5
|
+
You are a professional content writer specializing in creating high-quality, engaging, and SEO-optimized content.
|
|
6
|
+
|
|
7
|
+
## Core Competencies
|
|
8
|
+
|
|
9
|
+
1. **Writing Excellence**
|
|
10
|
+
- Clear, concise, and engaging prose
|
|
11
|
+
- Proper grammar, spelling, and punctuation
|
|
12
|
+
- Varied sentence structure and rhythm
|
|
13
|
+
- Active voice preference
|
|
14
|
+
- Storytelling when appropriate
|
|
15
|
+
|
|
16
|
+
2. **SEO Optimization**
|
|
17
|
+
- Natural keyword integration
|
|
18
|
+
- Proper heading hierarchy (H1, H2, H3)
|
|
19
|
+
- Meta descriptions (150-160 characters)
|
|
20
|
+
- Internal and external linking suggestions
|
|
21
|
+
- URL-friendly slugs
|
|
22
|
+
|
|
23
|
+
3. **Content Structure**
|
|
24
|
+
- Compelling introductions with hooks
|
|
25
|
+
- Logical flow and transitions
|
|
26
|
+
- Scannable formatting (bullets, lists, short paragraphs)
|
|
27
|
+
- Strong conclusions with CTAs when appropriate
|
|
28
|
+
|
|
29
|
+
## Writing Process
|
|
30
|
+
|
|
31
|
+
1. **Understanding**: Analyze the topic, audience, and goals from $ARGUMENTS
|
|
32
|
+
2. **Research**: Use WebSearch to gather current, relevant information
|
|
33
|
+
3. **Planning**: Create a detailed outline with logical structure
|
|
34
|
+
4. **Writing**: Craft the content following SEO best practices
|
|
35
|
+
5. **Optimization**: Review for clarity, accuracy, and SEO
|
|
36
|
+
6. **Formatting**: Ensure proper Markdown formatting
|
|
37
|
+
|
|
38
|
+
## Output Requirements
|
|
39
|
+
|
|
40
|
+
Save the content as a markdown file with the following structure:
|
|
41
|
+
|
|
42
|
+
```markdown
|
|
43
|
+
---
|
|
44
|
+
title: [Compelling, keyword-rich title]
|
|
45
|
+
meta_description: [150-160 character summary]
|
|
46
|
+
slug: [url-friendly-version]
|
|
47
|
+
tags: [relevant, topic, tags]
|
|
48
|
+
category: [Primary category]
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
# [Title]
|
|
52
|
+
|
|
53
|
+
[Content with proper heading hierarchy]
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
## Parameters Supported
|
|
57
|
+
|
|
58
|
+
- Topic (required): Main subject matter
|
|
59
|
+
- Word count: Target length (default: 800)
|
|
60
|
+
- Tone: professional, casual, technical, conversational, academic
|
|
61
|
+
- Audience: Target reader demographic
|
|
62
|
+
- SEO keywords: Primary and secondary keywords
|
|
63
|
+
- Publish to WordPress: Auto-publish as draft (true/false)
|
|
64
|
+
|
|
65
|
+
## WordPress Integration
|
|
66
|
+
|
|
67
|
+
If publish_to_wordpress is requested:
|
|
68
|
+
1. Save the content locally first
|
|
69
|
+
2. Check for WordPress configuration in environment variables
|
|
70
|
+
3. Use the WordPress MCP to create a draft post
|
|
71
|
+
4. Report the draft URL to the user
|
|
72
|
+
|
|
73
|
+
Always prioritize user value over keyword density. Write for humans first, search engines second.
|
|
@@ -0,0 +1,159 @@
|
|
|
1
|
+
# Coolify Deployment Manager
|
|
2
|
+
|
|
3
|
+
Execute Coolify deployment operations: $ARGUMENTS
|
|
4
|
+
|
|
5
|
+
Launch the Coolify deployment specialist agent for application deployment and infrastructure management.
|
|
6
|
+
|
|
7
|
+
## Available Operations
|
|
8
|
+
|
|
9
|
+
### Quick Deploy Commands
|
|
10
|
+
- `deploy <app-name>` - Deploy application by name or from current directory
|
|
11
|
+
- `status` - Check Coolify system status and connectivity
|
|
12
|
+
- `list <resource-type>` - List servers, projects, applications, databases
|
|
13
|
+
- `logs <app-name>` - View application deployment logs
|
|
14
|
+
- `restart <app-name>` - Restart an application
|
|
15
|
+
- `env <app-name>` - Manage environment variables
|
|
16
|
+
|
|
17
|
+
### Detailed Deploy Commands
|
|
18
|
+
- `deploy --repo <url> --name <name> --server <uuid>` - Deploy with specific configuration
|
|
19
|
+
- `deploy --dockerfile --port 8080 --domain app.example.com` - Deploy Docker app
|
|
20
|
+
- `deploy-database --type postgresql --name mydb` - Deploy database
|
|
21
|
+
- `deploy-stack --config stack.json` - Deploy multi-component stack
|
|
22
|
+
|
|
23
|
+
## Usage Examples
|
|
24
|
+
|
|
25
|
+
### Quick Deployments
|
|
26
|
+
```
|
|
27
|
+
/myai-coolify-deploy status
|
|
28
|
+
/myai-coolify-deploy list servers
|
|
29
|
+
/myai-coolify-deploy deploy my-nextjs-app
|
|
30
|
+
/myai-coolify-deploy logs my-app
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
### Advanced Deployments
|
|
34
|
+
```
|
|
35
|
+
/myai-coolify-deploy deploy --repo https://github.com/user/app --name api-server
|
|
36
|
+
/myai-coolify-deploy deploy --dockerfile --port 3000 --domain api.example.com
|
|
37
|
+
/myai-coolify-deploy deploy-database --type postgresql --version 16
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
### Environment Management
|
|
41
|
+
```
|
|
42
|
+
/myai-coolify-deploy env my-app --set API_KEY=secret123
|
|
43
|
+
/myai-coolify-deploy env my-app --file .env.production
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
### Monitoring & Management
|
|
47
|
+
```
|
|
48
|
+
/myai-coolify-deploy list applications --detailed
|
|
49
|
+
/myai-coolify-deploy restart my-app
|
|
50
|
+
/myai-coolify-deploy logs my-app --follow
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
## Process Flow
|
|
54
|
+
|
|
55
|
+
1. **Parse Arguments**
|
|
56
|
+
- Extract operation type from $ARGUMENTS
|
|
57
|
+
- Identify deployment target and configuration
|
|
58
|
+
- Validate required parameters
|
|
59
|
+
|
|
60
|
+
2. **Verify Connectivity**
|
|
61
|
+
- Check Coolify API accessibility
|
|
62
|
+
- Validate credentials from `.env`
|
|
63
|
+
- Confirm target server availability
|
|
64
|
+
|
|
65
|
+
3. **Execute Operation**
|
|
66
|
+
- Load coolify-deploy agent
|
|
67
|
+
- Run appropriate deployment script
|
|
68
|
+
- Monitor progress and handle errors
|
|
69
|
+
|
|
70
|
+
4. **Report Results**
|
|
71
|
+
- Provide deployment URL and status
|
|
72
|
+
- Show relevant logs if deployment fails
|
|
73
|
+
- Suggest next steps or troubleshooting
|
|
74
|
+
|
|
75
|
+
## Required Environment Variables
|
|
76
|
+
|
|
77
|
+
```bash
|
|
78
|
+
COOLIFY_URL=https://coolify.myai1.ai
|
|
79
|
+
COOLIFY_API_KEY=your_api_key_here
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
Create API token in Coolify: Settings → Keys & Tokens → Create API Token
|
|
83
|
+
|
|
84
|
+
## Examples with Context
|
|
85
|
+
|
|
86
|
+
### Example 1: Deploy Current Directory
|
|
87
|
+
```bash
|
|
88
|
+
# User has Next.js app in current directory
|
|
89
|
+
/myai-coolify-deploy deploy .
|
|
90
|
+
|
|
91
|
+
# Agent workflow:
|
|
92
|
+
# 1. Detects Next.js app (reads package.json)
|
|
93
|
+
# 2. Lists available servers
|
|
94
|
+
# 3. Prompts for server selection
|
|
95
|
+
# 4. Deploys with Nixpacks
|
|
96
|
+
# 5. Provides deployment URL
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### Example 2: Deploy with GitHub Repo
|
|
100
|
+
```bash
|
|
101
|
+
/myai-coolify-deploy deploy --repo https://github.com/user/api --name api-prod
|
|
102
|
+
|
|
103
|
+
# Agent workflow:
|
|
104
|
+
# 1. Validates repository accessibility
|
|
105
|
+
# 2. Selects optimal server
|
|
106
|
+
# 3. Creates Coolify application
|
|
107
|
+
# 4. Triggers deployment
|
|
108
|
+
# 5. Monitors until complete
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
### Example 3: Deploy Full Stack
|
|
112
|
+
```bash
|
|
113
|
+
/myai-coolify-deploy deploy-stack
|
|
114
|
+
|
|
115
|
+
# Agent workflow:
|
|
116
|
+
# 1. Reads stack configuration (stack.json or prompts)
|
|
117
|
+
# 2. Uses Task tool to parallelize:
|
|
118
|
+
# - Deploy PostgreSQL database
|
|
119
|
+
# - Deploy Redis cache
|
|
120
|
+
# - Deploy API backend
|
|
121
|
+
# - Deploy frontend
|
|
122
|
+
# 3. Configures connections between components
|
|
123
|
+
# 4. Runs health checks
|
|
124
|
+
# 5. Reports complete stack status
|
|
125
|
+
```
|
|
126
|
+
|
|
127
|
+
## Safety Features
|
|
128
|
+
|
|
129
|
+
- **Confirmation gates** - Prompts for production deployments
|
|
130
|
+
- **Rollback support** - Can revert failed deployments
|
|
131
|
+
- **Credential safety** - API keys never logged or exposed
|
|
132
|
+
- **Resource validation** - Verifies server capacity before deployment
|
|
133
|
+
- **Error recovery** - Auto-retry with exponential backoff
|
|
134
|
+
|
|
135
|
+
## Output Format
|
|
136
|
+
|
|
137
|
+
The agent provides structured output:
|
|
138
|
+
- **Status updates**: Real-time deployment progress
|
|
139
|
+
- **Success confirmation**: Deployment URL and access info
|
|
140
|
+
- **Error details**: Clear error messages with troubleshooting steps
|
|
141
|
+
- **Next actions**: Suggested follow-up commands
|
|
142
|
+
|
|
143
|
+
## Integration with Other Agents
|
|
144
|
+
|
|
145
|
+
Works seamlessly with:
|
|
146
|
+
- **content-writer** - Deploy WordPress for published content
|
|
147
|
+
- **wordpress-admin** - Manage deployed WordPress instances
|
|
148
|
+
- Custom agents for CI/CD pipeline integration
|
|
149
|
+
|
|
150
|
+
## Performance Notes
|
|
151
|
+
|
|
152
|
+
- Typical deployment: 2-5 minutes (depends on build complexity)
|
|
153
|
+
- Script execution: <1 second for status/list operations
|
|
154
|
+
- Agent initialization: <3k tokens (lightweight pattern)
|
|
155
|
+
- Extended thinking available for complex decisions
|
|
156
|
+
|
|
157
|
+
---
|
|
158
|
+
|
|
159
|
+
Always run `/myai-coolify-deploy status` first to verify connectivity before deployment operations.
|