myaidev-method 0.2.16 → 0.2.17

package/CHANGELOG.md

@@ -5,6 +5,39 @@ All notable changes to the MyAIDev Method package will be documented in this fil
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.17] - 2025-11-19
+
+### Added
+- **Custom Content Rules**: content-rules.md support for customizable content generation
+  - content-writer agent now checks for `content-rules.md` in project root
+  - Apply custom brand voice, formatting, SEO guidelines without modifying agents
+  - Gracefully continues if file doesn't exist (backward compatible)
+  - Added comprehensive `content-rules.example.md` template with examples
+  - Includes brand voice, formatting preferences, SEO requirements, required elements
+
+### Changed
+- **Content Writer Agent**: Enhanced with Phase 0 for loading custom rules
+  - Documented content-rules.md usage and examples
+  - Merged custom rules with default best practices
+  - Instructions for checking and applying custom rules
+
+### Documentation
+- **README.md**: Added "Content Writer Custom Rules" section with quick start
+- **USER_GUIDE.md**: Added "Customizing Content Generation (Recommended)" best practices
+- **package.json**: Added content-rules.example.md to published files
+
+### Benefits
+- ✅ No agent modification required for customization
+- ✅ Preserves agent updates when upgrading MyAIDev Method
+- ✅ Easy to version control (commit content-rules.md to git)
+- ✅ Project-specific customization
+- ✅ Backward compatible (works without file)
+
+### Testing
+- Verified with content-rules.md: Applied custom rules (emoji, Quick Takeaways, author signature)
+- Verified without content-rules.md: Used default professional standards
+- Both scenarios work correctly
+
 ## [0.2.16] - 2025-11-19
 
 ### Fixed

package/README.md

@@ -1000,14 +1000,66 @@ When SSH access is available, the WordPress admin agent can perform:
 
 You can customize agent behavior by editing their Markdown files after installation.
 
+### Content Writer Custom Rules (Recommended)
+
+The content-writer agent supports custom content generation rules via a `content-rules.md` file. This is the **recommended approach** for customizing content creation without modifying the agent itself.
+
+**Quick Start:**
+```bash
+# Copy the example template
+cp content-rules.example.md content-rules.md
+
+# Edit with your preferences
+nano content-rules.md
+```
+
+**What you can customize:**
+- Brand voice and tone
+- Writing style preferences
+- Formatting guidelines
+- SEO requirements
+- Required/optional content elements
+- Topics to avoid
+- Company-specific terminology
+
+**Example content-rules.md:**
+```markdown
+# Content Generation Rules
+
+## Brand Voice
+- Use conversational, friendly tone
+- Avoid jargon unless explaining technical concepts
+
+## Formatting Preferences
+- Keep paragraphs under 3 sentences
+- Use numbered lists for sequential steps
+
+## SEO Guidelines
+- Target keyword density: 1-2%
+- Include FAQ section for articles over 1000 words
+
+## Required Elements
+- Author bio at the end
+- Call-to-action in conclusion
+```
+
+**Benefits:**
+- ✅ No agent modification required
+- ✅ Preserves agent updates when upgrading
+- ✅ Easy to version control
+- ✅ Project-specific customization
+- ✅ Agent continues working if file doesn't exist
+
 ### Editing Agent Prompts
 
+For deeper customization, you can edit agent files directly:
+
 1. **Locate the agent file**:
    ```bash
    # Content writer agent
    .claude/agents/content-writer.md
-   
-   # WordPress admin agent  
+
+   # WordPress admin agent
    .claude/agents/wordpress-admin.md
    ```
 
@@ -1018,9 +1070,9 @@ You can customize agent behavior by editing their Markdown files after installat
    description: Your custom description
    tools: Read, Write, Edit, WebSearch, WebFetch, Task
    ---
-   
+
    Your custom agent prompt goes here...
-   
+
    ## Custom Instructions
    - Add your specific requirements
    - Modify the writing style

package/USER_GUIDE.md

