myaidev-method 0.3.4 → 0.3.5

package/src/scripts/wordpress/publish-to-wordpress.js

@@ -21,144 +21,144 @@ const args = process.argv.slice(2);
 const filePath = args[0];
 const statusIndex = args.indexOf("--status");
 const requestedStatus =
-	statusIndex !== -1 && args[statusIndex + 1] ? args[statusIndex + 1] : "draft";
+  statusIndex !== -1 && args[statusIndex + 1] ? args[statusIndex + 1] : "draft";
 
 if (!filePath) {
-	console.error("Error: File path is required");
-	console.error(
-		"Usage: node publish-to-wordpress.js <file-path> [--status draft|publish]",
-	);
-	process.exit(1);
+  console.error("Error: File path is required");
+  console.error(
+    "Usage: node publish-to-wordpress.js <file-path> [--status draft|publish]",
+  );
+  process.exit(1);
 }
 
 // Validate WordPress configuration
 if (
-	!process.env.WORDPRESS_URL ||
-	!process.env.WORDPRESS_USERNAME ||
-	!process.env.WORDPRESS_APP_PASSWORD
+  !process.env.WORDPRESS_URL ||
+  !process.env.WORDPRESS_USERNAME ||
+  !process.env.WORDPRESS_APP_PASSWORD
 ) {
-	console.error("Error: WordPress configuration is incomplete");
-	console.error("Required environment variables:");
-	console.error("  - WORDPRESS_URL");
-	console.error("  - WORDPRESS_USERNAME");
-	console.error("  - WORDPRESS_APP_PASSWORD");
-	console.error(
-		"\nRun /myai-configure wordpress to set up your WordPress connection",
-	);
-	process.exit(1);
+  console.error("Error: WordPress configuration is incomplete");
+  console.error("Required environment variables:");
+  console.error("  - WORDPRESS_URL");
+  console.error("  - WORDPRESS_USERNAME");
+  console.error("  - WORDPRESS_APP_PASSWORD");
+  console.error(
+    "\nRun /myai-configurator wordpress to set up your WordPress connection",
+  );
+  process.exit(1);
 }
 
 async function publishToWordPress() {
-	try {
-		// Read and parse markdown file
-		const absolutePath = resolve(filePath);
-		const fileContent = readFileSync(absolutePath, "utf-8");
-		const { data: frontmatter, content } = matter(fileContent);
-
-		console.log("📄 Processing file:", filePath);
-		console.log("📋 Title:", frontmatter.title || "No title");
-
-		// Extract interactive blocks before markdown conversion
-		// const { markdown: cleanMarkdown, interactiveBlocks } =
-		// 	GutenbergConverter.extractInteractiveBlocks(content);
-
-		// if (interactiveBlocks.length > 0) {
-		// 	console.log(
-		// 		`   Interactive blocks: ${interactiveBlocks.length} found`,
-		// 	);
-		// }
-
-		// Convert markdown to HTML using marked (preserves placeholders)
-		const html = marked.parse(content);
-
-		// Convert HTML to Gutenberg blocks
-		let htmlContent = GutenbergConverter.htmlToGutenberg(html);
-
-		// Restore interactive blocks as raw HTML blocks
-		// if (interactiveBlocks.length > 0) {
-		// 	htmlContent = GutenbergConverter.restoreInteractiveBlocks(
-		// 		htmlContent,
-		// 		interactiveBlocks,
-		// 	);
-		// }
-
-		// Prepare WordPress configuration
-		const config = {
-			endpoint: {
-				url: process.env.WORDPRESS_URL,
-				api_version: "wp/v2",
-				authentication: {
-					username: process.env.WORDPRESS_USERNAME,
-					password: process.env.WORDPRESS_APP_PASSWORD,
-				},
-			},
-			defaults: {
-				post_status: requestedStatus,
-				format: "standard",
-				comment_status: "open",
-				ping_status: "open",
-			},
-		};
-
-		// Initialize WordPress client
-		const wp = new WordPressMCP(config);
-
-		// Prepare post data
-		const postParams = {
-			title: frontmatter.title || "Untitled",
-			content: htmlContent,
-			status: requestedStatus,
-			excerpt: frontmatter.meta_description || "",
-			slug: frontmatter.slug || "",
-			use_gutenberg: process.env.USE_GUTENBERG === "true",
-			// Note: Tags and categories require ID mapping which will be added in future versions
-		};
-
-		console.log("🚀 Publishing to WordPress...");
-		console.log("   URL:", process.env.WORDPRESS_URL);
-		console.log("   Status:", requestedStatus);
-		console.log(
-			"   Format:",
-			postParams.use_gutenberg ? "Gutenberg" : "Classic",
-		);
-
-		// Create the post
-		const result = await wp.createPost(postParams);
-
-		// Success!
-		console.log("\n✅ Successfully published to WordPress!");
-		console.log("\n📄 Post Details:");
-		console.log("   Post ID:", result.id);
-		console.log("   Title:", result.title.rendered);
-		console.log("   Status:", result.status);
-		console.log("   Slug:", result.slug);
-
-		console.log("\n🔗 URLs:");
-		console.log("   View:", result.link);
-		console.log(
-			"   Edit:",
-			`${process.env.WORDPRESS_URL}/wp-admin/post.php?post=${result.id}&action=edit`,
-		);
-
-		return result;
-	} catch (error) {
-		console.error("\n❌ Error publishing to WordPress:");
-		console.error(error.message);
-
-		if (error.message.includes("401")) {
-			console.error("\n🔑 Authentication failed. Please check:");
-			console.error("   1. Your WordPress username is correct");
-			console.error("   2. Your Application Password is valid");
-			console.error("   3. Application Passwords are enabled on your site");
-		} else if (error.message.includes("404")) {
-			console.error("\n🌐 WordPress site not found. Please check:");
-			console.error("   1. Your WORDPRESS_URL is correct");
-			console.error("   2. The site is accessible");
-			console.error("   3. The REST API is enabled");
-		}
-
-		process.exit(1);
-	}
+  try {
+    // Read and parse markdown file
+    const absolutePath = resolve(filePath);
+    const fileContent = readFileSync(absolutePath, "utf-8");
+    const { data: frontmatter, content } = matter(fileContent);
+
+    console.log("📄 Processing file:", filePath);
+    console.log("📋 Title:", frontmatter.title || "No title");
+
+    // Extract interactive blocks before markdown conversion
+    // const { markdown: cleanMarkdown, interactiveBlocks } =
+    // 	GutenbergConverter.extractInteractiveBlocks(content);
+
+    // if (interactiveBlocks.length > 0) {
+    // 	console.log(
+    // 		`   Interactive blocks: ${interactiveBlocks.length} found`,
+    // 	);
+    // }
+
+    // Convert markdown to HTML using marked (preserves placeholders)
+    const html = marked.parse(content);
+
+    // Convert HTML to Gutenberg blocks
+    let htmlContent = GutenbergConverter.htmlToGutenberg(html);
+
+    // Restore interactive blocks as raw HTML blocks
+    // if (interactiveBlocks.length > 0) {
+    // 	htmlContent = GutenbergConverter.restoreInteractiveBlocks(
+    // 		htmlContent,
+    // 		interactiveBlocks,
+    // 	);
+    // }
+
+    // Prepare WordPress configuration
+    const config = {
+      endpoint: {
+        url: process.env.WORDPRESS_URL,
+        api_version: "wp/v2",
+        authentication: {
+          username: process.env.WORDPRESS_USERNAME,
+          password: process.env.WORDPRESS_APP_PASSWORD,
+        },
+      },
+      defaults: {
+        post_status: requestedStatus,
+        format: "standard",
+        comment_status: "open",
+        ping_status: "open",
+      },
+    };
+
+    // Initialize WordPress client
+    const wp = new WordPressMCP(config);
+
+    // Prepare post data
+    const postParams = {
+      title: frontmatter.title || "Untitled",
+      content: htmlContent,
+      status: requestedStatus,
+      excerpt: frontmatter.meta_description || "",
+      slug: frontmatter.slug || "",
+      use_gutenberg: process.env.USE_GUTENBERG === "true",
+      // Note: Tags and categories require ID mapping which will be added in future versions
+    };
+
+    console.log("🚀 Publishing to WordPress...");
+    console.log("   URL:", process.env.WORDPRESS_URL);
+    console.log("   Status:", requestedStatus);
+    console.log(
+      "   Format:",
+      postParams.use_gutenberg ? "Gutenberg" : "Classic",
+    );
+
+    // Create the post
+    const result = await wp.createPost(postParams);
+
+    // Success!
+    console.log("\n✅ Successfully published to WordPress!");
+    console.log("\n📄 Post Details:");
+    console.log("   Post ID:", result.id);
+    console.log("   Title:", result.title.rendered);
+    console.log("   Status:", result.status);
+    console.log("   Slug:", result.slug);
+
+    console.log("\n🔗 URLs:");
+    console.log("   View:", result.link);
+    console.log(
+      "   Edit:",
+      `${process.env.WORDPRESS_URL}/wp-admin/post.php?post=${result.id}&action=edit`,
+    );
+
+    return result;
+  } catch (error) {
+    console.error("\n❌ Error publishing to WordPress:");
+    console.error(error.message);
+
+    if (error.message.includes("401")) {
+      console.error("\n🔑 Authentication failed. Please check:");
+      console.error("   1. Your WordPress username is correct");
+      console.error("   2. Your Application Password is valid");
+      console.error("   3. Application Passwords are enabled on your site");
+    } else if (error.message.includes("404")) {
+      console.error("\n🌐 WordPress site not found. Please check:");
+      console.error("   1. Your WORDPRESS_URL is correct");
+      console.error("   2. The site is accessible");
+      console.error("   3. The REST API is enabled");
+    }
+
+    process.exit(1);
+  }
 }
 
 // Run the publisher

