claude-presentation-master 8.0.0 → 8.1.0

package/bin/cli.js

@@ -20,7 +20,7 @@ const args = process.argv.slice(2);
 
 // Help text
 const helpText = `
-Claude Presentation Master v7.2.0
+Claude Presentation Master v8.1.0
 Generate world-class presentations using expert methodologies
 
 100% FREE • Zero API Keys • Runs Locally • KB-Driven Quality
@@ -30,11 +30,16 @@ USAGE:
   cpm <command> [options]
 
 COMMANDS:
-  generate <input>    Generate presentation from input file
+  generate [input]    Generate presentation (auto-detects file if omitted)
   validate <file>     Validate an existing HTML presentation
   visual-qa <file>    Run HIGH-LEVEL visual quality evaluation (Playwright)
   info                Show package information
 
+AUTO-DETECTION:
+  If no input file is specified, the CLI scans your current directory for:
+  - Priority files: README.md, content.md, presentation.md, slides.md, pitch.md
+  - Any .md, .txt, .json, .yaml file
+
 OPTIONS:
   -o, --output <dir>      Output directory (default: ./output)
   -m, --mode <mode>       Presentation mode: keynote or business (default: keynote)
@@ -55,17 +60,20 @@ OPTIONS:
   -v, --version           Show version number
 
 EXAMPLES:
-  # Quick one-off: Generate keynote from markdown (npx - no install needed)
+  # Auto-detect content in current directory
+  npx claude-presentation-master generate
+
+  # Or specify a file
   npx claude-presentation-master generate notes.md -m keynote -f html
 
   # Generate consulting deck as PowerPoint
   cpm generate strategy.md -m business --type consulting_deck -f pptx
 
   # Investment banking pitchbook
-  cpm generate deal-memo.md --type investment_banking -f pptx -o ./pitchbook
+  cpm generate --type investment_banking -f pptx -o ./pitchbook
 
   # Generate both formats
-  cpm generate quarterly-review.md -m business -f html,pptx -o ./slides
+  cpm generate -f html,pptx -o ./slides
 
   # Validate an existing presentation
   cpm validate output/presentation.html -m keynote
@@ -89,7 +97,7 @@ For more information: https://github.com/Stuinfla/claude-presentation-master
 `;
 
 // Version