@@ -1055,9 +1055,64 @@ ls -la .claude/commands/
 cat .claude/commands/myai-content-writer.md
 ```
 
-### Customizing Commands
+### Customizing Content Generation (Recommended)
 
-Edit command files to modify behavior:
+**Best Practice:** Use `content-rules.md` for content customization instead of editing agents directly.
+
+```bash
+# Copy the example template
+cp content-rules.example.md content-rules.md
+
+# Edit with your preferences
+nano content-rules.md
+```
+
+**Why use content-rules.md?**
+- ✅ No agent modification required
+- ✅ Preserves updates when upgrading MyAIDev Method
+- ✅ Easy to version control
+- ✅ Project-specific customization
+- ✅ Works even if file doesn't exist
+
+**Example content-rules.md:**
+
+```markdown
+# Content Generation Rules
+
+## Brand Voice
+- Use conversational, friendly tone
+- Avoid jargon unless explaining technical concepts
+- Include real-world examples
+
+## Formatting Preferences
+- Keep paragraphs under 3 sentences
+- Use numbered lists for sequential steps
+- Include code examples for technical content
+
+## SEO Guidelines
+- Target keyword density: 1-2%
+- Include FAQ section for articles over 1000 words
+- Add "Related Resources" section at the end
+
+## Required Elements
+- Author bio at the end
+- Call-to-action in conclusion
+- Technical accuracy verification
+```
+
+**What you can customize:**
+- Brand voice and tone
+- Writing style preferences
+- Formatting guidelines
+- SEO requirements
+- Required/optional content elements
+- Topics to avoid
+- Company-specific terminology
+- Content structure preferences
+
+### Customizing Commands (Advanced)
+
+For deeper customization, edit command files directly:
 
 ```bash
 # Edit content writer command

package/content-rules.example.md

