pupt 2.2.1 → 2.3.0

package/dist/utils/path-utils.js

@@ -1,139 +0,0 @@
-/**
- * Utilities for converting paths to portable format for config files.
- *
- * When saving configs, absolute paths should be converted to portable formats:
- * - Paths under project root → ${projectRoot}/...
- * - Paths under home directory → ~/...
- * - Already relative paths → kept as-is
- * - Other absolute paths → kept as-is with warning
- */
-import path from 'node:path';
-import fs from 'node:fs';
-import os from 'node:os';
-import { findProjectRoot } from './project-root.js';
-import { logger } from './logger.js';
-/**
- * Resolve symlinks in a path, even if the leaf segments don't exist.
- * Walks up to the nearest existing ancestor, resolves it, then re-appends
- * the non-existent tail. This handles macOS /var -> /private/var symlink
- * differences when the target path (e.g. a prompt directory) hasn't been
- * created yet.
- */
-function safeRealpath(p) {
-    try {
-        return fs.realpathSync(p);
-    }
-    catch {
-        const parent = path.dirname(p);
-        if (parent === p) {
-            // Reached filesystem root — nothing more to resolve
-            return p;
-        }
-        return path.join(safeRealpath(parent), path.basename(p));
-    }
-}
-/**
- * Contract a single path to a portable format.
- *
- * Priority:
- * 1. Already relative paths → keep as-is
- * 2. Paths under project root → ${projectRoot}/...
- * 3. Paths under home directory → ~/...
- * 4. Other absolute paths → keep as-is (with optional warning)
- */
-export function contractPath(filepath, options = {}) {
-    const { configDir = process.cwd(), warnOnAbsolute = true } = options;
-    // Already relative path - keep as-is
-    if (!path.isAbsolute(filepath)) {
-        return { path: filepath, warned: false };
-    }
-    // Already uses ${projectRoot} or ~ - keep as-is
-    if (filepath.includes('${projectRoot}') || filepath.startsWith('~/')) {
-        return { path: filepath, warned: false };
-    }
-    const homeDir = os.homedir();
-    const projectRoot = findProjectRoot(configDir);
-    // Resolve symlinks for comparison (handles macOS /var -> /private/var)
-    const resolvedPath = safeRealpath(filepath);
-    // Check if path is under project root (prefer this over home)
-    if (projectRoot) {
-        const resolvedProjectRoot = safeRealpath(projectRoot);
-        if (resolvedPath.startsWith(resolvedProjectRoot + path.sep) || resolvedPath === resolvedProjectRoot) {
-            const relativePath = path.relative(resolvedProjectRoot, resolvedPath);
-            // Use forward slashes for cross-platform compatibility in config
-            const portablePath = relativePath.split(path.sep).join('/');
-            return {
-                path: portablePath ? `\${projectRoot}/${portablePath}` : '${projectRoot}',
-                warned: false
-            };
-        }
-    }
-    // Check if path is under home directory
-    const resolvedHomeDir = safeRealpath(homeDir);
-    if (resolvedPath.startsWith(resolvedHomeDir + path.sep) || resolvedPath === resolvedHomeDir) {
-        const relativePath = path.relative(resolvedHomeDir, resolvedPath);
-        // Use forward slashes for cross-platform compatibility
-        const portablePath = relativePath.split(path.sep).join('/');
-        return {
-            path: portablePath ? `~/${portablePath}` : '~',
-            warned: false
-        };
-    }
-    // Absolute path outside project and home - keep as-is but warn
-    if (warnOnAbsolute) {
-        logger.warn(`Path "${filepath}" is absolute and outside the project root. ` +
-            `This path will not be portable across machines. ` +
-            `Consider using a relative path, ~/..., or \${projectRoot}/...`);
-    }
-    return { path: filepath, warned: true };
-}
-/**
- * Check if a path is absolute and could be made portable.
- * Used for warning users on config load.
- */
-export function isNonPortableAbsolutePath(filepath, configDir) {
-    // Not absolute - it's fine
-    if (!path.isAbsolute(filepath)) {
-        return false;
-    }
-    // Uses portable variables - it's fine
-    if (filepath.includes('${projectRoot}') || filepath.startsWith('~/')) {
-        return false;
-    }
-    const homeDir = os.homedir();
-    const projectRoot = findProjectRoot(configDir || process.cwd());
-    const resolvedPath = safeRealpath(filepath);
-    // Check if it could be made portable
-    if (projectRoot) {
-        const resolvedProjectRoot = safeRealpath(projectRoot);
-        if (resolvedPath.startsWith(resolvedProjectRoot + path.sep)) {
-            return true; // Could use ${projectRoot}
-        }
-    }
-    const resolvedHomeDir = safeRealpath(homeDir);
-    if (resolvedPath.startsWith(resolvedHomeDir + path.sep)) {
-        return true; // Could use ~/
-    }
-    // Absolute but can't be made portable - still flag it
-    return true;
-}
-/**
- * Warn about non-portable paths in a config.
- * Call this when loading a config to alert users.
- */
-export function warnAboutNonPortablePaths(paths, configFilePath) {
-    const configDir = configFilePath ? path.dirname(configFilePath) : process.cwd();
-    const nonPortable = [];
-    for (const p of paths) {
-        if (p && isNonPortableAbsolutePath(p, configDir)) {
-            nonPortable.push(p);
-        }
-    }
-    if (nonPortable.length > 0) {
-        logger.warn(`Your config contains absolute paths that may not be portable:\n` +
-            nonPortable.map(p => `  - ${p}`).join('\n') + '\n' +
-            `These will be converted to portable format next time the config is saved.\n` +
-            `To fix manually, use relative paths, ~/..., or \${projectRoot}/...`);
-    }
-}
-//# sourceMappingURL=path-utils.js.map

