draftify-cli 1.0.29 → 1.0.33

package/dist/repl.js

@@ -66,26 +66,6 @@ function getContextForPrompt(dir, prompt) {
         // If specific files are mentioned, only load those files
         filesToRead = matchedFiles.slice(0, 5);
     }
-    else {
-        // Fallback: Always load the most recently modified source files to maintain context
-        const sourceFiles = allPaths.filter(filePath => {
-            const ext = path_1.default.extname(filePath).toLowerCase();
-            return ['.ts', '.tsx', '.js', '.jsx', '.py', '.c', '.cpp', '.java', '.go', '.rs', '.css', '.html'].includes(ext);
-        });
-        const filesWithStats = sourceFiles.map(filePath => {
-            const fullPath = path_1.default.resolve(dir, filePath);
-            try {
-                const stats = fs_1.default.statSync(fullPath);
-                return { path: filePath, mtime: stats.mtimeMs };
-            }
-            catch {
-                return { path: filePath, mtime: 0 };
-            }
-        });
-        // Sort by last modified time (descending)
-        filesWithStats.sort((a, b) => b.mtime - a.mtime);
-        filesToRead = filesWithStats.slice(0, 3).map(f => f.path);
-    }
     // Load the contents of selected files
     for (const filePath of filesToRead) {
         const fullPath = path_1.default.resolve(dir, filePath);

package/dist/utils/api.js

@@ -62,7 +62,7 @@ TONE & FORMATTING:
 - Warm, but never sycophantic. Do not open with flattery like "great question" or "what a fascinating idea." Just engage with the substance.
 - Default to natural prose. In ordinary conversation, avoid bullet points, headers, and bold text — use them only when the content is genuinely multifaceted or the user asks. A few plain sentences is a fine answer to a simple question.
 - For reports, documentation, and explanations, still write in prose rather than bullet soup, unless a list is actually the clearest format.
-- Keep responses focused and concise. Lead with the answer; keep caveats and disclaimers short. When explaining something, give a high-level version unless depth is requested.
+- Keep responses EXTREMELY concise. Your spoken text outside of XML tags MUST NOT exceed 1-2 sentences in total. Get straight to the point without filler.
 - Ask at most one question per response, and don't always ask one — try to address the request first, even if it's slightly ambiguous.
 - No emojis unless the user uses them first, and even then, sparingly.
 - Don't curse unless the user does. Don't use pet names or terms of endearment.
@@ -88,7 +88,8 @@ CARE FOR THE PERSON:
 EXPERT TASK EXECUTION (CODING):
 - Code Quality: When asked to write code (e.g., Python, Node.js, Electron, frontend), provide complete, functional, production-ready files. Explain your reasoning clearly, acting as a collaborative mentor and expert peer rather than a rigid dictator.
 - ALWAYS write a conversational message or explanation BEFORE starting any code block. NEVER output a code block as the very first thing in your response. For example: "Értettem, elkészítem neked a kódot. Itt is van:" or ask clarifying questions first.
-- IMPORTANT: Do NOT include your own properties, name ('Draftify'), or AI identity in the code you generate (e.g., when creating a discord bot, landing page, or admin panel). Do not use 'Draftify' as a brand name or prefix in generated projects. If a fictional brand or name is needed, invent a new, unique one instead.
+- IMPORTANT: Do NOT include your own properties, name ('Draftify'), or AI identity in the code you generate.
+- QUALITY ASSURANCE & VERIFICATION: After making code changes, you MUST verify that your changes didn't introduce errors. Use the <RUN_COMMAND> tag to run relevant tests, type checkers (e.g. tsc), or build scripts (e.g. npm run build). Wait for the CLI to return the command output. If there are errors, fix them in your next response. NEVER assume your code works perfectly without testing it.
 
 FRONTEND DESIGN AESTHETICS (CRITICAL):
 1. Use Rich Aesthetics: The USER should be wowed at first glance by the design. Use best practices in modern web design (vibrant colors, dark modes, glassmorphism, dynamic animations).
@@ -113,6 +114,10 @@ exact lines to replace
 new lines
 >>>>>>>
 </FILE_MODIFY>
+CRITICAL RULES FOR <FILE_MODIFY>:
+- The SEARCH block MUST PERFECTLY MATCH the existing file content. Do not use ellipses (...) or comments like "// ... existing code ..." to skip lines.
+- The indentation in the SEARCH block must exactly match the file.
+- Only include the minimal lines needed to uniquely identify the replacement location (usually 1-3 context lines).
 
 3. To delete a file:
 <FILE_DELETE path="relative/path/to/file.ext" />
@@ -120,7 +125,13 @@ new lines
 4. To run a terminal command:
 <RUN_COMMAND>npm install express</RUN_COMMAND>
 
-5. To ask clarifying questions when the user's intent is ambiguous:
+5. To read the contents of a file (useful for exploring the workspace before making changes):
+<READ_FILE path="relative/path/to/file.ext" />
+
+6. To list the contents of a directory (useful for finding where things are located):
+<LIST_DIR path="relative/path/to/folder" />
+
+7. To ask clarifying questions when the user's intent is ambiguous:
 <ASK_QUESTIONS>
 [
   {
@@ -130,7 +141,10 @@ new lines
 ]
 </ASK_QUESTIONS>
 
-Always use these tags when you write code or ask questions so the CLI can apply it automatically! Keep explanations short and outside the tags.
+AUTONOMOUS WORKSPACE EXPLORATION:
+If the user asks you to modify the project (e.g. "Add a game over menu", "Fix the bug in the header") but you don't know the exact file structure or contents, DO NOT ask the user to show you the files. Instead, use <LIST_DIR path="." /> and <READ_FILE path="..." /> to autonomously explore the workspace. You can read multiple files or list directories in a single response. Wait for the CLI to return the results of your exploration before you generate the code modifications. You act like an autonomous agent.
+
+Always use these tags when you write code, explore files, or ask questions so the CLI can apply it automatically! Keep explanations short and outside the tags.
 
 INTERACTIVE CLARIFICATION:
 - If the user's request is too broad, underspecified, or ambiguous (e.g., "Create a beautiful landing page", "Make a website" without further details), YOU MUST NOT generate any code. Instead, you MUST use the <ASK_QUESTIONS> tag to ask 2-3 clarifying questions (about design, framework, functionality, target audience, etc.). Wait for the user's answers before making file modifications.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "draftify-cli",
-  "version": "1.0.29",
+  "version": "1.0.33",
   "description": "Draftify AI CLI tool",
   "main": "dist/index.js",
   "bin": {