@@ -0,0 +1,239 @@
+# Content Generation Rules
+
+This file contains custom rules and guidelines for the content-writer agent. Copy this file to `content-rules.md` in your project root and customize it for your specific content needs.
+
+## Brand Voice & Tone
+
+- **Primary Tone**: Professional yet approachable
+- **Reading Level**: 8th-10th grade (accessible to broad audience)
+- **Perspective**: Use "we" and "you" for engagement
+- **Personality Traits**: Helpful, knowledgeable, encouraging
+
+## Writing Style Guidelines
+
+### Sentence Structure
+- Keep sentences under 25 words when possible
+- Vary sentence length for rhythm
+- Use active voice (passive voice < 10% of content)
+- One main idea per sentence
+
+### Paragraph Guidelines
+- Maximum 3-4 sentences per paragraph
+- Start paragraphs with topic sentences
+- Include white space for readability
+- Break up long sections with subheadings
+
+### Word Choice
+- Prefer simple words over complex alternatives
+- Avoid jargon unless necessary (then explain it)
+- Use specific, concrete language
+- Minimize adverbs and weak verbs
+
+## Formatting Preferences
+
+### Headings
+- H1: Article title only
+- H2: Main section headers (4-7 words)
+- H3: Subsection headers (3-5 words)
+- H4: Rarely used, only for deeply nested content
+
+### Lists
+- Use numbered lists for sequential steps or ranked items
+- Use bullet points for non-sequential items
+- Keep list items parallel in structure
+- Include 3-7 items per list (optimal for comprehension)
+
+### Emphasis
+- **Bold** for key terms and important concepts
+- *Italics* for emphasis and technical terms
+- `Code formatting` for code, commands, file names
+- > Blockquotes for important callouts or quotes
+
+## SEO Requirements
+
+### Keywords
+- Primary keyword density: 1-2%
+- Include primary keyword in: title, first paragraph, at least one H2, conclusion
+- Natural keyword variations throughout
+- LSI keywords to support topic relevance
+
+### Meta Elements
+- Meta description: 150-160 characters
+- Title tag: 50-60 characters
+- URL slug: lowercase, hyphens, primary keyword
+- Alt text: descriptive, includes keyword when natural
+
+### Internal Linking
+- Link to 2-3 related internal articles
+- Use descriptive anchor text
+- Link from relevant context, not forced
+
+### Featured Snippets
+- Include FAQ section for informational content
+- Use numbered lists for "how-to" content
+- Create summary paragraphs for definitions
+- Structure tables for comparison content
+
+## Content Structure
+
+### Introduction
+- Hook reader within first 1-2 sentences
+- State article value proposition
+- Preview main points or sections
+- Length: 100-150 words
+
+### Body Content
+- Use the inverted pyramid style (most important first)
+- Include examples, data, or case studies
+- Break up text with subheadings every 300-400 words
+- Add images/visuals every 500-700 words
+
+### Conclusion
+- Summarize key takeaways (3-5 points)
+- Include clear call-to-action
+- Suggest next steps or related content
+- Length: 100-200 words
+
+## Required Elements
+
+### Must Include
+- [ ] Author attribution
+- [ ] Publication date
+- [ ] Reading time estimate
+- [ ] Category/tags for organization
+- [ ] Social sharing metadata
+- [ ] Call-to-action (CTA)
+
+### Optional Elements
+- Table of contents (for 1500+ word articles)
+- FAQ section (for informational content)
+- Key takeaways box
+- Related resources section
+- Expert quotes or testimonials
+
+## Content Types Specific Guidelines
+
+### Blog Posts
+- Length: 800-1500 words
+- Conversational tone
+- Include personal anecdotes or examples
+- Strong opening hook
+- Social sharing friendly
+
+### Technical Articles
+- Length: 1200-2500 words
+- More formal, precise language
+- Code examples with explanations
+- Step-by-step instructions
+- Prerequisites section
+
+### Product Reviews
+- Length: 1000-1800 words
+- Balanced pros and cons
+- Real-world testing experience
+- Comparison tables
+- Clear recommendation
+
+### How-To Guides
+- Length: 800-2000 words
+- Numbered step-by-step instructions
+- Screenshots or diagrams
+- Prerequisites and materials list
+- Troubleshooting section
+
+## Topics & Restrictions
+
+### Topics to Avoid
+- Political opinions or endorsements
+- Medical diagnoses or treatment advice
+- Financial investment recommendations
+- Legal advice
+- Controversial or divisive subjects
+
+### Topics to Handle Carefully
+- Competitor mentions (factual only, no negativity)
+- Statistics and data (always cite sources)
+- Future predictions (use qualifiers like "may" or "could")
+- Industry trends (acknowledge uncertainty)
+
+## Quality Standards
+
+### Fact-Checking
+- Verify all statistics and data
+- Link to original sources
+- Use reputable sources only (.gov, .edu, industry leaders)
+- Update outdated information
+- Date-stamp time-sensitive content
+
+### Originality
+- 100% original content (no plagiarism)
+- Unique perspective or insights
+- Fresh examples, not recycled from competitors
+- Add value beyond what already exists
+
+### Accessibility
+- Use descriptive link text (no "click here")
+- Provide alt text for all images
+- Ensure sufficient color contrast
+- Structure content for screen readers
+- Use simple language for complex topics
+
+## Brand-Specific Requirements
+
+### Company Information
+- Company Name: [Your Company]
+- Website: [Your Website]
+- Industry: [Your Industry]
+- Target Audience: [Your Audience]
+
+### Preferred Terminology
+- Use "client" instead of "customer"
+- Use "platform" instead of "software"
+- Use "solution" instead of "product"
+- [Add your specific terms]
+
+### Branding Elements
+- Include company tagline when relevant
+- Link to company blog or resources
+- Mention company values or mission when appropriate
+- Use consistent product/service names
+
+### Call-to-Action Guidelines
+- Primary CTA: [e.g., "Start Free Trial"]
+- Secondary CTA: [e.g., "Contact Sales"]
+- Placement: End of article, after value is demonstrated
+- Style: Action-oriented, clear benefit
+
+## Compliance & Legal
+
+### Disclaimers
+- Include disclaimers for advice content
+- Note affiliate relationships if applicable
+- Privacy policy compliance
+- Cookie consent requirements
+
+### Copyright
+- Respect copyright for quotes (cite source)
+- Obtain permission for extensive quotes
+- Use Creative Commons images only
+- Credit photographers/creators
+
+## Review Checklist
+
+Before submitting content, verify:
+
+- [ ] Custom rules applied consistently
+- [ ] All required elements included
+- [ ] SEO optimized (title, meta, keywords)
+- [ ] Factual accuracy verified
+- [ ] No spelling or grammar errors
+- [ ] Links working and relevant
+- [ ] Images optimized and have alt text
+- [ ] Mobile-friendly formatting
+- [ ] Readability score meets target
+- [ ] Brand voice consistent
+- [ ] CTA clear and actionable
+
+---
+
+**Note**: These are template rules. Customize this file for your specific content needs, brand voice, and target audience. The content-writer agent will use these rules to guide content generation while maintaining its core quality standards.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "myaidev-method",
-  "version": "0.2.16",
-  "description": "Comprehensive development framework with SPARC methodology for AI-assisted software development, AI visual content generation (Gemini, Imagen, DALL-E, Veo), multi-platform publishing (WordPress, PayloadCMS, Astro, Docusaurus, Mintlify), and Coolify deployment",
+  "version": "0.2.17",
+  "description": "Comprehensive development framework with SPARC methodology for AI-assisted software development, AI visual content generation (Gemini, Imagen, DALL-E, Veo, FLUX), multi-platform publishing (WordPress, PayloadCMS, Astro, Docusaurus, Mintlify), and Coolify deployment",
   "mcpName": "io.github.myaione/myaidev-method",
   "main": "src/index.js",
   "bin": {
@@ -148,6 +148,7 @@
     "CONTENT_CREATION_GUIDE.md",
     "VISUAL_CONTENT_GENERATION_GUIDE.md",
     "VISUAL_GENERATION_FILE_ORGANIZATION.md",
+    "content-rules.example.md",
     "LICENSE",
     ".env.example",
     "DEV_WORKFLOW_GUIDE.md",

package/src/lib/visual-generation-utils.js

@@ -80,9 +80,11 @@ const PRICING = {
 export function validateAPIKeys() {
   const googleKey = process.env.GOOGLE_API_KEY;
   const openaiKey = process.env.OPENAI_API_KEY;
+  const falKey = process.env.FAL_KEY;
 
   const hasGoogle = !!(googleKey && googleKey.length > 20);
   const hasOpenAI = !!(openaiKey && openaiKey.length > 20);
+  const hasFal = !!(falKey && falKey.length > 20);
 
   const availableServices = [];
   if (hasGoogle) {
@@ -91,11 +93,15 @@ export function validateAPIKeys() {
   if (hasOpenAI) {
     availableServices.push('dalle');
   }
+  if (hasFal) {
+    availableServices.push('flux', 'flux-pro', 'flux-dev', 'veo3');
+  }
 
   return {
     hasGoogle,
     hasOpenAI,
-    hasAny: hasGoogle || hasOpenAI,
+    hasFal,
+    hasAny: hasGoogle || hasOpenAI || hasFal,
     availableServices
   };
 }
@@ -133,6 +139,17 @@ export function estimateCost(service, options = {}) {
     case 'veo':
       return PRICING.veo;
 
+    case 'flux':
+    case 'flux-pro':
+      return PRICING.flux_pro;
+
+    case 'flux-dev':
+      return PRICING.flux_dev;
+
+    case 'veo3':
+    case 'veo3-fast':
+      return PRICING.veo3; // per second, will multiply by duration
+
     default:
       return 0;
   }
@@ -571,17 +588,33 @@ export async function generateImageFal(prompt, options = {}) {
         logs: false
       });
 
-      if (result.images && result.images[0]) {
-        const image = result.images[0];
+      // Fal.ai can return images in different formats
+      let imageUrl;
+      let contentType = 'image/png';
+
+      if (result.data && result.data.images && result.data.images[0]) {
+        imageUrl = result.data.images[0].url;
+        contentType = result.data.images[0].content_type || 'image/png';
+      } else if (result.images && result.images[0]) {
+        imageUrl = result.images[0].url;
+        contentType = result.images[0].content_type || 'image/png';
+      } else if (result.image && result.image.url) {
+        imageUrl = result.image.url;
+      } else if (result.data && result.data[0] && result.data[0].url) {
+        imageUrl = result.data[0].url;
+      } else if (typeof result === 'string') {
+        imageUrl = result;
+      }
 
+      if (imageUrl) {
         // Fal.ai returns URL, need to fetch and convert to base64
-        const imageResponse = await fetch(image.url);
+        const imageResponse = await fetch(imageUrl);
         const imageBuffer = await imageResponse.arrayBuffer();
         const base64Data = Buffer.from(imageBuffer).toString('base64');
 
         return {
           data: base64Data,
-          mimeType: image.content_type || 'image/png',
+          mimeType: contentType,
           service: 'fal',
           model: model,
           cost: PRICING[`${model.replace('-', '_')}`] || PRICING.flux_pro

package/src/templates/claude/agents/content-writer.md

@@ -65,13 +65,62 @@ if (hasAnyAPIKeys()) {
 - Understanding the target audience
 - Competitive content analysis
 
+## Custom Content Rules
+
+The content-writer agent supports custom content generation rules via a `content-rules.md` file in your project root. If this file exists, the agent will incorporate your custom guidelines into the content generation process.
+
+**To use custom rules:**
+
+1. Create a `content-rules.md` file in your project directory
+2. Define your content preferences, style guidelines, brand voice, or formatting requirements
+3. The agent will automatically detect and apply these rules
+
+**Example content-rules.md:**
+```markdown
+# Content Generation Rules
+
+## Brand Voice
+- Use conversational, friendly tone
+- Avoid jargon unless explaining technical concepts
+- Include real-world examples
+
+## Formatting Preferences
+- Keep paragraphs under 3 sentences
+- Use numbered lists for sequential steps
+- Use bullet points for non-sequential items
+
+## SEO Guidelines
+- Target keyword density: 1-2%
+- Include FAQ section for articles over 1000 words
+- Add "Related Resources" section at the end
+
+## Topics to Avoid
+- Political opinions
+- Medical advice
+- Financial recommendations
+
+## Required Elements
+- Author bio at the end
+- Call-to-action in conclusion
+- Social sharing snippet
+```
+
+**Note:** If `content-rules.md` doesn't exist, the agent will use its default professional content creation guidelines.
+
 ## Writing Process
 
+### Phase 0: Load Custom Rules (if available)
+- Check for `content-rules.md` in project root
+- If found, read and incorporate custom guidelines
+- Merge custom rules with default best practices
+- Continue with standard process if file doesn't exist
+
 ### Phase 1: Understanding
 - Identify the content purpose and goals
 - Define the target audience
 - Determine the desired tone and style
 - Clarify key messages and takeaways
+- **Apply custom content rules if available**
 
 ### Phase 2: Research
 - Conduct thorough topic research using WebSearch