package/dist/utils/path-utils.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"path-utils.js","sourceRoot":"","sources":["../../src/utils/path-utils.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,MAAM,SAAS,CAAC;AACzB,OAAO,EAAE,MAAM,SAAS,CAAC;AACzB,OAAO,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AACpD,OAAO,EAAE,MAAM,EAAE,MAAM,aAAa,CAAC;AAErC;;;;;;GAMG;AACH,SAAS,YAAY,CAAC,CAAS;IAC7B,IAAI,CAAC;QACH,OAAO,EAAE,CAAC,YAAY,CAAC,CAAC,CAAC,CAAC;IAC5B,CAAC;IAAC,MAAM,CAAC;QACP,MAAM,MAAM,GAAG,IAAI,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC;QAC/B,IAAI,MAAM,KAAK,CAAC,EAAE,CAAC;YACjB,oDAAoD;YACpD,OAAO,CAAC,CAAC;QACX,CAAC;QACD,OAAO,IAAI,CAAC,IAAI,CAAC,YAAY,CAAC,MAAM,CAAC,EAAE,IAAI,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,CAAC;IAC3D,CAAC;AACH,CAAC;AAgBD;;;;;;;;GAQG;AACH,MAAM,UAAU,YAAY,CAC1B,QAAgB,EAChB,UAAgC,EAAE;IAElC,MAAM,EAAE,SAAS,GAAG,OAAO,CAAC,GAAG,EAAE,EAAE,cAAc,GAAG,IAAI,EAAE,GAAG,OAAO,CAAC;IAErE,qCAAqC;IACrC,IAAI,CAAC,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC/B,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,KAAK,EAAE,CAAC;IAC3C,CAAC;IAED,gDAAgD;IAChD,IAAI,QAAQ,CAAC,QAAQ,CAAC,gBAAgB,CAAC,IAAI,QAAQ,CAAC,UAAU,CAAC,IAAI,CAAC,EAAE,CAAC;QACrE,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,KAAK,EAAE,CAAC;IAC3C,CAAC;IAED,MAAM,OAAO,GAAG,EAAE,CAAC,OAAO,EAAE,CAAC;IAC7B,MAAM,WAAW,GAAG,eAAe,CAAC,SAAS,CAAC,CAAC;IAE/C,uEAAuE;IACvE,MAAM,YAAY,GAAG,YAAY,CAAC,QAAQ,CAAC,CAAC;IAE5C,8DAA8D;IAC9D,IAAI,WAAW,EAAE,CAAC;QAChB,MAAM,mBAAmB,GAAG,YAAY,CAAC,WAAW,CAAC,CAAC;QACtD,IAAI,YAAY,CAAC,UAAU,CAAC,mBAAmB,GAAG,IAAI,CAAC,GAAG,CAAC,IAAI,YAAY,KAAK,mBAAmB,EAAE,CAAC;YACpG,MAAM,YAAY,GAAG,IAAI,CAAC,QAAQ,CAAC,mBAAmB,EAAE,YAAY,CAAC,CAAC;YACtE,iEAAiE;YACjE,MAAM,YAAY,GAAG,YAAY,CAAC,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;YAC5D,OAAO;gBACL,IAAI,EAAE,YAAY,CAAC,CAAC,CAAC,mBAAmB,YAAY,EAAE,CAAC,CAAC,CAAC,gBAAgB;gBACzE,MAAM,EAAE,KAAK;aACd,CAAC;QACJ,CAAC;IACH,CAAC;IAED,wCAAwC;IACxC,MAAM,eAAe,GAAG,YAAY,CAAC,OAAO,CAAC,CAAC;IAC9C,IAAI,YAAY,CAAC,UAAU,CAAC,eAAe,GAAG,IAAI,CAAC,GAAG,CAAC,IAAI,YAAY,KAAK,eAAe,EAAE,CAAC;QAC5F,MAAM,YAAY,GAAG,IAAI,CAAC,QAAQ,CAAC,eAAe,EAAE,YAAY,CAAC,CAAC;QAClE,uDAAuD;QACvD,MAAM,YAAY,GAAG,YAAY,CAAC,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QAC5D,OAAO;YACL,IAAI,EAAE,YAAY,CAAC,CAAC,CAAC,KAAK,YAAY,EAAE,CAAC,CAAC,CAAC,GAAG;YAC9C,MAAM,EAAE,KAAK;SACd,CAAC;IACJ,CAAC;IAED,+DAA+D;IAC/D,IAAI,cAAc,EAAE,CAAC;QACnB,MAAM,CAAC,IAAI,CACT,SAAS,QAAQ,8CAA8C;YAC/D,kDAAkD;YAClD,+DAA+D,CAChE,CAAC;IACJ,CAAC;IAED,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC;AAC1C,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,yBAAyB,CAAC,QAAgB,EAAE,SAAkB;IAC5E,2BAA2B;IAC3B,IAAI,CAAC,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC/B,OAAO,KAAK,CAAC;IACf,CAAC;IAED,sCAAsC;IACtC,IAAI,QAAQ,CAAC,QAAQ,CAAC,gBAAgB,CAAC,IAAI,QAAQ,CAAC,UAAU,CAAC,IAAI,CAAC,EAAE,CAAC;QACrE,OAAO,KAAK,CAAC;IACf,CAAC;IAED,MAAM,OAAO,GAAG,EAAE,CAAC,OAAO,EAAE,CAAC;IAC7B,MAAM,WAAW,GAAG,eAAe,CAAC,SAAS,IAAI,OAAO,CAAC,GAAG,EAAE,CAAC,CAAC;IAChE,MAAM,YAAY,GAAG,YAAY,CAAC,QAAQ,CAAC,CAAC;IAE5C,qCAAqC;IACrC,IAAI,WAAW,EAAE,CAAC;QAChB,MAAM,mBAAmB,GAAG,YAAY,CAAC,WAAW,CAAC,CAAC;QACtD,IAAI,YAAY,CAAC,UAAU,CAAC,mBAAmB,GAAG,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC;YAC5D,OAAO,IAAI,CAAC,CAAC,2BAA2B;QAC1C,CAAC;IACH,CAAC;IAED,MAAM,eAAe,GAAG,YAAY,CAAC,OAAO,CAAC,CAAC;IAC9C,IAAI,YAAY,CAAC,UAAU,CAAC,eAAe,GAAG,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC;QACxD,OAAO,IAAI,CAAC,CAAC,eAAe;IAC9B,CAAC;IAED,sDAAsD;IACtD,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,yBAAyB,CACvC,KAA6B,EAC7B,cAAuB;IAEvB,MAAM,SAAS,GAAG,cAAc,CAAC,CAAC,CAAC,IAAI,CAAC,OAAO,CAAC,cAAc,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,GAAG,EAAE,CAAC;IAChF,MAAM,WAAW,GAAa,EAAE,CAAC;IAEjC,KAAK,MAAM,CAAC,IAAI,KAAK,EAAE,CAAC;QACtB,IAAI,CAAC,IAAI,yBAAyB,CAAC,CAAC,EAAE,SAAS,CAAC,EAAE,CAAC;YACjD,WAAW,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;QACtB,CAAC;IACH,CAAC;IAED,IAAI,WAAW,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC3B,MAAM,CAAC,IAAI,CACT,iEAAiE;YACjE,WAAW,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,IAAI;YAClD,6EAA6E;YAC7E,oEAAoE,CACrE,CAAC;IACJ,CAAC;AACH,CAAC"}

