veogent 1.4.0 → 1.5.0

package/README.md

@@ -45,12 +45,12 @@ veogent setup-flow --flowkey "ya29.a0AW..." --tier "PAYGATE_TIER_TWO"   # Setup
 ### How VEOGENT Works — The Mental Model
 
 ```
---idea → AI Description → Project + Characters (reference images)
-                                  → Chapter Content (storyboard)
-                                  → Scenes → Images → Videos
+Core chapter story text → Project + Characters (reference images)
+                        → Chapter Content (storyboard)
+                        → Scenes → Images → Videos
 ```
 
-**Key concept:** Names in `--idea` become character/entity references with image URIs at project level. These references ensure visual consistency across ALL chapters and scenes.
+**Key concept:** Pass rich story text directly to `create-project` (chapter-structured). VEOGENT uses named entities from that story to build project-level references for consistency.
 
 ### The Pipeline (4 Phases)
 
@@ -58,21 +58,21 @@ veogent setup-flow --flowkey "ya29.a0AW..." --tier "PAYGATE_TIER_TWO"   # Setup
 
 ```bash
 veogent create-project \
-  --idea "Bella the white Bichon Frisé CEO in pink blazer, two Doberman bodyguards Rex and Duke in black suits, luxury shopping mall Saigon" \
   --name "Boss Babe in Fur" \
+  --story "Chapter 1.
+Bella the white Bichon Frisé CEO in a pink blazer enters the luxury Saigon mall with two Doberman bodyguards Rex and Duke. She shops designer stores, faces a tense crowd moment, then exits with golden bags under neon lights." \
   --lang English \
   --material CINEMATIC
 ```
 
-**What happens internally:**
-1. CLI calls `/app/description` with --idea → VEOGENT AI generates rich story description
-2. CLI calls `/app/project` with rich description → creates project + auto-generates characters from names in --idea
+**Story format rules:**
+- If `--chapters` is omitted, default is `1`
+- Must include headings like `Chapter 1.` (and `Chapter 2.` ... when chapters > 1)
+- Keep each chapter as core plot text (VEOGENT will expand into scenes later)
 
-**--idea rules:**
-- ✅ Include specific names: characters, locations, props, creatures
-- ✅ Include visual traits: "white Bichon Frisé", "black suits", "luxury mall"
-- ❌ Don't be vague: "cute dog shopping" → VEOGENT will invent random characters
-- Names in --idea → appear in storyboard → VEOGENT creates reference images → consistent across N chapters
+**What happens internally:**
+1. CLI sends your `--story` directly to `/app/project` (no `/app/description` call)
+2. VEOGENT creates project + chapter shell, then `create-chapter-content` expands story into scene scripts
 
 #### Phase 2: Generate Storyboard + Scenes
 
@@ -163,7 +163,7 @@ veogent request --type GENERATE_VIDEO \
 |---------|-------------|
 | `projects` | List all projects |
 | `project <id>` | Get project details |
-| `create-project` | Create project (auto-generates description from `--idea`) |
+| `create-project` | Create project from chapter-structured `--story` text |
 
 ### Chapters & Scenes
 
@@ -257,7 +257,7 @@ Maximum **5** concurrent requests. If queue is full (E10071), CLI auto-retries o
 
 - Always use `--agent-safe` flag
 - Use `workflow-status` for the most complete snapshot
-- Character reference images are created from names found in `--idea` and scene scripts
+- Character reference images are created from named entities in `--story` and generated scene scripts
 - Use character NAMES only in prompts — never describe appearance (reference images define it)
 - See **[`skills/SKILL.md`](./skills/SKILL.md)** for the full agent guide
 

package/index.js

@@ -203,56 +203,63 @@ program
 
 program
     .command('create-project')
-    .description('Create a new project (auto-generates rich description from idea)')
+    .description('Create a new project from chapter-structured core story text')
     .requiredOption('--name <name>', 'Project name')
-    .requiredOption('--idea <idea>', 'Story idea')
-    .option('--desc <desc>', 'Description (if omitted, auto-generated from idea via AI)')
+    .requiredOption('--story <story>', 'Core story text. Format: "Chapter 1. ..." (and "Chapter N." blocks when --chapters > 1)')
     .requiredOption('--lang <lang>', 'Story language')
     .option('--sound <sound>', 'Sound effects (true/false)', 'true')
     .requiredOption('--material <material>', 'Image material')