package/src/templates/claude/CLAUDE.md

@@ -27,20 +27,16 @@ Skills are the primary delivery mechanism. Each skill is a self-contained orches
 
 ### Content Creation
 - `content-writer` - Multi-agent pipeline (research, plan, write, SEO, edit, visuals)
-- `content-rules-setup` - Interactive brand voice configuration
-- `content-verifier` - Content uniqueness and quality verification
-- `content-coordinator` - Batch content verification and publishing
-- `content-enrichment` - Enrich articles with real-time data and visuals
+- `content-rules-config` - Interactive brand voice configuration
+- `proprietary-content-verifier` - Content uniqueness and quality verification
+- `content-production-coordinator` - Batch content verification and publishing
+- `myai-content-enrichment` - Enrich articles with real-time data and visuals
 
 ### Publishing
-- `wordpress-publisher` - WordPress REST API publishing
-- `payloadcms-publisher` - PayloadCMS with Lexical format
-- `docusaurus-publisher` - Docusaurus with sidebar config
-- `mintlify-publisher` - Mintlify with navigation updates
-- `astro-publisher` - Astro content collections
+- `content-publisher` - Platform-detecting publisher (WordPress, PayloadCMS, Astro, Docusaurus, Mintlify)
 
 ### Visual & Media
-- `visual-generator` - AI image/video generation (Gemini, DALL-E, FLUX, Veo)
+- `myai-visual-generator` - AI image/video generation (Gemini, DALL-E, FLUX, Veo) with fal.ai MCP model discovery
 
 ### Deployment & Infrastructure
 - `deployer` - Multi-environment deployment (dev/staging/prod)
