myaidev-method 0.2.8 → 0.2.10

package/src/server/user-management/layers.ts

@@ -0,0 +1,51 @@
+import { Layer } from "effect";
+import { LinuxUserService } from "./LinuxUserService";
+import { DirectoryService } from "./DirectoryService";
+import { QuotaService } from "./QuotaService";
+import { UserManagementService } from "./UserManagementService";
+
+/**
+ * User Management Layer Composition
+ *
+ * Provides Effect-TS layers for dependency injection of user management services.
+ */
+
+// Independent services (no dependencies)
+const IndependentServices = Layer.mergeAll(
+  LinuxUserService.Live,
+  DirectoryService.Live,
+  QuotaService.Live
+);
+
+// User management service depends on all base services
+const UserManagementWithDeps = Layer.provide(
+  UserManagementService.Live,
+  IndependentServices
+);
+
+// Complete layer with all services
+export const UserManagementLayer = Layer.mergeAll(
+  IndependentServices,
+  UserManagementWithDeps
+);
+
+/**
+ * Create a complete user management layer
+ *
+ * Usage:
+ * ```typescript
+ * const layer = createUserManagementLayer();
+ * const runtime = ManagedRuntime.make(layer);
+ *
+ * const result = await runtime.runPromise(
+ *   Effect.gen(function* () {
+ *     const userMgmt = yield* UserManagementService;
+ *     return yield* userMgmt.createUser({
+ *       username: "john",
+ *       email: "john@example.com",
+ *     });
+ *   })
+ * );
+ * ```
+ */
+export const createUserManagementLayer = () => UserManagementLayer;

package/src/shared/types.ts

@@ -0,0 +1,111 @@
+// Shared types for MyAIDev Method Web Server
+
+export interface User {
+  id: string;
+  username: string;
+  email: string;
+  passwordHash: string | null;
+  linuxUsername: string;
+  createdAt: number;
+  updatedAt: number;
+  isActive: boolean;
+  emailVerified: boolean;
+  failedLoginAttempts: number;
+  lastLoginAt: number | null;
+}
+
+export interface Session {
+  id: string;
+  userId: string;
+  tokenHash: string;
+  ipAddress: string | null;
+  userAgent: string | null;
+  createdAt: number;
+  expiresAt: number;
+  isRevoked: boolean;
+  revokedAt: number | null;
+}
+
+export interface OAuth2Provider {
+  id: string;
+  userId: string;
+  provider: "google" | "github" | "microsoft";
+  providerUserId: string;
+  providerEmail: string | null;
+  accessToken: string | null;
+  refreshToken: string | null;
+  tokenExpiresAt: number | null;
+  createdAt: number;
+  updatedAt: number;
+}
+
+export interface AuditLog {
+  id: string;
+  userId: string | null;
+  action: string;
+  resourceType: string | null;
+  resourceId: string | null;
+  ipAddress: string | null;
+  userAgent: string | null;
+  details: string | null;
+  createdAt: number;
+}
+
+// JWT Payload - compatible with jose library
+export interface JWTPayload {
+  sub: string; // user id
+  username: string;
+  email: string;
+  iat: number;
+  exp: number;
+  jti: string; // session id
+  [key: string]: unknown; // Index signature for jose compatibility
+}
+
+// API Request/Response types
+export interface RegisterRequest {
+  username: string;
+  email: string;
+  password: string;
+}
+
+export interface LoginRequest {
+  email: string;
+  password: string;
+}
+
+export interface AuthResponse {
+  user: {
+    id: string;
+    username: string;
+    email: string;
+    emailVerified: boolean;
+  };
+  token: string;
+}
+
+// Error types
+export class AuthError {
+  readonly _tag = "AuthError";
+  constructor(
+    readonly code: string,
+    readonly message: string,
+    readonly cause?: unknown
+  ) {}
+}
+
+export class ValidationError {
+  readonly _tag = "ValidationError";
+  constructor(
+    readonly field: string,
+    readonly message: string
+  ) {}
+}
+
+export class DatabaseError {
+  readonly _tag = "DatabaseError";
+  constructor(
+    readonly message: string,
+    readonly cause?: unknown
+  ) {}
+}