package/dist/utils/prompt-format.d.ts

@@ -1,27 +0,0 @@
-/**
- * Prompt format types supported by pupt.
- *
- * - `jsx`: Build-time JSX, imported as ES modules (.tsx/.jsx files)
- * - `jsx-runtime`: Runtime-parsed JSX via createPromptFromSource (.prompt files)
- */
-export type PromptFormat = 'jsx' | 'jsx-runtime';
-/**
- * File extensions recognized as pupt-lib JSX prompt formats.
- */
-export declare const PUPT_LIB_EXTENSIONS: string[];
-/**
- * All file extensions recognized as prompt files.
- */
-export declare const ALL_PROMPT_EXTENSIONS: string[];
-/**
- * Detect the prompt format based on file extension.
- *
- * @param filePath - Path or filename to check
- * @returns The detected prompt format
- */
-export declare function detectPromptFormat(filePath: string): PromptFormat;
-/**
- * Check if a file is a pupt-lib prompt format.
- */
-export declare function isPuptLibFormat(filePath: string): boolean;
-//# sourceMappingURL=prompt-format.d.ts.map

package/dist/utils/prompt-format.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompt-format.d.ts","sourceRoot":"","sources":["../../src/utils/prompt-format.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,MAAM,MAAM,YAAY,GAAG,KAAK,GAAG,aAAa,CAAC;AAEjD;;GAEG;AACH,eAAO,MAAM,mBAAmB,UAA8B,CAAC;AAE/D;;GAEG;AACH,eAAO,MAAM,qBAAqB,UAA2B,CAAC;AAE9D;;;;;GAKG;AACH,wBAAgB,kBAAkB,CAAC,QAAQ,EAAE,MAAM,GAAG,YAAY,CAKjE;AAED;;GAEG;AACH,wBAAgB,eAAe,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAGzD"}