-const version = '7.2.0';
+const version = '8.1.0';
 
 // Parse arguments
 function parseArgs(args) {
@@ -194,6 +202,49 @@ function parseArgs(args) {
   return options;
 }
 
+/**
+ * Auto-detect a content file in the given directory.
+ * Prioritizes: README.md, content.md, presentation.md, then any .md, .txt, .json, .yaml
+ */
+function autoDetectContentFile(directory) {
+  const contentExtensions = ['.md', '.markdown', '.txt', '.json', '.yaml', '.yml'];
+  const priorityFiles = [
+    'README.md', 'readme.md',
+    'content.md', 'Content.md',
+    'presentation.md', 'Presentation.md',
+    'slides.md', 'Slides.md',
+    'pitch.md', 'Pitch.md',
+    'deck.md', 'Deck.md'
+  ];
+
+  // First, check for priority files
+  for (const file of priorityFiles) {
+    const filePath = join(directory, file);
+    if (existsSync(filePath)) {
+      return file;
+    }
+  }
+
+  // Then scan for any content file
+  try {
+    const files = readdirSync(directory);
+    for (const file of files) {
+      const ext = extname(file).toLowerCase();
+      if (contentExtensions.includes(ext)) {
+        // Skip node_modules, hidden files, package files
+        if (file.startsWith('.') || file.startsWith('_')) continue;
+        if (file === 'package.json' || file === 'package-lock.json') continue;
+        if (file === 'tsconfig.json' || file === 'jest.config.js') continue;
+        return file;
+      }
+    }
+  } catch (e) {
+    // Directory not readable
+  }
+
+  return null;
+}
+
 // Determine content type from file extension
 function getContentType(filename) {
   const ext = extname(filename).toLowerCase();
@@ -293,8 +344,19 @@ Usage:
     process.exit(1);
   }
 
-  // Validate input
-  if (!options.input) {
+  // Auto-detect input file if not specified
+  if (!options.input && options.command === 'generate') {
+    const detected = autoDetectContentFile(process.cwd());
+    if (detected) {
+      options.input = detected;
+      console.log(`📁 Auto-detected: ${detected}`);
+    } else {
+      console.error(`Error: No content file found in current directory.`);
+      console.error(`Looked for: *.md, *.txt, *.json, *.yaml, *.yml`);
+      console.error(`\nEither create a content file or specify one: cpm generate <file>`);
+      process.exit(1);
+    }
+  } else if (!options.input) {
     console.error(`Error: No input file specified for "${options.command}" command.`);
     process.exit(1);
   }

package/dist/index.d.mts

@@ -1579,22 +1579,48 @@ declare class QAEngine {
 }
 
 /**
- * VisualQualityEvaluator - Evaluates presentations like a human expert.
+ * VisualQualityEvaluator - EXPERT-LEVEL Presentation Evaluation
  *
- * THIS IS NOT A LINTER. This evaluates:
- * - Is this slide visually compelling?
- * - Does the presentation tell a coherent story?
- * - Would an executive be impressed?
- * - Does it look like McKinsey made it?
+ * THIS IS NOT A LINTER. This evaluates like a world-class presentation coach:
  *
- * Uses Playwright to render and screenshot each slide, then evaluates
- * the ACTUAL visual output, not just data structures.
+ * EXPERT PRINCIPLES APPLIED:
+ * 1. Nancy Duarte's Glance Test - Can you understand each slide in 3 seconds?
+ * 2. Chris Anderson's One Idea Rule - Does each slide communicate ONE message?
+ * 3. Edward Tufte's Data-Ink Ratio - Does every element serve a purpose?
+ * 4. Barbara Minto's Pyramid Principle - Is the answer first, then support?
+ * 5. Garr Reynolds' Signal to Noise - Is decoration minimized?
+ * 6. Carmine Gallo's Rule of Three - Are key points structured effectively?
+ * 7. Cole Knaflic's Context First - Does data have proper context?
  *
- * @version 9.0.0
+ * WHAT EXPERTS WOULD CHECK:
+ * - Does the deck accomplish its purpose? (Persuade, inform, inspire)
+ * - Does the narrative hang together? (Story arc, tension, resolution)
+ * - Is each slide communicative? (Message clear in 3 seconds)
+ * - Are visuals used intelligently? (Supporting message, not decorating)
+ * - Is typography/layout professional? (Hierarchy, spacing, balance)
+ * - Would McKinsey show this to a Fortune 500 CEO?
+ *
+ * CRITICAL VISUAL FAILURES (immediate score penalty):
+ * - Truncated text (content cut off)
+ * - Empty slides (missing content)
+ * - Broken layouts (overflow, misalignment)
+ * - Low contrast (illegible text)
+ *
+ * @version 10.0.0 - Expert-Driven QA
  */
 interface SlideVisualScore {
     slideIndex: number;
     slideType: string;
+    glanceTest: number;
+    glanceTestNotes: string;
+    oneIdea: number;
+    oneIdeaNotes: string;
+    dataInkRatio: number;
+    dataInkNotes: string;
+    professionalExecution: number;
+    professionalExecutionNotes: string;
+    hasCriticalFailure: boolean;
+    criticalFailures: string[];
     visualImpact: number;
     visualImpactNotes: string;
     contentClarity: number;
@@ -1660,7 +1686,17 @@ declare class VisualQualityEvaluator {
     private closeBrowser;
     private getSlideCount;
     private evaluateSlide;
+    /**
+     * EXPERT-LEVEL SLIDE SCORING
+     *
+     * This evaluates each slide like Nancy Duarte, Carmine Gallo, or a McKinsey partner would.
+     * It's not about rules - it's about whether the slide WORKS.
+     */
     private scoreSlide;
+    /**
+     * Create a failed slide score (for critical failures)
+     */
+    private createFailedSlideScore;
     private inferSlideType;
     private evaluateNarrativeFlow;
     private evaluateVisualConsistency;

package/dist/index.d.ts

@@ -1579,22 +1579,48 @@ declare class QAEngine {
 }
 
 /**
- * VisualQualityEvaluator - Evaluates presentations like a human expert.
+ * VisualQualityEvaluator - EXPERT-LEVEL Presentation Evaluation
  *
- * THIS IS NOT A LINTER. This evaluates:
- * - Is this slide visually compelling?
- * - Does the presentation tell a coherent story?
- * - Would an executive be impressed?
- * - Does it look like McKinsey made it?
+ * THIS IS NOT A LINTER. This evaluates like a world-class presentation coach:
  *
- * Uses Playwright to render and screenshot each slide, then evaluates
- * the ACTUAL visual output, not just data structures.
+ * EXPERT PRINCIPLES APPLIED:
+ * 1. Nancy Duarte's Glance Test - Can you understand each slide in 3 seconds?
+ * 2. Chris Anderson's One Idea Rule - Does each slide communicate ONE message?
+ * 3. Edward Tufte's Data-Ink Ratio - Does every element serve a purpose?
+ * 4. Barbara Minto's Pyramid Principle - Is the answer first, then support?
+ * 5. Garr Reynolds' Signal to Noise - Is decoration minimized?
+ * 6. Carmine Gallo's Rule of Three - Are key points structured effectively?
+ * 7. Cole Knaflic's Context First - Does data have proper context?
  *
- * @version 9.0.0
+ * WHAT EXPERTS WOULD CHECK:
+ * - Does the deck accomplish its purpose? (Persuade, inform, inspire)
+ * - Does the narrative hang together? (Story arc, tension, resolution)
+ * - Is each slide communicative? (Message clear in 3 seconds)
+ * - Are visuals used intelligently? (Supporting message, not decorating)
+ * - Is typography/layout professional? (Hierarchy, spacing, balance)
+ * - Would McKinsey show this to a Fortune 500 CEO?
+ *
+ * CRITICAL VISUAL FAILURES (immediate score penalty):
+ * - Truncated text (content cut off)
+ * - Empty slides (missing content)
+ * - Broken layouts (overflow, misalignment)
+ * - Low contrast (illegible text)
+ *
+ * @version 10.0.0 - Expert-Driven QA
  */
 interface SlideVisualScore {
     slideIndex: number;
     slideType: string;
+    glanceTest: number;
+    glanceTestNotes: string;
+    oneIdea: number;
+    oneIdeaNotes: string;
+    dataInkRatio: number;
+    dataInkNotes: string;
+    professionalExecution: number;
+    professionalExecutionNotes: string;
+    hasCriticalFailure: boolean;
+    criticalFailures: string[];
     visualImpact: number;
     visualImpactNotes: string;
     contentClarity: number;
@@ -1660,7 +1686,17 @@ declare class VisualQualityEvaluator {
     private closeBrowser;
     private getSlideCount;
     private evaluateSlide;
+    /**
+     * EXPERT-LEVEL SLIDE SCORING
+     *
+     * This evaluates each slide like Nancy Duarte, Carmine Gallo, or a McKinsey partner would.
+     * It's not about rules - it's about whether the slide WORKS.
+     */
     private scoreSlide;
+    /**
+     * Create a failed slide score (for critical failures)
+     */
+    private createFailedSlideScore;
     private inferSlideType;
     private evaluateNarrativeFlow;
     private evaluateVisualConsistency;