@@ -55,7 +51,7 @@ Skills are the primary delivery mechanism. Each skill is a self-contained orches
 - `security-auditor` - Compliance auditing (PCI-DSS, GDPR, SOC 2)
 
 ### Skill Development
-- `skill-builder` - Guided skill creation with concept discovery, iterative refinement, testing, and marketplace submission
+- `myai-skill-builder` - Guided skill creation with concept discovery, iterative refinement, testing, and marketplace submission
 - `skill-contributor` - Quick skill scaffolding and marketplace submission
 
 ### Configuration
@@ -64,7 +60,7 @@ Skills are the primary delivery mechanism. Each skill is a self-contained orches
 ## Content Customization
 
 - **content-rules.md** - Brand voice and writing guidelines
-  - Run the `content-rules-setup` skill to generate this interactively
+  - Run the `content-rules-config` skill to generate this interactively
 
 ## Platform Configuration
 
@@ -84,6 +80,7 @@ PAYLOADCMS_PASSWORD=your-password
 # Visual APIs
 GOOGLE_API_KEY=your-key
 OPENAI_API_KEY=your-key
+FAL_KEY=your-key
 
 # Coolify
 COOLIFY_URL=https://coolify.your-server.com
@@ -100,6 +97,16 @@ node .myaidev-method/scripts/wordpress-health-check.js
 node .myaidev-method/scripts/coolify-deploy-app.js --name myapp
 ```
 
+## MCP Servers
+
+The following MCP servers are auto-configured during init:
+
+| Server | Purpose | Env Var Required |
+|--------|---------|------------------|
+| `fal-ai` | Visual generation model discovery, pricing, and generation across 600+ models | `FAL_KEY` |
+
+MCP servers activate automatically when their required environment variable is set.
+
 ## Project Structure
 
 ```

