autoblogger 0.2.20 → 0.2.22

package/dist/cli/index.js

@@ -446,6 +446,17 @@ async function promptInit(options) {
     message: "Run database migration after setup?",
     initial: true
   });
+  questions.push({
+    type: "select",
+    name: "deploymentPlatform",
+    message: "Where will you deploy? (for RSS auto-draft scheduling)",
+    choices: [
+      { title: "Vercel (serverless)", value: "vercel", description: "Creates API route + vercel.json cron" },
+      { title: "Server (VPS/Docker)", value: "server", description: "Creates cron script for crontab" },
+      { title: "Skip for now", value: "skip", description: "Set up auto-draft later" }
+    ],
+    initial: 0
+  });
   if (options.contentPaths.length > 0) {
     const contentSummary = options.contentPaths.map((p) => `${p} (${options.contentCounts[p]} files)`).join(", ");
     console.log(import_picocolors.default.cyan(`
@@ -478,7 +489,8 @@ Found existing content: ${contentSummary}`));
     dbProvider: answers.dbProvider || "postgresql",
     runMigration: answers.runMigration ?? true,
     importContent: answers.importContent ?? false,
-    importPath: answers.importPath || options.contentPaths[0]
+    importPath: answers.importPath || options.contentPaths[0],
+    deploymentPlatform: answers.deploymentPlatform || "vercel"
   };
 }
 async function confirm(message, initial = true) {
@@ -632,6 +644,121 @@ var WRITER_LAYOUT_TEMPLATE = `export default function WriterLayout({
 }
 `;
 
+// src/cli/templates/auto-draft-script.ts
+var AUTO_DRAFT_SCRIPT_TEMPLATE = `/**
+ * Auto-Draft Cron Script
+ * 
+ * Fetches RSS feeds for active topic subscriptions and generates essay drafts.
+ * Run with: npx tsx --env-file=.env.local scripts/auto-draft.ts
+ * 
+ * Schedule via cron:
+ *   0 6 * * * cd /path/to/project && npx tsx scripts/auto-draft.ts >> /var/log/auto-draft.log 2>&1
+ */
+
+import 'dotenv/config'
+import { cms } from '../lib/cms'
+
+async function main() {
+  const startTime = new Date()
+  console.log(\`[\${startTime.toISOString()}] Starting auto-draft...\`)
+  
+  try {
+    const results = await cms.autoDraft.run()
+    
+    if (results.length === 0) {
+      console.log('  No active topics to process.')
+    } else {
+      let totalGenerated = 0
+      let totalSkipped = 0
+      
+      for (const r of results) {
+        console.log(\`  \${r.topicName}: generated \${r.generated}, skipped \${r.skipped}\`)
+        totalGenerated += r.generated
+        totalSkipped += r.skipped
+      }
+      
+      console.log('  ---')
+      console.log(\`  Total: \${totalGenerated} essays generated, \${totalSkipped} articles skipped\`)
+    }
+    
+    const endTime = new Date()
+    const duration = (endTime.getTime() - startTime.getTime()) / 1000
+    console.log(\`[\${endTime.toISOString()}] Done in \${duration.toFixed(1)}s\`)
+    
+    process.exit(0)
+  } catch (error) {
+    console.error('Auto-draft failed:', error)
+    process.exit(1)
+  }
+}
+
+main()
+`;
+
+// src/cli/templates/vercel-cron-route.ts
+var VERCEL_CRON_ROUTE_TEMPLATE = `import { NextResponse } from 'next/server'
+import { cms } from '@/lib/cms'
+
+/**
+ * Vercel Cron endpoint for RSS auto-draft generation.
+ * 
+ * Triggered by Vercel Cron on schedule defined in vercel.json.
+ * Fetches RSS feeds for active topic subscriptions and generates essay drafts.
+ * 
+ * To test manually:
+ *   curl -H "Authorization: Bearer YOUR_CRON_SECRET" http://localhost:3000/api/cron/auto-draft
+ */
+export async function GET(request: Request) {
+  // Verify the request is from Vercel Cron (security)
+  const authHeader = request.headers.get('authorization')
+  if (authHeader !== \`Bearer \${process.env.CRON_SECRET}\`) {
+    return NextResponse.json({ error: 'Unauthorized' }, { status: 401 })
+  }
+
+  const startTime = new Date()
+  console.log(\`[\${startTime.toISOString()}] Starting auto-draft via Vercel Cron...\`)
+
+  try {
+    const results = await cms.autoDraft.run()
+
+    if (results.length === 0) {
+      console.log('  No active topics to process.')
+    } else {
+      let totalGenerated = 0
+      let totalSkipped = 0
+
+      for (const r of results) {
+        console.log(\`  \${r.topicName}: generated \${r.generated}, skipped \${r.skipped}\`)
+        totalGenerated += r.generated
+        totalSkipped += r.skipped
+      }
+
+      console.log('  ---')
+      console.log(\`  Total: \${totalGenerated} essays generated, \${totalSkipped} articles skipped\`)
+    }
+
+    const endTime = new Date()
+    const duration = (endTime.getTime() - startTime.getTime()) / 1000
+    console.log(\`[\${endTime.toISOString()}] Done in \${duration.toFixed(1)}s\`)
+
+    return NextResponse.json({
+      success: true,
+      results,
+      duration: \`\${duration.toFixed(1)}s\`,
+    })
+  } catch (error) {
+    console.error('Auto-draft failed:', error)
+    return NextResponse.json(
+      { error: error instanceof Error ? error.message : 'Auto-draft failed' },
+      { status: 500 }
+    )
+  }
+}
+
+// Vercel Cron requires a longer timeout for AI generation
+export const maxDuration = 300 // 5 minutes
+`;
+
 // src/cli/import.ts
 var fs5 = __toESM(require("fs"));
 var path5 = __toESM(require("path"));
@@ -895,11 +1022,15 @@ async function init(options = {}) {
   for (const contentPath of project.contentPaths) {
     contentCounts[contentPath] = countMarkdownFiles(path6.join(cwd, contentPath));
   }
+  const hasVercelJson = fs6.existsSync(path6.join(cwd, "vercel.json"));
+  const hasVercelDir = fs6.existsSync(path6.join(cwd, ".vercel"));
+  const isLikelyVercel = hasVercelJson || hasVercelDir;
   let answers = {
     dbProvider: "postgresql",
     runMigration: !options.skipMigrate,
     importContent: !!options.importPath,
-    importPath: options.importPath || project.contentPaths[0]
+    importPath: options.importPath || project.contentPaths[0],
+    deploymentPlatform: isLikelyVercel ? "vercel" : "server"
   };
   if (!options.yes) {
     answers = await promptInit({
@@ -929,6 +1060,12 @@ Error: Found conflicting model names in your Prisma schema:`));
     console.log(`  - ${project.appRouterPath}/api/cms/[...path]/route.ts`);
     console.log(`  - ${project.appRouterPath}/(writer)/writer/[[...path]]/page.tsx`);
     console.log(`  - ${project.appRouterPath}/(writer)/layout.tsx`);
+    if (answers.deploymentPlatform === "vercel") {
+      console.log(`  - ${project.appRouterPath}/api/cron/auto-draft/route.ts (Vercel Cron endpoint)`);
+      console.log(`  - vercel.json (add cron schedule)`);
+    } else if (answers.deploymentPlatform === "server") {
+      console.log(`  - scripts/auto-draft.ts (cron script for crontab)`);
+    }
     console.log(`  - globals.css (add CSS import)`);
     console.log(`  - ${project.appRouterPath}/layout.tsx (add suppressHydrationWarning, GlobalShortcuts)`);
     if (answers.runMigration) {
@@ -999,6 +1136,53 @@ Would import ${count} posts from ${answers.importPath}`);
     fs6.writeFileSync(writerLayoutPath, WRITER_LAYOUT_TEMPLATE);
     log("write", `Created ${project.appRouterPath}/(writer)/layout.tsx`);
   }
+  if (answers.deploymentPlatform === "vercel") {
+    const cronRoutePath = path6.join(cwd, project.appRouterPath, "api", "cron", "auto-draft", "route.ts");
+    if (fs6.existsSync(cronRoutePath)) {
+      log("skip", `${project.appRouterPath}/api/cron/auto-draft/route.ts already exists`);
+    } else {
+      const cronRouteDir = path6.dirname(cronRoutePath);
+      if (!fs6.existsSync(cronRouteDir)) {
+        fs6.mkdirSync(cronRouteDir, { recursive: true });
+      }
+      fs6.writeFileSync(cronRoutePath, VERCEL_CRON_ROUTE_TEMPLATE);
+      log("write", `Created ${project.appRouterPath}/api/cron/auto-draft/route.ts`);
+    }
+    const vercelJsonPath = path6.join(cwd, "vercel.json");
+    let vercelConfig = {};
+    if (fs6.existsSync(vercelJsonPath)) {
+      try {
+        vercelConfig = JSON.parse(fs6.readFileSync(vercelJsonPath, "utf-8"));
+      } catch {
+      }
+    }
+    const cronPath = "/api/cron/auto-draft";
+    const existingCron = vercelConfig.crons?.find((c) => c.path === cronPath);
+    if (existingCron) {
+      log("skip", "vercel.json already has auto-draft cron");
+    } else {
+      vercelConfig.crons = vercelConfig.crons || [];
+      vercelConfig.crons.push({
+        path: cronPath,
+        schedule: "0 6 * * *"
+        // Daily at 6am UTC
+      });
+      fs6.writeFileSync(vercelJsonPath, JSON.stringify(vercelConfig, null, 2) + "\n");
+      log("write", "Updated vercel.json with auto-draft cron (daily at 6am UTC)");
+    }
+  } else if (answers.deploymentPlatform === "server") {
+    const scriptsDir = path6.join(cwd, "scripts");
+    const autoDraftScriptPath = path6.join(scriptsDir, "auto-draft.ts");
+    if (fs6.existsSync(autoDraftScriptPath)) {
+      log("skip", "scripts/auto-draft.ts already exists");
+    } else {
+      if (!fs6.existsSync(scriptsDir)) {
+        fs6.mkdirSync(scriptsDir, { recursive: true });
+      }
+      fs6.writeFileSync(autoDraftScriptPath, AUTO_DRAFT_SCRIPT_TEMPLATE);
+      log("write", "Created scripts/auto-draft.ts (schedule via crontab)");
+    }
+  }
   const globalsCssPath = findGlobalsCss(cwd);
   if (globalsCssPath) {
     const cssResult = patchGlobalsCss(globalsCssPath);
@@ -1095,6 +1279,12 @@ Would import ${count} posts from ${answers.importPath}`);
   console.log(import_picocolors3.default.gray("  1. Update lib/cms.ts with your auth configuration"));
   console.log(import_picocolors3.default.gray("  2. Add your auth check to app/(writer)/writer/[[...path]]/page.tsx"));
   console.log(import_picocolors3.default.gray("  3. Set ANTHROPIC_API_KEY and/or OPENAI_API_KEY for AI features"));
+  if (answers.deploymentPlatform === "vercel") {
+    console.log(import_picocolors3.default.gray("  4. Set CRON_SECRET env var in Vercel for auto-draft security"));
+  } else if (answers.deploymentPlatform === "server") {
+    console.log(import_picocolors3.default.gray("  4. Schedule scripts/auto-draft.ts via crontab:"));
+    console.log(import_picocolors3.default.gray("     0 6 * * * cd /path/to/project && npx tsx scripts/auto-draft.ts"));
+  }
   console.log("");
 }
 

package/dist/index.d.mts

@@ -689,30 +689,35 @@ declare function buildAutoDraftPrompt(options: {
  * Placeholders: {{RULES}}, {{STYLE_EXAMPLES}}, {{WORD_COUNT}}
  */
 declare const DEFAULT_GENERATE_TEMPLATE = "<system>\n<role>Expert essay writer creating engaging, thoughtful content</role>\n\n<critical>\nALWAYS output a complete essay. NEVER respond conversationally.\n- Do NOT ask questions or request clarification\n- Do NOT say \"Here is your essay\" or similar preamble\n- Do NOT explain what you're going to write\n- If the prompt is vague, make creative choices and proceed\n- Output ONLY the essay in markdown format\n</critical>\n\n<rules>\n{{RULES}}\n</rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n\n<constraints>\n<word_count>{{WORD_COUNT}}</word_count>\n</constraints>\n\n<output_format>\nCRITICAL: Your response MUST start with exactly this format:\n\nLine 1: # [Your Title Here]\nLine 2: *[Your subtitle here]*\nLine 3: (blank line)\nLine 4+: Essay body in markdown\n\n<title_guidelines>\n- Be SPECIFIC, not generic (avoid \"The Power of\", \"Why X Matters\", \"A Guide to\")\n- Include a concrete detail, angle, or unexpected element\n- Create curiosity or make a bold claim\n- 5-12 words ideal\n</title_guidelines>\n\n<subtitle_guidelines>\n- One sentence that hooks the reader\n- Tease the main argument or reveal a key insight\n- Create tension, curiosity, or promise value\n- Make readers want to continue reading\n</subtitle_guidelines>\n</output_format>\n</system>";
+
 /**
  * Default template for chat interactions.
  * Placeholders: {{CHAT_RULES}}, {{RULES}}, {{STYLE_EXAMPLES}}, {{ESSAY_CONTEXT}}
  */
 declare const DEFAULT_CHAT_TEMPLATE = "<system>\n<role>Helpful writing assistant for essay creation and editing</role>\n\n<chat_rules>\n{{CHAT_RULES}}\n</chat_rules>\n\n<writing_rules>\n{{RULES}}\n</writing_rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n\n<context>\n{{ESSAY_CONTEXT}}\n</context>\n\n<behavior>\n- Be concise and actionable\n- When suggesting edits, be specific about what to change\n- Match the author's voice and style when writing\n- Ask clarifying questions if the request is ambiguous\n</behavior>\n</system>";
+
 /**
  * Default template for text rewriting.
  * Placeholders: {{REWRITE_RULES}}, {{RULES}}, {{STYLE_EXAMPLES}}
  */
 declare const DEFAULT_REWRITE_TEMPLATE = "<system>\n<role>Writing assistant that improves text quality</role>\n\n<rewrite_rules>\n{{REWRITE_RULES}}\n</rewrite_rules>\n\n<writing_rules>\n{{RULES}}\n</writing_rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n\n<behavior>\n- Preserve the original meaning exactly\n- Improve clarity, flow, and readability\n- Fix grammar and punctuation issues\n- Maintain the author's voice and tone\n- Output only the improved text, no explanations\n</behavior>\n</system>";
+
 /**
  * Default template for auto-drafting from news articles.
  * Placeholders: {{AUTO_DRAFT_RULES}}, {{RULES}}, {{STYLE_EXAMPLES}}, {{TOPIC_NAME}}, {{ARTICLE_TITLE}}, {{ARTICLE_SUMMARY}}, {{ARTICLE_URL}}, {{AUTO_DRAFT_WORD_COUNT}}
  */
 declare const DEFAULT_AUTO_DRAFT_TEMPLATE = "<system>\n<role>Expert essay writer creating engaging content from news articles</role>\n\n<auto_draft_rules>\n{{AUTO_DRAFT_RULES}}\n</auto_draft_rules>\n\n<writing_rules>\n{{RULES}}\n</writing_rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n\n<source_article>\n<topic>{{TOPIC_NAME}}</topic>\n<title>{{ARTICLE_TITLE}}</title>\n<summary>{{ARTICLE_SUMMARY}}</summary>\n<url>{{ARTICLE_URL}}</url>\n</source_article>\n\n<constraints>\n<word_count>{{AUTO_DRAFT_WORD_COUNT}}</word_count>\n</constraints>\n\n<output_format>\nCRITICAL: Your response MUST start with exactly this format:\n\nLine 1: # [Your Title Here]\nLine 2: *[Your subtitle here]*\nLine 3: (blank line)\nLine 4+: Essay body in markdown\n\n<title_guidelines>\n- Be SPECIFIC about the news angle, not generic\n- Include a concrete detail or unexpected element\n- Create curiosity or make a bold claim\n- 5-12 words ideal\n</title_guidelines>\n\n<subtitle_guidelines>\n- One sentence that hooks the reader\n- Tease the main argument or unique perspective\n- Create tension, curiosity, or promise value\n</subtitle_guidelines>\n</output_format>\n</system>";
+
 /**
  * Default template for essay outline generation.
  * Placeholders: {{PLAN_RULES}}, {{STYLE_EXAMPLES}}
  */
-declare const DEFAULT_PLAN_TEMPLATE = "<system>\n<role>Writing assistant that creates essay outlines</role>\n\n<critical>\nWrap your ENTIRE response in <plan> tags. Output NOTHING outside the tags.\n</critical>\n\n<rules>\n{{PLAN_RULES}}\n</rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n</system>";
+declare const DEFAULT_PLAN_TEMPLATE = "<system>\n<role>Essay outline generator - you ONLY output plans, never conversation</role>\n\n<critical>\nYOU ARE A PLAN GENERATOR. Every response must be a complete essay outline.\n\nABSOLUTE RULES:\n1. ALWAYS output a plan wrapped in <plan> tags\n2. NEVER have conversational responses outside the plan\n3. If user asks a question \u2192 answer by generating/revising a plan\n4. If user gives feedback \u2192 output the revised plan\n5. If user gives a topic \u2192 output a new plan for that topic\n6. Your ENTIRE response is ONLY the <plan>...</plan> block\n\nNO EXCEPTIONS. Every message you send is a plan.\n</critical>\n\n<rules>\n{{PLAN_RULES}}\n</rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n</system>";
 /**
  * Default rules for plan generation format.
  */
-declare const DEFAULT_PLAN_RULES = "<format>\nSTRICT LIMIT: Maximum 3 bullets per section. Most sections should have 1-2 bullets.\n\n<plan>\n# Essay Title\n*One-line subtitle*\n\n## Section Name\n- Key point\n\n## Section Name\n- Key point\n- Another point\n\n## Section Name\n- Key point\n</plan>\n</format>\n\n<constraints>\n- 4-6 section headings (## lines)\n- 1-3 bullets per section \u2014 NEVER 4 or more\n- Bullets are short phrases, not sentences\n- No prose, no paragraphs, no explanations\n- When revising, output the complete updated plan\n</constraints>\n\n<title_guidelines>\n- Be SPECIFIC about the essay's angle\n- Include a concrete detail or unexpected element\n- Avoid generic patterns like \"The Power of\", \"Why X Matters\"\n- 5-12 words ideal\n</title_guidelines>\n\n<subtitle_guidelines>\n- One sentence that previews the main argument\n- Create curiosity or make a bold claim\n</subtitle_guidelines>";
+declare const DEFAULT_PLAN_RULES = "<format>\nEXACT OUTPUT FORMAT - copy this structure precisely:\n\n<plan>\n# Essay Title\n*One-line subtitle*\n\n## Section Name\n- Key point\n\n## Section Name\n- Key point\n- Another point\n\n## Section Name\n- Key point\n</plan>\n</format>\n\n<syntax_requirements>\n- Title: \"# \" (hash + space) then title text\n- Subtitle: \"*\" + text + \"*\" (asterisks for italics)\n- Sections: \"## \" (double hash + space) then section name  \n- Points: \"- \" (dash + space) then point text\n</syntax_requirements>\n\n<constraints>\n- 4-6 section headings (## lines)\n- 1-3 bullets per section \u2014 NEVER 4 or more\n- Bullets are short phrases, not full sentences\n- NO prose, NO paragraphs, NO explanations outside the plan\n- When revising, output the COMPLETE updated plan\n- NEVER output anything outside the <plan> tags\n</constraints>\n\n<title_guidelines>\n- Be SPECIFIC about the essay's angle\n- Include a concrete detail or unexpected element\n- Avoid generic patterns like \"The Power of\", \"Why X Matters\"\n- 5-12 words ideal\n</title_guidelines>\n\n<subtitle_guidelines>\n- One sentence that previews the main argument\n- Create curiosity or make a bold claim\n</subtitle_guidelines>";
+
 /**
  * Default template for expanding outlines into full essays.
  * Placeholders: {{RULES}}, {{STYLE_EXAMPLES}}, {{PLAN}}

package/dist/index.d.ts

@@ -689,30 +689,35 @@ declare function buildAutoDraftPrompt(options: {
  * Placeholders: {{RULES}}, {{STYLE_EXAMPLES}}, {{WORD_COUNT}}
  */
 declare const DEFAULT_GENERATE_TEMPLATE = "<system>\n<role>Expert essay writer creating engaging, thoughtful content</role>\n\n<critical>\nALWAYS output a complete essay. NEVER respond conversationally.\n- Do NOT ask questions or request clarification\n- Do NOT say \"Here is your essay\" or similar preamble\n- Do NOT explain what you're going to write\n- If the prompt is vague, make creative choices and proceed\n- Output ONLY the essay in markdown format\n</critical>\n\n<rules>\n{{RULES}}\n</rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n\n<constraints>\n<word_count>{{WORD_COUNT}}</word_count>\n</constraints>\n\n<output_format>\nCRITICAL: Your response MUST start with exactly this format:\n\nLine 1: # [Your Title Here]\nLine 2: *[Your subtitle here]*\nLine 3: (blank line)\nLine 4+: Essay body in markdown\n\n<title_guidelines>\n- Be SPECIFIC, not generic (avoid \"The Power of\", \"Why X Matters\", \"A Guide to\")\n- Include a concrete detail, angle, or unexpected element\n- Create curiosity or make a bold claim\n- 5-12 words ideal\n</title_guidelines>\n\n<subtitle_guidelines>\n- One sentence that hooks the reader\n- Tease the main argument or reveal a key insight\n- Create tension, curiosity, or promise value\n- Make readers want to continue reading\n</subtitle_guidelines>\n</output_format>\n</system>";
+
 /**
  * Default template for chat interactions.
  * Placeholders: {{CHAT_RULES}}, {{RULES}}, {{STYLE_EXAMPLES}}, {{ESSAY_CONTEXT}}
  */
 declare const DEFAULT_CHAT_TEMPLATE = "<system>\n<role>Helpful writing assistant for essay creation and editing</role>\n\n<chat_rules>\n{{CHAT_RULES}}\n</chat_rules>\n\n<writing_rules>\n{{RULES}}\n</writing_rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n\n<context>\n{{ESSAY_CONTEXT}}\n</context>\n\n<behavior>\n- Be concise and actionable\n- When suggesting edits, be specific about what to change\n- Match the author's voice and style when writing\n- Ask clarifying questions if the request is ambiguous\n</behavior>\n</system>";
+
 /**
  * Default template for text rewriting.
  * Placeholders: {{REWRITE_RULES}}, {{RULES}}, {{STYLE_EXAMPLES}}
  */
 declare const DEFAULT_REWRITE_TEMPLATE = "<system>\n<role>Writing assistant that improves text quality</role>\n\n<rewrite_rules>\n{{REWRITE_RULES}}\n</rewrite_rules>\n\n<writing_rules>\n{{RULES}}\n</writing_rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n\n<behavior>\n- Preserve the original meaning exactly\n- Improve clarity, flow, and readability\n- Fix grammar and punctuation issues\n- Maintain the author's voice and tone\n- Output only the improved text, no explanations\n</behavior>\n</system>";
+
 /**
  * Default template for auto-drafting from news articles.
  * Placeholders: {{AUTO_DRAFT_RULES}}, {{RULES}}, {{STYLE_EXAMPLES}}, {{TOPIC_NAME}}, {{ARTICLE_TITLE}}, {{ARTICLE_SUMMARY}}, {{ARTICLE_URL}}, {{AUTO_DRAFT_WORD_COUNT}}
  */
 declare const DEFAULT_AUTO_DRAFT_TEMPLATE = "<system>\n<role>Expert essay writer creating engaging content from news articles</role>\n\n<auto_draft_rules>\n{{AUTO_DRAFT_RULES}}\n</auto_draft_rules>\n\n<writing_rules>\n{{RULES}}\n</writing_rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n\n<source_article>\n<topic>{{TOPIC_NAME}}</topic>\n<title>{{ARTICLE_TITLE}}</title>\n<summary>{{ARTICLE_SUMMARY}}</summary>\n<url>{{ARTICLE_URL}}</url>\n</source_article>\n\n<constraints>\n<word_count>{{AUTO_DRAFT_WORD_COUNT}}</word_count>\n</constraints>\n\n<output_format>\nCRITICAL: Your response MUST start with exactly this format:\n\nLine 1: # [Your Title Here]\nLine 2: *[Your subtitle here]*\nLine 3: (blank line)\nLine 4+: Essay body in markdown\n\n<title_guidelines>\n- Be SPECIFIC about the news angle, not generic\n- Include a concrete detail or unexpected element\n- Create curiosity or make a bold claim\n- 5-12 words ideal\n</title_guidelines>\n\n<subtitle_guidelines>\n- One sentence that hooks the reader\n- Tease the main argument or unique perspective\n- Create tension, curiosity, or promise value\n</subtitle_guidelines>\n</output_format>\n</system>";
+
 /**
  * Default template for essay outline generation.
  * Placeholders: {{PLAN_RULES}}, {{STYLE_EXAMPLES}}
  */
-declare const DEFAULT_PLAN_TEMPLATE = "<system>\n<role>Writing assistant that creates essay outlines</role>\n\n<critical>\nWrap your ENTIRE response in <plan> tags. Output NOTHING outside the tags.\n</critical>\n\n<rules>\n{{PLAN_RULES}}\n</rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n</system>";
+declare const DEFAULT_PLAN_TEMPLATE = "<system>\n<role>Essay outline generator - you ONLY output plans, never conversation</role>\n\n<critical>\nYOU ARE A PLAN GENERATOR. Every response must be a complete essay outline.\n\nABSOLUTE RULES:\n1. ALWAYS output a plan wrapped in <plan> tags\n2. NEVER have conversational responses outside the plan\n3. If user asks a question \u2192 answer by generating/revising a plan\n4. If user gives feedback \u2192 output the revised plan\n5. If user gives a topic \u2192 output a new plan for that topic\n6. Your ENTIRE response is ONLY the <plan>...</plan> block\n\nNO EXCEPTIONS. Every message you send is a plan.\n</critical>\n\n<rules>\n{{PLAN_RULES}}\n</rules>\n\n<style_reference>\n{{STYLE_EXAMPLES}}\n</style_reference>\n</system>";
 /**
  * Default rules for plan generation format.
  */
-declare const DEFAULT_PLAN_RULES = "<format>\nSTRICT LIMIT: Maximum 3 bullets per section. Most sections should have 1-2 bullets.\n\n<plan>\n# Essay Title\n*One-line subtitle*\n\n## Section Name\n- Key point\n\n## Section Name\n- Key point\n- Another point\n\n## Section Name\n- Key point\n</plan>\n</format>\n\n<constraints>\n- 4-6 section headings (## lines)\n- 1-3 bullets per section \u2014 NEVER 4 or more\n- Bullets are short phrases, not sentences\n- No prose, no paragraphs, no explanations\n- When revising, output the complete updated plan\n</constraints>\n\n<title_guidelines>\n- Be SPECIFIC about the essay's angle\n- Include a concrete detail or unexpected element\n- Avoid generic patterns like \"The Power of\", \"Why X Matters\"\n- 5-12 words ideal\n</title_guidelines>\n\n<subtitle_guidelines>\n- One sentence that previews the main argument\n- Create curiosity or make a bold claim\n</subtitle_guidelines>";
+declare const DEFAULT_PLAN_RULES = "<format>\nEXACT OUTPUT FORMAT - copy this structure precisely:\n\n<plan>\n# Essay Title\n*One-line subtitle*\n\n## Section Name\n- Key point\n\n## Section Name\n- Key point\n- Another point\n\n## Section Name\n- Key point\n</plan>\n</format>\n\n<syntax_requirements>\n- Title: \"# \" (hash + space) then title text\n- Subtitle: \"*\" + text + \"*\" (asterisks for italics)\n- Sections: \"## \" (double hash + space) then section name  \n- Points: \"- \" (dash + space) then point text\n</syntax_requirements>\n\n<constraints>\n- 4-6 section headings (## lines)\n- 1-3 bullets per section \u2014 NEVER 4 or more\n- Bullets are short phrases, not full sentences\n- NO prose, NO paragraphs, NO explanations outside the plan\n- When revising, output the COMPLETE updated plan\n- NEVER output anything outside the <plan> tags\n</constraints>\n\n<title_guidelines>\n- Be SPECIFIC about the essay's angle\n- Include a concrete detail or unexpected element\n- Avoid generic patterns like \"The Power of\", \"Why X Matters\"\n- 5-12 words ideal\n</title_guidelines>\n\n<subtitle_guidelines>\n- One sentence that previews the main argument\n- Create curiosity or make a bold claim\n</subtitle_guidelines>";
+
 /**
  * Default template for expanding outlines into full essays.
  * Placeholders: {{RULES}}, {{STYLE_EXAMPLES}}, {{PLAN}}