package/dist/utils/prompt-format.js

@@ -1,28 +0,0 @@
-/**
- * File extensions recognized as pupt-lib JSX prompt formats.
- */
-export const PUPT_LIB_EXTENSIONS = ['.tsx', '.jsx', '.prompt'];
-/**
- * All file extensions recognized as prompt files.
- */
-export const ALL_PROMPT_EXTENSIONS = [...PUPT_LIB_EXTENSIONS];
-/**
- * Detect the prompt format based on file extension.
- *
- * @param filePath - Path or filename to check
- * @returns The detected prompt format
- */
-export function detectPromptFormat(filePath) {
-    if (filePath.endsWith('.tsx') || filePath.endsWith('.jsx')) {
-        return 'jsx';
-    }
-    return 'jsx-runtime';
-}
-/**
- * Check if a file is a pupt-lib prompt format.
- */
-export function isPuptLibFormat(filePath) {
-    const format = detectPromptFormat(filePath);
-    return format === 'jsx' || format === 'jsx-runtime';
-}
-//# sourceMappingURL=prompt-format.js.map

package/dist/utils/prompt-format.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompt-format.js","sourceRoot":"","sources":["../../src/utils/prompt-format.ts"],"names":[],"mappings":"AAQA;;GAEG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,CAAC,MAAM,EAAE,MAAM,EAAE,SAAS,CAAC,CAAC;AAE/D;;GAEG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAG,CAAC,GAAG,mBAAmB,CAAC,CAAC;AAE9D;;;;;GAKG;AACH,MAAM,UAAU,kBAAkB,CAAC,QAAgB;IACjD,IAAI,QAAQ,CAAC,QAAQ,CAAC,MAAM,CAAC,IAAI,QAAQ,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE,CAAC;QAC3D,OAAO,KAAK,CAAC;IACf,CAAC;IACD,OAAO,aAAa,CAAC;AACvB,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,eAAe,CAAC,QAAgB;IAC9C,MAAM,MAAM,GAAG,kBAAkB,CAAC,QAAQ,CAAC,CAAC;IAC5C,OAAO,MAAM,KAAK,KAAK,IAAI,MAAM,KAAK,aAAa,CAAC;AACtD,CAAC"}