package/src/templates/claude/agents/coolify-deploy.md

@@ -25,7 +25,7 @@ COOLIFY_API_KEY=your_api_key_here
 
 Verify configuration:
 ```bash
-node src/scripts/coolify-status.js
+node node_modules/myaidev-method/src/scripts/coolify-status.js
 ```
 
 ## Operational Patterns (Claude Code 2.0)
@@ -37,10 +37,10 @@ node src/scripts/coolify-status.js
 
 ```bash
 # Deploy application
-node src/scripts/coolify-deploy-app.js --name myapp --repo https://github.com/user/repo
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js --name myapp --repo https://github.com/user/repo
 
 # Check status
-node src/scripts/coolify-list-resources.js --type applications
+node node_modules/myaidev-method/src/scripts/coolify-list-resources.js --type applications
 ```
 
 ### Pattern 2: Extended Thinking
@@ -69,13 +69,13 @@ Main agent → Deploy subagent (App A) → Verify subagent
 
 ```bash
 # Step 1: Verify Coolify connectivity
-node src/scripts/coolify-status.js
+node node_modules/myaidev-method/src/scripts/coolify-status.js
 
 # Step 2: List available servers
-node src/scripts/coolify-list-resources.js --type servers
+node node_modules/myaidev-method/src/scripts/coolify-list-resources.js --type servers
 
 # Step 3: Deploy application
-node src/scripts/coolify-deploy-app.js \
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js \
   --name "myapp" \
   --repo "https://github.com/user/myapp" \
   --branch "main" \
@@ -86,7 +86,7 @@ node src/scripts/coolify-deploy-app.js \
   --domain "myapp.example.com"
 
 # Step 4: Monitor deployment
-node src/scripts/coolify-watch-deployment.js --uuid "app-uuid"
+node node_modules/myaidev-method/src/scripts/coolify-watch-deployment.js --uuid "app-uuid"
 
 # Step 5: Verify deployment
 curl https://myapp.example.com
@@ -118,14 +118,14 @@ curl https://myapp.example.com
 
 ```bash
 # Deploy to staging
-node src/scripts/coolify-deploy-app.js \
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js \
   --name "myapp-staging" \
   --branch "develop" \
   --env-file ".env.staging"
 
 # Deploy to production (with approval gate)
 # Agent prompts: "Ready to deploy to production? (y/n)"
-node src/scripts/coolify-deploy-app.js \
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js \
   --name "myapp-prod" \
   --branch "main" \
   --env-file ".env.production"
@@ -139,23 +139,23 @@ All scripts use credentials from `.env` automatically:
 
 ```bash
 # Resource Management
-node src/scripts/coolify-list-resources.js [--type servers|projects|applications|databases]
-node src/scripts/coolify-status.js
-node src/scripts/coolify-server-info.js --uuid <server-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-list-resources.js [--type servers|projects|applications|databases]
+node node_modules/myaidev-method/src/scripts/coolify-status.js
+node node_modules/myaidev-method/src/scripts/coolify-server-info.js --uuid <server-uuid>
 
 # Application Deployment
-node src/scripts/coolify-deploy-app.js [options]
-node src/scripts/coolify-watch-deployment.js --uuid <app-uuid>
-node src/scripts/coolify-restart-app.js --uuid <app-uuid>
-node src/scripts/coolify-stop-app.js --uuid <app-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js [options]
+node node_modules/myaidev-method/src/scripts/coolify-watch-deployment.js --uuid <app-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-restart-app.js --uuid <app-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-stop-app.js --uuid <app-uuid>
 
 # Environment Variables
-node src/scripts/coolify-set-env.js --uuid <app-uuid> --file .env.production
-node src/scripts/coolify-get-env.js --uuid <app-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-set-env.js --uuid <app-uuid> --file .env.production
+node node_modules/myaidev-method/src/scripts/coolify-get-env.js --uuid <app-uuid>
 
 # Logs & Debugging
-node src/scripts/coolify-logs.js --uuid <app-uuid> [--follow]
-node src/scripts/coolify-deployment-report.js --uuid <app-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-logs.js --uuid <app-uuid> [--follow]
+node node_modules/myaidev-method/src/scripts/coolify-deployment-report.js --uuid <app-uuid>
 ```
 
 ### Using Coolify Utils Library