package/hooks/hooks.json

@@ -1,26 +0,0 @@
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "Write|Edit",
-        "hooks": [
-          {
-            "type": "prompt",
-            "prompt": "If the file written/edited is a content markdown file (in content-output/ or content-queue/), verify it has valid frontmatter with title, description, and date fields. Report any missing required fields."
-          }
-        ]
-      }
-    ],
-    "Stop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "prompt",
-            "prompt": "Before finishing, check if there are any unsaved content drafts in content-output/ that haven't been published. If found, remind the user about pending drafts."
-          }
-        ]
-      }
-    ]
-  }
-}

package/skills/content-coordinator/SKILL.md

@@ -1,130 +0,0 @@
----
-name: content-coordinator
-description: Orchestrates content verification and multi-platform publishing workflows with batch processing. Use when publishing multiple content files or running content production pipelines.
-argument-hint: "[directory] [--dry-run] [--force] [--verbose] [--platform wordpress|payloadcms]"
-allowed-tools: [Read, Write, Edit, WebSearch, WebFetch, Task, Bash, Glob, Grep, AskUserQuestion]
-disable-model-invocation: true
----
-
-# Content Production Coordinator
-
-You are the **Content Production Coordinator** — orchestrating content verification and publishing workflows. You manage batch content processing, quality verification, and multi-platform publishing.
-
-## Arguments
-
-Parse from: `$ARGUMENTS`
-
-- `[directory]` → Path to content queue directory (default: `./content-queue/`)
-- `--dry-run` → Verify only, don't publish
-- `--force` → Skip confirmation prompts
-- `--verbose` → Detailed progress output
-- `--platform` → Target platform (default: from frontmatter)
-- `--output-dir` → Report directory
-
-## Content Queue Format
-
-Each markdown file in the queue should have:
-
-```markdown
----
-title: "Article Title"
-content_type: article
-target_platform: wordpress
-status: pending
-priority: normal
-references:
-  - "https://source1.com"
-goals:
-  - "Primary goal"
----
-
-## Proprietary Content
-
-[Unique content to be verified]
-
-## Supporting Content
-
-[Additional context]
-```
-
-## Workflow
-
-### Phase 1: Discovery
-1. Scan content directory for `.md` files
-2. Parse frontmatter from each file
-3. Filter by `status: pending`
-4. Sort by priority
-
-### Phase 2: Verification
-For each content file, spawn a verification subagent:
-
-```
-Task(subagent_type: "general-purpose")
-Prompt: Verify content uniqueness and quality
-```
-
-**Verification checks:**
-- Knowledge redundancy (is this unique or commodity info?)
-- Content quality (depth, originality, value-add)
-- AI detection characteristics
-- Minimum length requirements
-
-**Scoring:** High | Medium | Low | Minimal redundancy
-
-### Phase 3: Categorization
-Based on verification results:
-- **Ready for Publishing:** Low/Minimal redundancy, passes quality
-- **Needs Review:** High/Medium redundancy, quality concerns
-
-### Phase 4: Report Generation
-Create timestamped report:
-```
-content-reports/report-{timestamp}.md
-```
-
-Contents:
-- Summary statistics
-- Per-file verification results
-- Recommendations
-- Publishing readiness status
-
-### Phase 5: Publishing (unless --dry-run)
-For approved content:
-1. Confirm with user (unless --force)
-2. Spawn publishing subagents in parallel per platform
-3. Track success/failure per file
-4. Report published URLs
-
-### Phase 6: Status Update
-- Update frontmatter `status` field: `pending` → `published` or `needs-review`
-- Add `published_at` timestamp
-- Add `published_url` if available
-
-## Parallel Processing
-
-- Verification: up to 3 files in parallel
-- Publishing: up to 5 files in parallel per platform
-- Use Task tool with run_in_background for parallelism
-
-## Error Handling
-
-- Verification failure → mark as needs-review, continue
-- Publishing failure → report error, don't update status
-- Partial batch failure → publish successful ones, report failures
-
-## Progress Reporting
-
-```
-Content Production Report
-═══════════════════════════
-Scanned: 8 files
-Verified: 8/8
-Ready: 6 files
-Needs Review: 2 files
-
-Publishing (6 files):
-  ✓ article-1.md → https://blog.com/article-1
-  ✓ article-2.md → https://blog.com/article-2
-  ✗ article-3.md → Error: API timeout
-  ...
-```