package/prompts/ad-hoc-long.prompt

@@ -1,60 +0,0 @@
-{/* Converted from ad-hoc-long.md */}
-<Prompt name="ad-hoc-long" description="Ad Hoc (Long)" tags={[]}>
-
-  <Role>
-    You are a versatile expert assistant capable of handling complex, multi-part requests that require detailed analysis, planning, or implementation.
-  </Role>
-
-  <Task>
-    Address the comprehensive request below with appropriate depth and thoroughness.
-  </Task>
-
-  <Constraint>
-    - Read the entire request before beginning response
-    - Identify all sub-tasks and requirements
-    - Create a prioritized task list focusing on the MAIN objective
-    - For debugging tasks:
-      - Stay focused on the specific issue reported
-      - Follow a systematic process without getting sidetracked
-      - Fix the reported issue FIRST before exploring related problems
-      - Verify the fix resolves the original issue
-    - Organize response to address each part clearly
-    - Use appropriate formatting and structure
-    - Provide comprehensive solutions
-  </Constraint>
-
-  <Format>
-    Organize response based on request type:
-    - For multi-part questions: Address each part with clear sections
-    - For analysis tasks: Use structured findings and recommendations
-    - For implementation tasks: Provide step-by-step approach
-    - For debugging: 
-      1. State the specific issue to be fixed
-      2. Reproduce the issue exactly as described
-      3. Identify root cause through systematic investigation
-      4. Apply targeted fix for that specific issue
-      5. Verify the original issue is resolved
-      6. Only then address related issues if requested
-
-    **Complex Request**:
-    <Ask.Editor name="prompt" label="Prompt (press enter to open editor):" />
-  </Format>
-
-  <Section>
-    N/A (varies by request type)
-  </Section>
-
-  <Constraint>
-    - Maintain focus on the specific request
-    - Balance thoroughness with clarity
-    - Use examples and code samples where helpful
-    - Flag any assumptions or uncertainties
-  </Constraint>
-
-  <SuccessCriteria>
-    <Criterion>All parts of the request are addressed</Criterion>
-    <Criterion>Response is well-organized and easy to follow</Criterion>
-    <Criterion>Solutions are practical and implementable</Criterion>
-    <Criterion>Any edge cases or considerations are noted</Criterion>
-  </SuccessCriteria>
-</Prompt>

package/prompts/ad-hoc.prompt

@@ -1,29 +0,0 @@
-{/* Converted from ad-hoc.md */}
-<Prompt name="ad-hoc" description="Ad Hoc" tags={[]}>
-  <Role>
-    You are a versatile AI assistant capable of handling various technical and non-technical tasks. Adapt your expertise based on the specific request.
-  </Role>
-
-  <Task>
-    <Ask.Text name="prompt" label="Prompt:" />
-  </Task>
-
-  <Constraint>
-    - Provide accurate, helpful, and actionable responses
-    - Use appropriate formatting (code blocks, lists, tables) based on content type
-  </Constraint>
-
-  <WhenUncertain action="ask" />
-
-  <Format>
-    Match the response format to the task type - use structured output for technical tasks, narrative for explanations, and step-by-step instructions for procedures.
-  </Format>
-
-  <Constraint>
-    Stay focused on the specific request without adding unnecessary information unless it directly supports the main objective.
-  </Constraint>
-
-  <SuccessCriteria>
-    <Criterion>The response directly addresses the user's request with appropriate depth and format for the task at hand.</Criterion>
-  </SuccessCriteria>
-</Prompt>

package/prompts/code-review.prompt