-    .option('--chapters <count>', 'Number of chapters', '1')
+    .option('--chapters <count>', 'Number of chapters (default: 1)', '1')
     .option('--customPromptId <customPromptId>', 'Custom Prompt ID')
     .option('--objects <objects...>', 'List of specific objects for the project as JSON strings (optional)')
     .action(async (options) => {
         try {
-            // Step 1: Generate rich description from keyword if not provided
-            let description = options.desc;
-            if (!description) {
-                humanLog('📝 Generating description from idea...');
-                const descData = unwrapData(await api.post('/app/description', {
-                    keyword: options.idea,
-                    language: options.lang,
-                }));
-                description = descData?.description || descData?.text || String(descData);
-                humanLog(`✅ Description generated (${description.length} chars)`);
+            const chapterCount = Number.parseInt(options.chapters, 10);
+            if (!Number.isFinite(chapterCount) || chapterCount < 1) {
+                throw new Error('--chapters must be an integer >= 1');
+            }
+
+            const story = String(options.story || '').trim();
+            if (!story) {
+                throw new Error('--story is required');
+            }
+
+            const chapterMatches = story.match(/Chapter\s+\d+\./gi) || [];
+            if (chapterMatches.length < chapterCount) {
+                throw new Error(`Story format invalid: expected at least ${chapterCount} chapter heading(s) like "Chapter N."`);
+            }
+            for (let i = 1; i <= chapterCount; i += 1) {
+                const hasHeading = new RegExp(`\\bChapter\\s+${i}\\.`, 'i').test(story);
+                if (!hasHeading) {
+                    throw new Error(`Story format invalid: missing heading "Chapter ${i}."`);
+                }
             }
 
-            // Step 2: Create project with rich description
             let parsedObjects = [];
             if (options.objects && options.objects.length > 0) {
                 try {
                     parsedObjects = options.objects.map(objStr => typeof objStr === 'string' ? JSON.parse(objStr) : objStr);
                 } catch (e) {
-                    throw new Error("Invalid JSON format for --objects.");
+                    throw new Error('Invalid JSON format for --objects.');
                 }
             }
 
             const payload = {
                 projectName: options.name,
-                keyword: options.idea,
-                description,
+                keyword: story,
+                description: story,
                 storyLanguage: options.lang,
                 soundEffects: options.sound === 'true' || options.sound === true,
                 imageMaterial: options.material,
-                numberChapters: parseInt(options.chapters),
+                numberChapters: chapterCount,
                 objects: parsedObjects
             };
             if (options.customPromptId) payload.customPromptId = options.customPromptId;
 
             const data = await api.post('/app/project', payload);
-            console.log(JSON.stringify({ status: "success", description, project: unwrapData(data) }, null, 2));
+            console.log(JSON.stringify({ status: 'success', story, project: unwrapData(data) }, null, 2));
         } catch (error) {
-            console.log(JSON.stringify({ status: "error", ...formatCliError(error) }));
+            console.log(JSON.stringify({ status: 'error', ...formatCliError(error) }));
         }
     });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "veogent",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "The official CLI to interact with the VEOGENT API - AI Video and Image generation platform",
   "main": "index.js",
   "bin": {

package/skills/SKILL.md

@@ -12,12 +12,12 @@ Use the `veogent` CLI as the source of truth for VEOGENT workflows. Always use `
 ## How VEOGENT Works — The Mental Model
 
 ```
---idea → AI Description → Project + Character References (image URIs)
+--story (chapter-structured plain text) → Project + Character References (image URIs)
                         → Storyboard (scene scripts)
                         → Scenes → Images → Videos
 ```
 
-**The key insight:** Names in `--idea` become character/entity references with image URIs at **project level**. These references ensure visual consistency across ALL chapters and scenes.
+**The key insight:** Names/entities in `--story` become character/entity references with image URIs at **project level**. These references ensure visual consistency across ALL chapters and scenes.
 
 That's why you use character **NAMES only** in prompts — never describe appearance. The reference images already define exactly how each character looks.
 
@@ -29,19 +29,21 @@ That's why you use character **NAMES only** in prompts — never describe appear
 
 ```bash
 veogent create-project \
-  --idea "Bella the white Bichon Frisé CEO in pink blazer, two Doberman bodyguards Rex and Duke in black suits, luxury shopping mall Saigon" \
+  --story "Chapter 1. Bella the white Bichon Frisé CEO in pink blazer enters a luxury shopping mall in Saigon with two Doberman bodyguards, Rex and Duke." \
   --name "Boss Babe in Fur" \
   --lang English --material CINEMATIC
 ```
 
-Internally: CLI calls `/app/description` → generates rich AI description from --idea → creates project with character references.
+Internally: CLI sends `--story` directly to `/app/project` (no `/app/description` pre-step).
 
-**--idea rules:**
+**--story rules:**
 - ✅ Specific character names + species/role: `"Mochi the Shiba Inu"`, `"Chef Gordon the Bulldog"`
 - ✅ Location names: `"Grand Luxury Mall Saigon"`, `"Tokyo Night Market"`
 - ✅ Visual traits: `"pink blazer"`, `"black tactical suit"`
 - ✅ Props/creatures: `"robot vacuum"`, `"durian toy"`, `"golden shopping bags"`
-- ❌ Vague: `"cute dog shopping"` → VEOGENT invents random characters
+- ❌ Vague one-liners: `"cute dog shopping"` → weak entity extraction and unstable references
+- ✅ Include headings like `Chapter 1.` (`Chapter 2.`... when chapters > 1)
+- ✅ If `--chapters` is omitted, default is `1`
 
 ### Phase 2: Storyboard + Scenes
 
@@ -150,8 +152,8 @@ veogent characters <projectId>
 ```
 
 **Rules:**
-- Characters from `--idea` are auto-created (no manual add needed)
-- `add-character` only for characters NOT in original --idea
+- Characters/entities from `--story` are auto-created (no manual add needed)
+- `add-character` only for entities NOT present in original `--story`
 - ⚠️ NEVER edit-character mid-project when scenes already generated
 - More references = better consistency (locations, props, troops too)
 - Mention a reference name in edit-scene → that entity appears in the scene
@@ -322,7 +324,7 @@ veogent request --type GENERATE_VIDEO --project X --chapter Y --scene Z \
 
 | Command | Description | Key Options |
 |---------|-------------|-------------|
-| `create-project` | Create project (auto-gen description from --idea) | `--idea`, `--name`, `--lang`, `--material`, `--chapters` |
+| `create-project` | Create project from chapter-structured story text | `--story`, `--name`, `--lang`, `--material`, `--chapters` |
 | `projects` | List all projects | — |
 | `project <id>` | Get project details | — |
 | `delete-project` | ⚠️ Delete project permanently | `--project`, `--confirm` |