package/skills/content-enrichment/SKILL.md

@@ -1,80 +0,0 @@
----
-name: content-enrichment
-description: Enriches existing articles with real-time data, updated statistics, AI-generated visuals, and fresh references. Use when updating old content, adding citations to articles, refreshing outdated statistics, or enhancing posts with images and FAQ sections.
-argument-hint: "[file.md] [--add-images] [--update-stats] [--add-references]"
-allowed-tools: [Read, Write, Edit, WebSearch, WebFetch, Task, Bash, Glob, Grep]
----
-
-# Content Enrichment Agent
-
-You are a **Content Enrichment Specialist** — taking existing articles and enhancing them with current data, fresh references, updated statistics, and AI-generated visuals.
-
-## Arguments
-
-Parse from: `$ARGUMENTS`
-
-- `[file.md]` → Article to enrich (required)
-- `--add-images` → Generate AI visuals for the article
-- `--update-stats` → Find and update statistics/data points
-- `--add-references` → Add authoritative source links
-- `--add-faq` → Generate FAQ section from content
-- `--add-schema` → Add structured data recommendations
-- `--full` → All enrichment types
-- `--dry-run` → Show what would change without modifying
-
-## Enrichment Types
-
-### 1. Statistics Update (`--update-stats`)
-- Identify data points, percentages, year references in the article
-- Search for current versions of cited statistics
-- Replace outdated figures with current ones
-- Add citation sources
-
-### 2. Reference Addition (`--add-references`)
-- Identify claims without sources
-- Find authoritative references via WebSearch
-- Add inline citations or reference section
-- Verify links are accessible
-
-### 3. Visual Enhancement (`--add-images`)
-- Identify sections that benefit from visuals
-- Generate image descriptions/alt text
-- Create visual-plan.json for the visual-generator skill
-- Insert image placeholders in markdown
-
-### 4. FAQ Generation (`--add-faq`)
-- Extract key topics from article
-- Generate 5-8 relevant questions
-- Write concise answers from article content
-- Format as ## FAQ section with schema-ready markup
-
-### 5. Schema Recommendations (`--add-schema`)
-- Analyze content type (article, how-to, FAQ, review)
-- Suggest JSON-LD structured data
-- Generate schema markup snippet
-
-## Workflow
-
-1. Read the target article
-2. Parse frontmatter and content structure
-3. Identify enrichment opportunities based on flags
-4. Execute enrichments (web search for data, generate content)
-5. Apply changes to the article (preserving structure)
-6. Update frontmatter with `enriched_at` timestamp
-7. Report changes made
-
-## Output
-
-Modified article in-place with:
-- Updated frontmatter (`enriched_at`, `enrichment_types`)
-- Enhanced content sections
-- New sections added (FAQ, references) at appropriate locations
-- Image placeholders where visuals were planned
-
-## Quality Rules
-
-- Never remove existing content
-- Preserve author's voice and style
-- Only add verifiable, current information
-- Mark enriched sections with HTML comments if needed for tracking
-- Respect content-rules.md if present