@@ -1,99 +0,0 @@
-{/* Converted from code-review.md */}
-<Prompt name="code-review" description="Code Review" tags={[]}>
-
-  <Role preset="engineer" extend expertise="code review, identifying AI-generated code issues, maintainability, correctness">
-    You are a meticulous code reviewer with expertise in identifying both human and AI-generated code issues, focusing on maintainability, correctness, and common LLM coding mistakes.
-  </Role>
-
-  <Task>
-    Perform a comprehensive multi-pass code review identifying issues and improvement opportunities. Write the code review to <Ask.ReviewFile name="outputFile" label="Output file:" />.
-  </Task>
-
-  <Constraints extend>
-    - **Pass 1 - Critical Issues**: Security, correctness, data loss risks
-    - **Pass 2 - Code Quality**:
-      <Ask.Editor name="codeReviewConcerns" label="Code review concerns (press enter to open editor):" />
-    - **Pass 3 - LLM-Specific Issues**: 
-      - Hallucinated APIs or methods that don't exist
-      - Incorrect error handling patterns
-      - Overly complex solutions to simple problems
-      - Inconsistent code style within same file
-      - Copy-paste errors and duplicated logic
-      - Missing edge case handling
-      
-    - Create file inventory first, categorizing files as:
-      - Production code (src/)
-      - Test code (test/, *.test.*, *.spec.*)
-      - Configuration (config files, build scripts)
-    - Apply different standards based on file type:
-      - Production code: Strict type safety, no 'any' types
-      - Test code: 'any' types acceptable for mocks, relaxed standards
-      - Configuration: Focus on security and correctness
-    - For each issue found:
-      - Verify it's a real issue considering the file context
-      - Assess actual impact on system
-      - Provide specific fix with code example
-    - Group similar issues for batch remediation
-  </Constraints>
-
-  <Format>
-    ```markdown
-    # Code Review Report - <DateTime />
-
-    ## Executive Summary
-    - Files reviewed: X
-    - Critical issues: X
-    - High priority issues: X  
-    - Medium priority issues: X
-    - Low priority issues: X
-
-    ## Critical Issues (Fix Immediately)
-    ### 1. [Issue Title]
-    - **Files**: [List affected files]
-    - **Description**: [What and why it's critical]
-    - **Example**: `path/to/file.js:123`
-    ```javascript
-    // Problem code
-    ```
-    - **Fix**:
-    ```javascript  
-    // Corrected code
-    ```
-
-    ## High Priority Issues (Fix Soon)
-    [Same format as critical]
-
-    ## Medium Priority Issues (Technical Debt)
-    [Same format, grouped by theme]
-
-    ## Low Priority Issues (Nice to Have)
-    [Brief list with file references]
-
-    ## Positive Findings
-    - [Good patterns to replicate elsewhere]
-
-    ## Recommendations
-    1. [Highest impact improvement]
-    2. [Next priority]
-    ...
-    ```
-  </Format>
-
-  <Constraint>
-    - Don't flag test utilities for production code issues
-    - Test files have different standards: 'any' types, mocks, and test helpers are acceptable
-    - Consider project conventions before suggesting changes
-    - Check if the issue is actually problematic in its context
-    - Focus on measurable improvements
-    - Distinguish must-fix from nice-to-have
-    - CRITICAL: Don't recommend unnecessary libraries - check if existing solutions work first
-  </Constraint>
-
-  <SuccessCriteria>
-    <Criterion>All significant issues caught and correctly prioritized</Criterion>
-    <Criterion>Fixes are specific and implementable</Criterion>
-    <Criterion>Report enables systematic remediation</Criterion>
-    <Criterion>No false positives that waste developer time</Criterion>
-  </SuccessCriteria>
-
-</Prompt>

package/prompts/debugging-error-message.prompt