@@ -249,7 +249,7 @@ const result = await coolify.waitForDeployment(uuid, {
 **Issue: API Authentication Failed**
 ```bash
 # Verify API key
-node src/scripts/coolify-status.js
+node node_modules/myaidev-method/src/scripts/coolify-status.js
 
 # Check .env file
 cat .env | grep COOLIFY
@@ -261,47 +261,47 @@ curl -H "Authorization: Bearer $COOLIFY_API_KEY" https://coolify.myai1.ai/api/v1
 **Issue: Deployment Stuck or Failed**
 ```bash
 # Check deployment logs
-node src/scripts/coolify-logs.js --uuid <app-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-logs.js --uuid <app-uuid>
 
 # Get deployment status
-node src/scripts/coolify-deployment-report.js --uuid <app-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-deployment-report.js --uuid <app-uuid>
 
 # Restart application
-node src/scripts/coolify-restart-app.js --uuid <app-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-restart-app.js --uuid <app-uuid>
 ```
 
 **Issue: Application Not Accessible**
 ```bash
 # Verify domains configured
-node src/scripts/coolify-list-resources.js --type applications | grep -A 5 "myapp"
+node node_modules/myaidev-method/src/scripts/coolify-list-resources.js --type applications | grep -A 5 "myapp"
 
 # Check server status
-node src/scripts/coolify-server-info.js --uuid <server-uuid>
+node node_modules/myaidev-method/src/scripts/coolify-server-info.js --uuid <server-uuid>
 
 # Verify application running
-node src/scripts/coolify-logs.js --uuid <app-uuid> --tail 50
+node node_modules/myaidev-method/src/scripts/coolify-logs.js --uuid <app-uuid> --tail 50
 ```
 
 ### Diagnostic Workflow
 
 1. **Check System Status**
    ```bash
-   node src/scripts/coolify-status.js
+   node node_modules/myaidev-method/src/scripts/coolify-status.js
    ```
 
 2. **Verify Application State**
    ```bash
-   node src/scripts/coolify-list-resources.js --type applications
+   node node_modules/myaidev-method/src/scripts/coolify-list-resources.js --type applications
    ```
 
 3. **Analyze Logs**
    ```bash
-   node src/scripts/coolify-logs.js --uuid <uuid> --follow
+   node node_modules/myaidev-method/src/scripts/coolify-logs.js --uuid <uuid> --follow
    ```
 
 4. **Generate Deployment Report**
    ```bash
-   node src/scripts/coolify-deployment-report.js --uuid <uuid> --output report.json
+   node node_modules/myaidev-method/src/scripts/coolify-deployment-report.js --uuid <uuid> --output report.json
    ```
 
 ## Security Best Practices
@@ -349,7 +349,7 @@ fi
 /myai-content-writer "10 Tips for Productivity"
 
 # Coolify-deploy agent deploys WordPress if needed
-node src/scripts/coolify-deploy-app.js --name wordpress --template wordpress
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js --name wordpress --template wordpress
 
 # WordPress-admin agent publishes content
 /myai-wordpress-publish content.md
@@ -370,7 +370,7 @@ node src/scripts/coolify-deploy-app.js --name wordpress --template wordpress
 
 ```bash
 # List servers with metrics
-node src/scripts/coolify-list-resources.js --type servers --detailed
+node node_modules/myaidev-method/src/scripts/coolify-list-resources.js --type servers --detailed
 
 # Agent analyzes:
 # - Server load
@@ -397,7 +397,7 @@ node src/scripts/coolify-list-resources.js --type servers --detailed
 
 ```bash
 # Real-time deployment monitoring
-node src/scripts/coolify-watch-deployment.js --uuid <uuid>
+node node_modules/myaidev-method/src/scripts/coolify-watch-deployment.js --uuid <uuid>
 
 # Output:
 # [12:00:00] 🚀 Deployment started
@@ -411,7 +411,7 @@ node src/scripts/coolify-watch-deployment.js --uuid <uuid>
 
 ```bash
 # System-wide health check
-node src/scripts/coolify-status.js --comprehensive
+node node_modules/myaidev-method/src/scripts/coolify-status.js --comprehensive
 
 # Per-application health check
 curl -I https://myapp.example.com/health
@@ -426,13 +426,13 @@ curl -I https://myapp.example.com/health
 **Agent workflow**:
 ```bash
 # 1. Verify connectivity
-node src/scripts/coolify-status.js
+node node_modules/myaidev-method/src/scripts/coolify-status.js
 
 # 2. List available servers
-node src/scripts/coolify-list-resources.js --type servers
+node node_modules/myaidev-method/src/scripts/coolify-list-resources.js --type servers
 
 # 3. Deploy application
-node src/scripts/coolify-deploy-app.js \
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js \
   --name "nextjs-app" \
   --repo "https://github.com/user/nextjs-app" \
   --branch "main" \
@@ -442,7 +442,7 @@ node src/scripts/coolify-deploy-app.js \
   --server-uuid "ho4k04okko0wks8g0gsccww4"
 
 # 4. Watch deployment
-node src/scripts/coolify-watch-deployment.js --uuid "<new-app-uuid>"
+node node_modules/myaidev-method/src/scripts/coolify-watch-deployment.js --uuid "<new-app-uuid>"
 ```
 
 ### Example 2: Update Environment Variables
@@ -452,16 +452,16 @@ node src/scripts/coolify-watch-deployment.js --uuid "<new-app-uuid>"
 **Agent workflow**:
 ```bash
 # 1. Find application
-node src/scripts/coolify-list-resources.js --type applications | grep myapp
+node node_modules/myaidev-method/src/scripts/coolify-list-resources.js --type applications | grep myapp
 
 # 2. Update environment variable
-node src/scripts/coolify-set-env.js \
+node node_modules/myaidev-method/src/scripts/coolify-set-env.js \
   --uuid "<app-uuid>" \
   --key "API_KEY" \
   --value "<new-api-key>"
 
 # 3. Restart application to apply changes
-node src/scripts/coolify-restart-app.js --uuid "<app-uuid>"
+node node_modules/myaidev-method/src/scripts/coolify-restart-app.js --uuid "<app-uuid>"
 ```
 
 ### Example 3: Deploy Database
@@ -471,7 +471,7 @@ node src/scripts/coolify-restart-app.js --uuid "<app-uuid>"
 **Agent workflow**:
 ```bash
 # 1. Create database
-node src/scripts/coolify-create-database.js \
+node node_modules/myaidev-method/src/scripts/coolify-create-database.js \
   --name "myapp-db" \
   --type "postgresql" \
   --version "16" \
@@ -479,10 +479,10 @@ node src/scripts/coolify-create-database.js \
   --project-uuid "<project-uuid>"
 
 # 2. Get connection string
-node src/scripts/coolify-get-database-connection.js --uuid "<db-uuid>"
+node node_modules/myaidev-method/src/scripts/coolify-get-database-connection.js --uuid "<db-uuid>"
 
 # 3. Update application with DB connection
-node src/scripts/coolify-set-env.js \
+node node_modules/myaidev-method/src/scripts/coolify-set-env.js \
   --uuid "<app-uuid>" \
   --key "DATABASE_URL" \
   --value "<connection-string>"
@@ -494,21 +494,21 @@ node src/scripts/coolify-set-env.js \
 
 ```bash
 # Deploy to blue environment
-node src/scripts/coolify-deploy-app.js --name "myapp-blue" --branch "release"
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js --name "myapp-blue" --branch "release"
 
 # Test blue environment
 curl https://blue.myapp.com/health
 
 # Switch traffic (update DNS or proxy)
 # Stop green environment
-node src/scripts/coolify-stop-app.js --uuid "<green-uuid>"
+node node_modules/myaidev-method/src/scripts/coolify-stop-app.js --uuid "<green-uuid>"
 ```
 
 ### Pattern: Canary Deployment
 
 ```bash
 # Deploy canary version
-node src/scripts/coolify-deploy-app.js \
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js \
   --name "myapp-canary" \
   --branch "canary" \
   --domain "canary.myapp.com"
@@ -522,12 +522,12 @@ node src/scripts/coolify-deploy-app.js \
 
 ```bash
 # Deploy to US server
-node src/scripts/coolify-deploy-app.js \
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js \
   --name "myapp-us" \
   --server-uuid "<us-server-uuid>"
 
 # Deploy to EU server
-node src/scripts/coolify-deploy-app.js \
+node node_modules/myaidev-method/src/scripts/coolify-deploy-app.js \
   --name "myapp-eu" \
   --server-uuid "<eu-server-uuid>"
 

package/src/templates/claude/agents/payloadcms-publish.md

@@ -29,23 +29,24 @@ token_target: 2800
 
 ### Step 1: Configuration Validation
 ```
-1. Check PayloadCMS credentials in environment or config
+1. Check PayloadCMS credentials in environment (.env file)
 2. Verify required fields:
-   - PAYLOAD_URL: API endpoint
-   - PAYLOAD_EMAIL: user email
-   - PAYLOAD_PASSWORD: user password
-   - PAYLOAD_COLLECTION: default collection name (optional)
-3. If missing → prompt user to run /myai-configure payloadcms
+   - PAYLOADCMS_URL: PayloadCMS API endpoint
+   - PAYLOADCMS_EMAIL: User email for authentication
+   - PAYLOADCMS_PASSWORD: User password for authentication
+3. If missing → prompt user to configure .env file
+   (See .env.example for template)
 ```
 
 ### Step 2: Authentication
 ```
-1. Call authenticatePayload(url, email, password)
-2. Receive JWT token for API requests
-3. Handle auth errors:
-   - Invalid credentials → verify config
-   - Network errors → check URL accessibility
-   - Server errors → verify PayloadCMS instance health
+1. Authenticate using email/password to obtain JWT token
+2. POST to {PAYLOADCMS_URL}/api/users/login with credentials
+3. Extract JWT token from response (used for all subsequent API calls)
+4. Handle auth errors:
+   - Invalid credentials → verify PAYLOADCMS_EMAIL and PAYLOADCMS_PASSWORD
+   - Network errors → check PAYLOADCMS_URL accessibility
+   - Server errors → verify PayloadCMS instance is running
 ```
 
 ### Step 3: Content Processing
@@ -123,12 +124,39 @@ Agent:
 
 ```
 1. Read(markdown_file) → Extract content
-2. authenticatePayload() → Get JWT token
-3. markdownToLexical() → Convert format
-4. publishToPayload() → Create/update document
-5. Report success with URLs
+2. Use Bash tool to execute publishing script:
+   node node_modules/myaidev-method/src/scripts/payloadcms-publish.js [file] [options]
+3. The script handles:
+   - Authentication (JWT token from .env credentials)
+   - Markdown to Lexical conversion
+   - Document creation/update via API
+4. Report success with URLs from script output
 ```
 
-## Configuration Integration
+**Alternative**: Use PayloadCMSUtils library directly if you prefer programmatic control:
+```
+import { PayloadCMSUtils } from 'node_modules/myaidev-method/src/lib/payloadcms-utils.js'
+```
+
+## Configuration Setup
+
+### Required Environment Variables
+
+Add to your `.env` file:
+
+```bash
+PAYLOADCMS_URL=https://your-payloadcms-site.com
+PAYLOADCMS_EMAIL=your-email@example.com
+PAYLOADCMS_PASSWORD=your-password
+```
+
+### Authentication Flow
+
+1. **Email/Password Login**: Agent authenticates using credentials from .env
+2. **JWT Token**: Receives JWT token from PayloadCMS `/api/users/login` endpoint
+3. **API Requests**: Uses JWT token in `Authorization: JWT {token}` header for all API calls
+4. **Token Expiry**: Automatically re-authenticates if token expires
+
+### No API Keys Required
 
-Use `/myai-configure` to set up PayloadCMS credentials before publishing.
+PayloadCMS integration uses standard user authentication (email/password) to obtain JWT tokens. No separate API keys or application passwords needed.

package/src/templates/codex/commands/myai-astro-publish.md

@@ -1,8 +1,14 @@
 # Astro Content Publisher
 
-Publish markdown content to Astro static site with content collections support and git workflow: $ARGUMENTS
+Use the Task tool with subagent_type="astro-publish" to publish the markdown file provided in the arguments to Astro.
+
+Pass all command arguments to the agent, including the file path and any flags (--collection, --pages, --project, --branch, --no-push, --dry-run).
+
+The agent will handle frontmatter transformation, content collection validation, and git workflow automation for Astro static sites.
 
-Invoke the Astro publishing agent to transform frontmatter, validate schemas, and deploy via git.
+## Overview
+
+Publish markdown content to Astro static site with content collections support and git workflow: $ARGUMENTS
 
 ## Usage Examples
 

package/src/templates/codex/commands/myai-content-writer.md

@@ -1,8 +1,14 @@
 # Professional Content Writer
 
-Create comprehensive, well-researched content based on the provided topic: $ARGUMENTS
+Use the Task tool with subagent_type="content-writer" to create SEO-optimized content based on the provided topic.
+
+Pass all command arguments to the agent, including the topic, word count, tone, audience, SEO keywords, and publish_to_wordpress flag.
+
+The agent will handle research, planning, writing, optimization, and formatting with professional content creation expertise.
 
-You are a professional content writer specializing in creating high-quality, engaging, and SEO-optimized content.
+## Overview
+
+Create comprehensive, well-researched content based on the provided topic: $ARGUMENTS
 
 ## Core Competencies
 

package/src/templates/codex/commands/myai-coolify-deploy.md

@@ -1,8 +1,14 @@
 # Coolify Deployment Manager
 
-Execute Coolify deployment operations: $ARGUMENTS
+Use the Task tool with subagent_type="coolify-deploy" to execute Coolify deployment operations provided in the arguments.
+
+Pass all command arguments to the agent, including the operation type (deploy, status, list, logs, restart, env) and any configuration flags.
+
+The agent will handle Coolify API communication, deployment orchestration, and infrastructure management operations.
 
-Launch the Coolify deployment specialist agent for application deployment and infrastructure management.
+## Overview
+
+Execute Coolify deployment operations: $ARGUMENTS
 
 ## Available Operations
 

package/src/templates/codex/commands/myai-dev-architect.md

@@ -1,8 +1,14 @@
 # System Architecture Design
 
-Design scalable system architecture using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="MyAIDev Architect" to design scalable system architecture based on the provided requirements.
+
+Pass all command arguments to the agent, including the task description and any flags (--existing-code, --tech-stack, --output-dir).
+
+The agent will handle requirements analysis, architecture design, diagram creation, API specifications, and technology recommendations using MyAIDev Method's SPARC workflow.
 
-Invoke the MyAIDev Architect agent to create comprehensive system designs with architecture diagrams, API specifications, and technology recommendations.
+## Overview
+
+Design scalable system architecture using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## What It Does
 

package/src/templates/codex/commands/myai-dev-code.md

@@ -1,8 +1,14 @@
 # Feature Implementation
 
-Implement features and write production-ready code using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="MyAIDev Coder" to implement features based on the provided requirements.
+
+Pass all command arguments to the agent, including the task description and any flags (--architecture, --test-driven, --output-dir).
+
+The agent will handle implementation planning, clean code generation, SOLID principles application, error handling, and test creation using MyAIDev Method's SPARC workflow.
 
-Invoke the MyAIDev Coder agent to implement features based on architecture specifications, following best practices and clean code principles.
+## Overview
+
+Implement features and write production-ready code using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## What It Does
 

package/src/templates/codex/commands/myai-dev-docs.md

@@ -1,8 +1,14 @@
 # Comprehensive Documentation
 
-Generate comprehensive documentation using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="MyAIDev Documenter" to generate comprehensive documentation based on the provided requirements.
+
+Pass all command arguments to the agent, including the task description and any flags (--type, --format, --output-dir).
+
+The agent will handle documentation generation including API references, user guides, architecture docs, code examples, and visual diagrams using MyAIDev Method's SPARC workflow.
 
-Invoke the MyAIDev Documenter agent to create API documentation, user guides, architecture docs, and technical specifications.
+## Overview
+
+Generate comprehensive documentation using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## What It Does