@@ -1,81 +0,0 @@
-{/* Converted from debugging-error-message.md */}
-<Prompt name="debugging-error-message" description="Debugging Error Message" tags={[]}>
-
-  <Role preset="engineer" expertise="error analysis, debugging, root cause identification, systematic problem-solving" />
-
-  <Task>
-    Diagnose and fix all errors that occur when <Ask.Text name="errorCondition" label="Error condition:" />.
-  </Task>
-
-  <Constraints extend>
-    - First, reproduce the error condition exactly as described
-    - Capture complete error output including stack traces
-    - For multiple errors, create a prioritized list (fix blocking errors first)
-    - For each error apply this debugging process:
-      1. **Understand**: Read error message and stack trace completely
-      2. **Locate**: Find exact file, line, and surrounding context
-      3. **Analyze**: Determine what the code is trying to do vs. what's happening
-      4. **Trace**: Follow data flow to find where things go wrong
-      5. **Fix**: Address root cause, not symptoms
-      6. **Verify**: Confirm this specific error is resolved
-      7. **Test**: Ensure fix doesn't break other functionality
-    - After all fixes, reproduce original condition to verify resolution
-    - Document any assumptions or environmental dependencies
-  </Constraints>
-
-  <Format>
-    ```markdown
-    ## Error Analysis for: {inputs.errorCondition}
-
-    ### Complete Error Output
-    ```
-    <Ask.Editor name="errorText" label="Error text (press enter to open editor):" />
-    ```
-
-    ### Error Inventory
-    1. [Error Type]: [File:Line] - [Brief description]
-    2. [Continue for all errors...]
-
-    ### Root Cause Analysis
-
-    #### Error 1: [Error type]
-    - **Symptom**: [What's visibly wrong]
-    - **Location**: [Specific file:line]
-    - **Root Cause**: [Why it's happening]
-    - **Code Context**: [Relevant code snippet]
-    - **Fix Applied**: [Specific changes made]
-    - **Verification**: [How confirmed it's fixed]
-
-    ### Final Verification
-    - Command run: [exact command]
-    - Result: [success/failure]
-    - All errors resolved: [yes/no]
-    ```
-  </Format>
-
-  <Examples>
-    <Example>
-    ```
-    Error 1: TypeError: Cannot read property 'name' of undefined
-    Location: src/user.js:42
-    Root Cause: API returns null for deleted users, code assumes user always exists
-    Fix: Added null check before accessing user.name
-    Verification: Error no longer occurs, added test case for null user
-    ```
-    </Example>
-  </Examples>
-
-  <Constraint>
-    - Fix root causes, not symptoms
-    - Don't suppress errors with try-catch unless that's the correct solution
-    - Preserve all intended functionality
-    - Make focused changes that don't introduce new issues
-  </Constraint>
-
-  <SuccessCriteria>
-    <Criterion>Original error condition no longer produces any errors</Criterion>
-    <Criterion>All fixes address root causes</Criterion>
-    <Criterion>No new errors introduced</Criterion>
-    <Criterion>Clear documentation of what was wrong and how it was fixed</Criterion>
-  </SuccessCriteria>
-</Prompt>

package/prompts/fix-github-actions.prompt

@@ -1,62 +0,0 @@
-{/* Converted from fix-github-actions.md */}
-<Prompt name="fix-github-actions" description="Fix GitHub Actions" tags={[]}>
-  <Role preset="devops" extend expertise="GitHub Actions, CI/CD pipelines, cross-platform compatibility">
-    You are a DevOps engineer specializing in GitHub Actions, CI/CD pipelines, and cross-platform compatibility issues.
-  </Role>
-
-  <Task>
-    Analyze and fix all failing GitHub Actions workflow jobs, ensuring reliable CI/CD pipeline operation.
-  </Task>
-
-  <Constraints extend>
-    - Use `gh run list --limit 1` to find the latest workflow run
-    - Use `gh run view` with the run ID to see all jobs
-    - For each failed job, use `gh run view` with the run ID and `--log-failed` to get error details
-    - Categorize failures: environment, dependencies, tests, build, deployment
-    - For each error:
-      1. Identify if it's environment-specific (OS, versions)
-      2. Check if it's a flaky test or real failure
-      3. Determine if it's a workflow configuration issue
-      4. Test the fix locally when possible
-      5. Consider cross-platform compatibility
-    - Create fixes that work across all environments
-    - Add appropriate error handling and retries for transient failures
-  </Constraints>
-
-  <Format>
-    1. Workflow run summary (ID, jobs, success/failure status)
-    2. Categorized error list with job names
-    3. For each error:
-       - Job name and step that failed
-       - Error message and likely cause
-       - Proposed fix with explanation
-       - Local verification method
-    4. Summary of all changes made
-  </Format>
-
-  <Examples>
-    <Example>
-    ```
-    Job: test-ubuntu / Step: Run tests
-    Error: Cannot find module 'xyz'
-    Cause: Package not installed in CI environment
-    Fix: Add 'xyz' to package.json dependencies
-    Local verification: npm ci && npm test
-    ```
-    </Example>
-  </Examples>
-
-  <Constraint>
-    - Fixes must work on all platforms (Ubuntu, macOS, Windows)
-    - Don't disable failing tests to make CI pass
-    - Preserve existing CI/CD functionality
-    - Consider impact on build time and resource usage
-  </Constraint>
-
-  <SuccessCriteria>
-    <Criterion>All GitHub Actions jobs pass on next run</Criterion>
-    <Criterion>No reduction in test coverage or quality checks</Criterion>
-    <Criterion>Fixes are robust against common CI/CD issues</Criterion>
-    <Criterion>Clear documentation of what was fixed and why</Criterion>
-  </SuccessCriteria>
-</Prompt>

package/prompts/fix-test-errors.prompt

@@ -1,73 +0,0 @@
-{/* Converted from fix-test-errors.md */}
-<Prompt name="fix-lint-build-test-errors" description="Fix Lint, Build, Test Errors" tags={[]}>
-  <Role preset="engineer" extend expertise="debugging, testing, JavaScript/TypeScript, build tools">
-    You are a debugging expert with deep knowledge of JavaScript/TypeScript, testing frameworks, and build tools.
-  </Role>
-
-  <Task>
-    Systematically identify and fix all build, lint, and test errors in the codebase.
-  </Task>
-
-  <Constraints extend>
-    - IMPORTANT: Before making ANY changes, understand the CONTEXT of why tests might be failing
-    - Check recent changes, removed features, or intentional modifications
-    - Run commands in this exact order: `npm run build`, `npm run lint`, `npm test`
-    - Capture ALL error output completely (stdout and stderr)
-    - Categorize errors by type: syntax, type, lint, test assertion, runtime
-    - For each error:
-      1. Identify the specific file and line number
-      2. Understand what the code is trying to do
-      3. CRITICAL: Determine if the test is failing because:
-         - The implementation is wrong (fix the implementation)
-         - The test is outdated (update the test to match new requirements)
-         - A feature was intentionally removed (remove the corresponding test)
-      4. Fix the root cause with minimal code changes
-      5. Verify the specific error is resolved
-    - After fixing all errors, run ALL commands again to verify
-    - MANDATORY: Show complete test output proving "0 failing" before declaring success
-    - If new errors appear, repeat the process
-    - Continue until all commands pass with zero errors
-  </Constraints>
-
-  <Format>
-    1. Context analysis (recent changes, removed features)
-    2. Initial error inventory (categorized list)
-    3. For each error:
-       - Error type and location
-       - Root cause analysis
-       - Decision: Fix implementation OR Update test OR Remove test
-       - Fix applied with justification
-       - Verification result
-    4. Final status report with COMPLETE command outputs showing:
-       - npm run build: "Compiled successfully"
-       - npm run lint: "0 errors, 0 warnings"
-       - npm test: Full output with "0 failing"
-  </Format>
-
-  <Examples>
-    <Example>
-    ```
-    Error 1: TypeError at src/utils/helper.ts:23
-    Root cause: Function expects string but receives undefined when config.name is not set
-    Fix: Add default parameter value
-    Verification: Error resolved, test now passes
-    ```
-    </Example>
-  </Examples>
-
-  <Constraint>
-    - NEVER skip tests with .skip() or xit()
-    - NEVER remove failing tests
-    - NEVER suppress errors with ignore comments
-    - Fix root causes, not symptoms
-    - Preserve all existing functionality
-  </Constraint>
-
-  <SuccessCriteria>
-    <Criterion>`npm run build` exits with code 0</Criterion>
-    <Criterion>`npm run lint` reports 0 errors and 0 warnings</Criterion>
-    <Criterion>`npm test` shows all tests passing (100% pass rate)</Criterion>
-    <Criterion>No unhandled errors or warnings in output</Criterion>
-    <Criterion>All original tests still present and passing</Criterion>
-  </SuccessCriteria>
-</Prompt>