pupt 1.4.0 → 2.0.0

package/dist/template/template-engine.js

@@ -1,85 +0,0 @@
-import Handlebars from 'handlebars';
-import { TemplateContext } from './template-context.js';
-import { registerHelpers } from './helpers/index.js';
-import { loadHandlebarsExtensions } from '../utils/handlebars-extensions.js';
-export class TemplateEngine {
-    handlebars;
-    context;
-    config;
-    configDir;
-    noInteractive;
-    constructor(config, configDir, noInteractive = false) {
-        this.handlebars = Handlebars.create();
-        this.context = new TemplateContext();
-        this.config = config;
-        this.configDir = configDir;
-        this.noInteractive = noInteractive;
-    }
-    async processTemplate(template, prompt) {
-        // Create new context with variable definitions
-        this.context = new TemplateContext(prompt.variables, this.noInteractive);
-        // Create a special Handlebars instance that has access to the context
-        this.handlebars = Handlebars.create();
-        // Load Handlebars extensions from config
-        if (this.config?.handlebarsExtensions) {
-            await loadHandlebarsExtensions(this.handlebars, this.config.handlebarsExtensions, this.configDir);
-        }
-        // Register helpers with context
-        registerHelpers(this.handlebars, this.context);
-        // Pre-process template to extract and protect raw blocks
-        const rawBlocks = [];
-        let rawIndex = 0;
-        // Extract content from {{#raw}}...{{/raw}} blocks before Handlebars processes them
-        template = template.replace(/{{#raw}}([\s\S]*?){{\/raw}}/g, (match, content) => {
-            const placeholder = `__RAW_BLOCK_${rawIndex++}__`;
-            rawBlocks.push({ placeholder, content });
-            return placeholder;
-        });
-        // Phase 1: Replace variable references with temporary placeholders
-        // to prevent them from being processed before values are available
-        const varPattern = /\{\{([^{}\s]+)\}\}/g;
-        const inputHelperPattern = /\{\{(input|select|multiselect|confirm|editor|password)\s+[^}]+\}\}/g;
-        // Store variable references to restore later
-        const variableRefs = [];
-        let tempTemplate = template;
-        let varIndex = 0;
-        // Replace non-helper variable references with placeholders
-        tempTemplate = tempTemplate.replace(varPattern, (match, varName) => {
-            // Check if this is a helper call
-            if (match.match(inputHelperPattern)) {
-                return match; // Keep helper calls as-is
-            }
-            const placeholder = `__VAR_${varIndex++}__`;
-            variableRefs.push({ placeholder, variable: varName });
-            return placeholder;
-        });
-        // Phase 2: Process helpers with the temporary template
-        const compiled = this.handlebars.compile(tempTemplate, { noEscape: true });
-        let result = compiled({});
-        // Process async operations (input helpers)
-        result = await this.context.processAsyncOperations(result);
-        // Phase 3: Restore variable references
-        for (const ref of variableRefs) {
-            result = result.replace(ref.placeholder, `{{${ref.variable}}}`);
-        }
-        // Phase 4: Final compilation with all values available
-        const finalCompiled = this.handlebars.compile(result, { noEscape: true });
-        const contextData = {};
-        // Add all collected values to context data
-        for (const [key, value] of this.context.getAllValues()) {
-            contextData[key] = value;
-        }
-        let finalResult = finalCompiled(contextData);
-        // Restore raw blocks
-        for (const block of rawBlocks) {
-            finalResult = finalResult.replace(block.placeholder, block.content);
-        }
-        // Restore escaped Handlebars syntax from user input
-        finalResult = finalResult.replace(/__ESCAPED_OPEN__/g, '{{').replace(/__ESCAPED_CLOSE__/g, '}}');
-        return finalResult;
-    }
-    getContext() {
-        return this.context;
-    }
-}
-//# sourceMappingURL=template-engine.js.map

package/dist/template/template-engine.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"template-engine.js","sourceRoot":"","sources":["../../src/template/template-engine.ts"],"names":[],"mappings":"AAAA,OAAO,UAAU,MAAM,YAAY,CAAC;AACpC,OAAO,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AACxD,OAAO,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AAErD,OAAO,EAAE,wBAAwB,EAAE,MAAM,mCAAmC,CAAC;AAG7E,MAAM,OAAO,cAAc;IACjB,UAAU,CAAoB;IAC9B,OAAO,CAAkB;IACzB,MAAM,CAAU;IAChB,SAAS,CAAU;IACnB,aAAa,CAAU;IAE/B,YAAY,MAAe,EAAE,SAAkB,EAAE,aAAa,GAAG,KAAK;QACpE,IAAI,CAAC,UAAU,GAAG,UAAU,CAAC,MAAM,EAAE,CAAC;QACtC,IAAI,CAAC,OAAO,GAAG,IAAI,eAAe,EAAE,CAAC;QACrC,IAAI,CAAC,MAAM,GAAG,MAAM,CAAC;QACrB,IAAI,CAAC,SAAS,GAAG,SAAS,CAAC;QAC3B,IAAI,CAAC,aAAa,GAAG,aAAa,CAAC;IACrC,CAAC;IAED,KAAK,CAAC,eAAe,CAAC,QAAgB,EAAE,MAAuB;QAC7D,+CAA+C;QAC/C,IAAI,CAAC,OAAO,GAAG,IAAI,eAAe,CAAC,MAAM,CAAC,SAAS,EAAE,IAAI,CAAC,aAAa,CAAC,CAAC;QAEzE,sEAAsE;QACtE,IAAI,CAAC,UAAU,GAAG,UAAU,CAAC,MAAM,EAAE,CAAC;QAEtC,yCAAyC;QACzC,IAAI,IAAI,CAAC,MAAM,EAAE,oBAAoB,EAAE,CAAC;YACtC,MAAM,wBAAwB,CAAC,IAAI,CAAC,UAAU,EAAE,IAAI,CAAC,MAAM,CAAC,oBAAoB,EAAE,IAAI,CAAC,SAAS,CAAC,CAAC;QACpG,CAAC;QAED,gCAAgC;QAChC,eAAe,CAAC,IAAI,CAAC,UAAU,EAAE,IAAI,CAAC,OAAO,CAAC,CAAC;QAE/C,yDAAyD;QACzD,MAAM,SAAS,GAAoD,EAAE,CAAC;QACtE,IAAI,QAAQ,GAAG,CAAC,CAAC;QAEjB,mFAAmF;QACnF,QAAQ,GAAG,QAAQ,CAAC,OAAO,CAAC,8BAA8B,EAAE,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE;YAC7E,MAAM,WAAW,GAAG,eAAe,QAAQ,EAAE,IAAI,CAAC;YAClD,SAAS,CAAC,IAAI,CAAC,EAAE,WAAW,EAAE,OAAO,EAAE,CAAC,CAAC;YACzC,OAAO,WAAW,CAAC;QACrB,CAAC,CAAC,CAAC;QAEH,mEAAmE;QACnE,mEAAmE;QACnE,MAAM,UAAU,GAAG,qBAAqB,CAAC;QACzC,MAAM,kBAAkB,GACtB,qEAAqE,CAAC;QAExE,6CAA6C;QAC7C,MAAM,YAAY,GAAqD,EAAE,CAAC;QAC1E,IAAI,YAAY,GAAG,QAAQ,CAAC;QAC5B,IAAI,QAAQ,GAAG,CAAC,CAAC;QAEjB,2DAA2D;QAC3D,YAAY,GAAG,YAAY,CAAC,OAAO,CAAC,UAAU,EAAE,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE;YACjE,iCAAiC;YACjC,IAAI,KAAK,CAAC,KAAK,CAAC,kBAAkB,CAAC,EAAE,CAAC;gBACpC,OAAO,KAAK,CAAC,CAAC,0BAA0B;YAC1C,CAAC;YACD,MAAM,WAAW,GAAG,SAAS,QAAQ,EAAE,IAAI,CAAC;YAC5C,YAAY,CAAC,IAAI,CAAC,EAAE,WAAW,EAAE,QAAQ,EAAE,OAAO,EAAE,CAAC,CAAC;YACtD,OAAO,WAAW,CAAC;QACrB,CAAC,CAAC,CAAC;QAEH,uDAAuD;QACvD,MAAM,QAAQ,GAAG,IAAI,CAAC,UAAU,CAAC,OAAO,CAAC,YAAY,EAAE,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC;QAC3E,IAAI,MAAM,GAAG,QAAQ,CAAC,EAAE,CAAC,CAAC;QAE1B,2CAA2C;QAC3C,MAAM,GAAG,MAAM,IAAI,CAAC,OAAO,CAAC,sBAAsB,CAAC,MAAM,CAAC,CAAC;QAE3D,uCAAuC;QACvC,KAAK,MAAM,GAAG,IAAI,YAAY,EAAE,CAAC;YAC/B,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,GAAG,CAAC,WAAW,EAAE,KAAK,GAAG,CAAC,QAAQ,IAAI,CAAC,CAAC;QAClE,CAAC;QAED,uDAAuD;QACvD,MAAM,aAAa,GAAG,IAAI,CAAC,UAAU,CAAC,OAAO,CAAC,MAAM,EAAE,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC;QAC1E,MAAM,WAAW,GAA4B,EAAE,CAAC;QAEhD,2CAA2C;QAC3C,KAAK,MAAM,CAAC,GAAG,EAAE,KAAK,CAAC,IAAI,IAAI,CAAC,OAAO,CAAC,YAAY,EAAE,EAAE,CAAC;YACvD,WAAW,CAAC,GAAG,CAAC,GAAG,KAAK,CAAC;QAC3B,CAAC;QAED,IAAI,WAAW,GAAG,aAAa,CAAC,WAAW,CAAC,CAAC;QAE7C,qBAAqB;QACrB,KAAK,MAAM,KAAK,IAAI,SAAS,EAAE,CAAC;YAC9B,WAAW,GAAG,WAAW,CAAC,OAAO,CAAC,KAAK,CAAC,WAAW,EAAE,KAAK,CAAC,OAAO,CAAC,CAAC;QACtE,CAAC;QAED,oDAAoD;QACpD,WAAW,GAAG,WAAW,CAAC,OAAO,CAAC,mBAAmB,EAAE,IAAI,CAAC,CAAC,OAAO,CAAC,oBAAoB,EAAE,IAAI,CAAC,CAAC;QAEjG,OAAO,WAAW,CAAC;IACrB,CAAC;IAED,UAAU;QACR,OAAO,IAAI,CAAC,OAAO,CAAC;IACtB,CAAC;CACF"}

package/dist/utils/handlebars-extensions.d.ts

@@ -1,4 +0,0 @@
-import type { HandlebarsExtensionConfig } from '../types/config.js';
-import type Handlebars from 'handlebars';
-export declare function loadHandlebarsExtensions(handlebars: typeof Handlebars, extensions: HandlebarsExtensionConfig[], configDir?: string): Promise<void>;
-//# sourceMappingURL=handlebars-extensions.d.ts.map

package/dist/utils/handlebars-extensions.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"handlebars-extensions.d.ts","sourceRoot":"","sources":["../../src/utils/handlebars-extensions.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,oBAAoB,CAAC;AACpE,OAAO,KAAK,UAAU,MAAM,YAAY,CAAC;AAEzC,wBAAsB,wBAAwB,CAC5C,UAAU,EAAE,OAAO,UAAU,EAC7B,UAAU,EAAE,yBAAyB,EAAE,EACvC,SAAS,CAAC,EAAE,MAAM,GACjB,OAAO,CAAC,IAAI,CAAC,CAIf"}

package/dist/utils/handlebars-extensions.js

@@ -1,87 +0,0 @@
-import * as vm from 'node:vm';
-import * as path from 'node:path';
-import { promises as fs } from 'node:fs';
-export async function loadHandlebarsExtensions(handlebars, extensions, configDir) {
-    for (const extension of extensions) {
-        await loadSingleExtension(handlebars, extension, configDir);
-    }
-}
-async function loadSingleExtension(handlebars, config, configDir) {
-    if (config.type === 'inline') {
-        await loadInlineExtension(handlebars, config);
-    }
-    else if (config.type === 'file') {
-        await loadFileExtension(handlebars, config, configDir);
-    }
-    else {
-        throw new Error(`Invalid extension type: ${config.type || 'unknown'}`);
-    }
-}
-async function loadInlineExtension(handlebars, config) {
-    if (!config.value) {
-        throw new Error('Inline extension value is required');
-    }
-    // Create a sandboxed context for executing the inline code
-    const sandbox = {
-        Handlebars: handlebars,
-        console: console, // Allow console for debugging
-        require: createSafeRequire()
-    };
-    try {
-        // Create a new context for the sandbox
-        const context = vm.createContext(sandbox);
-        // Run the code with a timeout
-        vm.runInContext(config.value, context, {
-            timeout: 5000, // 5 second timeout
-            displayErrors: true
-        });
-    }
-    catch (error) {
-        const message = error instanceof Error ? error.message : String(error);
-        throw new Error(`Failed to load inline Handlebars extension: ${message}`);
-    }
-}
-// Create a safe require function that blocks dangerous modules
-function createSafeRequire() {
-    return (id) => {
-        const blockedModules = ['fs', 'child_process', 'net', 'http', 'https', 'os', 'path', 'crypto'];
-        if (blockedModules.includes(id)) {
-            throw new Error(`Module '${id}' is not allowed in inline extensions`);
-        }
-        throw new Error(`require() is not available in inline extensions`);
-    };
-}
-async function loadFileExtension(handlebars, config, configDir) {
-    if (!config.path) {
-        throw new Error('File extension path is required');
-    }
-    // Resolve path relative to config directory if provided
-    const extensionPath = configDir
-        ? path.resolve(configDir, config.path)
-        : path.resolve(config.path);
-    try {
-        // Check if file exists
-        await fs.access(extensionPath);
-    }
-    catch {
-        throw new Error(`Extension file not found: ${extensionPath}`);
-    }
-    try {
-        // Use dynamic import for ESM compatibility
-        const extensionModule = await import(extensionPath);
-        const extension = extensionModule.default || extensionModule;
-        if (typeof extension !== 'function') {
-            throw new Error(`Extension file must export a function, got ${typeof extension}`);
-        }
-        // Call the extension function with Handlebars instance
-        await extension(handlebars);
-    }
-    catch (error) {
-        if (error instanceof Error && error.message.includes('Extension file must export')) {
-            throw error;
-        }
-        const message = error instanceof Error ? error.message : String(error);
-        throw new Error(`Failed to load file Handlebars extension: ${message}`);
-    }
-}
-//# sourceMappingURL=handlebars-extensions.js.map

package/dist/utils/handlebars-extensions.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"handlebars-extensions.js","sourceRoot":"","sources":["../../src/utils/handlebars-extensions.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAClC,OAAO,EAAE,QAAQ,IAAI,EAAE,EAAE,MAAM,SAAS,CAAC;AAIzC,MAAM,CAAC,KAAK,UAAU,wBAAwB,CAC5C,UAA6B,EAC7B,UAAuC,EACvC,SAAkB;IAElB,KAAK,MAAM,SAAS,IAAI,UAAU,EAAE,CAAC;QACnC,MAAM,mBAAmB,CAAC,UAAU,EAAE,SAAS,EAAE,SAAS,CAAC,CAAC;IAC9D,CAAC;AACH,CAAC;AAED,KAAK,UAAU,mBAAmB,CAChC,UAA6B,EAC7B,MAAiC,EACjC,SAAkB;IAElB,IAAI,MAAM,CAAC,IAAI,KAAK,QAAQ,EAAE,CAAC;QAC7B,MAAM,mBAAmB,CAAC,UAAU,EAAE,MAAM,CAAC,CAAC;IAChD,CAAC;SAAM,IAAI,MAAM,CAAC,IAAI,KAAK,MAAM,EAAE,CAAC;QAClC,MAAM,iBAAiB,CAAC,UAAU,EAAE,MAAM,EAAE,SAAS,CAAC,CAAC;IACzD,CAAC;SAAM,CAAC;QACN,MAAM,IAAI,KAAK,CAAC,2BAA4B,MAA4B,CAAC,IAAI,IAAI,SAAS,EAAE,CAAC,CAAC;IAChG,CAAC;AACH,CAAC;AAED,KAAK,UAAU,mBAAmB,CAChC,UAA6B,EAC7B,MAAiC;IAEjC,IAAI,CAAC,MAAM,CAAC,KAAK,EAAE,CAAC;QAClB,MAAM,IAAI,KAAK,CAAC,oCAAoC,CAAC,CAAC;IACxD,CAAC;IAED,2DAA2D;IAC3D,MAAM,OAAO,GAAG;QACd,UAAU,EAAE,UAAU;QACtB,OAAO,EAAE,OAAO,EAAE,8BAA8B;QAChD,OAAO,EAAE,iBAAiB,EAAE;KAC7B,CAAC;IAEF,IAAI,CAAC;QACH,uCAAuC;QACvC,MAAM,OAAO,GAAG,EAAE,CAAC,aAAa,CAAC,OAAO,CAAC,CAAC;QAE1C,8BAA8B;QAC9B,EAAE,CAAC,YAAY,CAAC,MAAM,CAAC,KAAK,EAAE,OAAO,EAAE;YACrC,OAAO,EAAE,IAAI,EAAE,mBAAmB;YAClC,aAAa,EAAE,IAAI;SACpB,CAAC,CAAC;IACL,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,OAAO,GAAG,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;QACvE,MAAM,IAAI,KAAK,CAAC,+CAA+C,OAAO,EAAE,CAAC,CAAC;IAC5E,CAAC;AACH,CAAC;AAED,+DAA+D;AAC/D,SAAS,iBAAiB;IACxB,OAAO,CAAC,EAAU,EAAE,EAAE;QACpB,MAAM,cAAc,GAAG,CAAC,IAAI,EAAE,eAAe,EAAE,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,QAAQ,CAAC,CAAC;QAC/F,IAAI,cAAc,CAAC,QAAQ,CAAC,EAAE,CAAC,EAAE,CAAC;YAChC,MAAM,IAAI,KAAK,CAAC,WAAW,EAAE,uCAAuC,CAAC,CAAC;QACxE,CAAC;QACD,MAAM,IAAI,KAAK,CAAC,iDAAiD,CAAC,CAAC;IACrE,CAAC,CAAC;AACJ,CAAC;AAED,KAAK,UAAU,iBAAiB,CAC9B,UAA6B,EAC7B,MAAiC,EACjC,SAAkB;IAElB,IAAI,CAAC,MAAM,CAAC,IAAI,EAAE,CAAC;QACjB,MAAM,IAAI,KAAK,CAAC,iCAAiC,CAAC,CAAC;IACrD,CAAC;IAED,wDAAwD;IACxD,MAAM,aAAa,GAAG,SAAS;QAC7B,CAAC,CAAC,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,MAAM,CAAC,IAAI,CAAC;QACtC,CAAC,CAAC,IAAI,CAAC,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC;IAE9B,IAAI,CAAC;QACH,uBAAuB;QACvB,MAAM,EAAE,CAAC,MAAM,CAAC,aAAa,CAAC,CAAC;IACjC,CAAC;IAAC,MAAM,CAAC;QACP,MAAM,IAAI,KAAK,CAAC,6BAA6B,aAAa,EAAE,CAAC,CAAC;IAChE,CAAC;IAED,IAAI,CAAC;QACH,2CAA2C;QAC3C,MAAM,eAAe,GAAG,MAAM,MAAM,CAAC,aAAa,CAAC,CAAC;QACpD,MAAM,SAAS,GAAG,eAAe,CAAC,OAAO,IAAI,eAAe,CAAC;QAE7D,IAAI,OAAO,SAAS,KAAK,UAAU,EAAE,CAAC;YACpC,MAAM,IAAI,KAAK,CAAC,8CAA8C,OAAO,SAAS,EAAE,CAAC,CAAC;QACpF,CAAC;QAED,uDAAuD;QACvD,MAAM,SAAS,CAAC,UAAU,CAAC,CAAC;IAC9B,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,IAAI,KAAK,YAAY,KAAK,IAAI,KAAK,CAAC,OAAO,CAAC,QAAQ,CAAC,4BAA4B,CAAC,EAAE,CAAC;YACnF,MAAM,KAAK,CAAC;QACd,CAAC;QACD,MAAM,OAAO,GAAG,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;QACvE,MAAM,IAAI,KAAK,CAAC,6CAA6C,OAAO,EAAE,CAAC,CAAC;IAC1E,CAAC;AACH,CAAC"}

package/prompts/ad-hoc-long.md

@@ -1,52 +0,0 @@
----
-title: Ad Hoc (Long)
-author: Adam Powers <apowers@ato.ms>
-creationDate: 20250816
-tags: []
----
-
-**Role & Context**: You are a versatile expert assistant capable of handling complex, multi-part requests that require detailed analysis, planning, or implementation.
-
-**Objective**: Address the comprehensive request below with appropriate depth and thoroughness.
-
-**Specific Requirements**:
-- 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
-
-**Format & Structure**: 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**:
-{{editor "prompt"}}
-
-**Examples**: N/A (varies by request type)
-
-**Constraints**: 
-- Maintain focus on the specific request
-- Balance thoroughness with clarity
-- Use examples and code samples where helpful
-- Flag any assumptions or uncertainties
-
-**Success Criteria**: 
-- All parts of the request are addressed
-- Response is well-organized and easy to follow
-- Solutions are practical and implementable
-- Any edge cases or considerations are noted

package/prompts/ad-hoc.md

@@ -1,23 +0,0 @@
----
-title: Ad Hoc
-author: Adam Powers <apowers@ato.ms>
-creationDate: 20250814
-tags: []
----
-
-**Role & Context**: You are a versatile AI assistant capable of handling various technical and non-technical tasks. Adapt your expertise based on the specific request.
-
-**Objective**: {{input "prompt"}}
-
-**Specific Requirements**:
-- Provide accurate, helpful, and actionable responses
-- If the task is ambiguous, ask clarifying questions before proceeding
-- Use appropriate formatting (code blocks, lists, tables) based on content type
-
-**Format & Structure**: Match the response format to the task type - use structured output for technical tasks, narrative for explanations, and step-by-step instructions for procedures.
-
-**Examples**: N/A (varies by request)
-
-**Constraints**: Stay focused on the specific request without adding unnecessary information unless it directly supports the main objective.
-
-**Success Criteria**: The response directly addresses the user's request with appropriate depth and format for the task at hand.

package/prompts/add-summary.md

@@ -1,42 +0,0 @@
----
-title: Update Prompt Summary
-summary: Update summary field in {{file "prompt"}} for better history display
-variables:
-  - name: prompt
-    type: file
-    message: "Select the prompt file to update"
-    filter: "*.md"
-    basePath: "."
----
-
-**Role & Context**: You are an expert at creating concise, informative summaries for prompt templates. You understand YAML frontmatter and Handlebars templating.
-
-**Objective**: Add or update the summary field for the following prompt file to improve its display in `pt history`.
-
-## Current Prompt File:
-{{file "prompt"}}
-
-**Specific Requirements**:
-- Create a single-line summary that clearly describes what the prompt does
-- Use Handlebars syntax to reference variables from the prompt (e.g., `{{file "design"}}`, `{{reviewFile "output"}}`)
-- Keep the summary under 80 characters for optimal display
-- Focus on the action/outcome rather than implementation details
-- Preserve all existing frontmatter fields when updating
-
-**Format & Structure**: 
-- If the file already has a `summary:` field, replace it with the new one
-- If the file has frontmatter but no summary, add the `summary:` field to it
-- If the file lacks frontmatter, create a minimal frontmatter section with at least title and summary
-- Output the complete updated file content that can be directly saved
-
-**Examples**:
-- `summary: Create React component {{input "name"}} with tests`
-- `summary: Review {{file "code"}} and suggest improvements`
-- `summary: Generate API client for {{select "service"}} using {{select "language"}}`
-
-**Constraints**: 
-- Maintain the exact formatting and structure of the existing file
-- Only modify the frontmatter section
-- Ensure the summary accurately reflects the prompt's purpose
-
-**Success Criteria**: The updated prompt file should have a clear, concise summary that will be displayed in `pt history` output.

package/prompts/analyze-execution.md

@@ -1,181 +0,0 @@
----
-title: Analyze Prompt Execution
-description: Automatically analyze prompt execution output to extract structured annotation data
-author: AI Analysis System
-tags: [auto-annotation, analysis]
----
-
-**Role & Context**: You are an expert AI conversation analyst specializing in intent extraction and alignment validation. You analyze AI execution transcripts to determine if the AI truly understood and fulfilled the user's intent, not just completed surface-level tasks.
-
-**Objective**: Extract the user's true intent from their prompt, then analyze whether the AI's execution aligned with that intent, regardless of technical success metrics.
-
-**Critical First Step - Intent Extraction**:
-
-Carefully analyze the user's prompt to extract:
-
-1. **Explicit Goals**: What the user directly asked for
-2. **Contextual Requirements**: HOW they want it done (look for phrases like "make sure", "important", "before doing X")
-3. **Constraints**: What NOT to do (look for "never", "don't", "avoid", "instead of")
-4. **Underlying Problem**: What problem is the user actually trying to solve?
-5. **Implicit Expectations**: What would a human understand from context that isn't explicitly stated?
-
-Pay special attention to:
-- "IMPORTANT", "CRITICAL", "MANDATORY" - these signal key requirements
-- Conditional instructions ("if X then Y")
-- Context about recent changes or intentional modifications
-- The difference between fixing symptoms vs root causes
-
-**Second Step - AI Understanding Analysis**:
-
-Examine the AI's responses for evidence it understood the intent:
-- Did it acknowledge the context and constraints?
-- Did it explain its understanding of the task?
-- Did it mention why it chose a particular approach?
-- Did it recognize conditional requirements?
-
-Red flags for misunderstanding:
-- Jumping straight to implementation without acknowledging context
-- No mention of constraints or special requirements
-- Treating all instructions as equally important
-- Missing the "why" behind the request
-
-**Third Step - Intent Alignment Validation**:
-
-Compare the AI's actions against extracted intent:
-
-**ALIGNED**:
-- AI's approach matches user's intended method
-- Constraints and requirements were respected
-- The underlying problem was addressed, not just symptoms
-- Context was properly considered
-
-**MISALIGNED**:
-- AI solved a different problem than intended
-- Explicit constraints were violated
-- The approach contradicts the user's context
-- Technical success but semantic failure
-
-**Success Criteria (Intent-Based)**:
-
-- **SUCCESS**: AI understood and fulfilled the user's actual intent
-- **PARTIAL**: AI partially understood but missed some aspects of intent
-- **FAILURE**: AI misunderstood intent or violated key constraints
-
-**Analysis Process**:
-
-1. **Extract Intent** - What did the user REALLY want?
-2. **Analyze Understanding** - Did the AI grasp the intent?
-3. **Validate Alignment** - Did actions match intent?
-4. **Identify Gaps** - Where did alignment fail?
-5. **Assess Severity** - How badly did it miss the mark?
-6. **Detect user redirects and off-track execution**
-
-**User Redirect Detection Patterns**:
-
-Look for these phrases from users that indicate redirection:
-- "No, I meant..." / "Actually, I meant..."
-- "Wait, why are you..." / "What are you doing?"
-- "Not that, I want..." / "That's not what I asked for"
-- Multiple rapid user inputs (indicates confusion)
-- "Wrong [file/folder/approach]"
-- "Stop" / "Hold on" / "Let me clarify"
-
-**Off-Track Execution Patterns**:
-
-Look for AI behaviors that indicate deviation:
-- Analyzing unrelated systems when asked about specific components
-- Implementing different technology than requested
-- Working in wrong directories or files
-- Performing extensive analysis when asked for simple tasks
-- User having to repeat or rephrase instructions
-
-**Issue Categories** (in order of severity):
-
-1. **intent_not_understood**: AI fundamentally misunderstood what user wanted
-   - Evidence: AI does opposite of request, ignores core requirement
-
-2. **constraint_violated**: AI understood goal but violated explicit constraints
-   - Evidence: User said "don't do X" but AI did X
-   
-3. **wrong_approach**: AI understood goal but used inappropriate method
-   - Evidence: User wanted tests updated, AI changed implementation
-
-4. **context_ignored**: AI missed critical contextual information
-   - Evidence: User mentioned "feature was removed" but AI reimplemented it
-   
-5. **partial_intent**: Only part of the user's intent was addressed
-   - Evidence: Multiple requirements but only some fulfilled
-
-6. **assumption_mismatch**: AI made assumptions that conflicted with user's intent
-   - Evidence: AI assumed user wanted one thing when context indicated another
-
-7. **verification_gap**: Missing tests/verification (DEVELOPMENT TASKS ONLY)
-   - Evidence: No verification after code changes
-
-8. **user_redirect**: User had to correct or redirect the AI's approach
-   - Evidence: User intervention required to get back on track
-
-9. **off_track_execution**: AI deviated without correction
-   - Evidence: Working on wrong files/systems
-
-**Output Format**: Return ONLY this JSON structure:
-
-```json
-{
-  "status": "success|partial|failure",
-  "intent_summary": "What the user actually wanted to achieve",
-  "alignment_assessment": "Brief explanation of whether AI met the intent",
-  "structured_outcome": {
-    "explicit_goals_met": <number>,
-    "explicit_goals_total": <number>,
-    "constraints_respected": <boolean>,
-    "context_considered": <boolean>,
-    "approach_aligned": <boolean>,
-    "execution_time": "<duration>"
-  },
-  "issues_identified": [
-    {
-      "category": "intent_not_understood|constraint_violated|wrong_approach|context_ignored|partial_intent|assumption_mismatch|verification_gap|user_redirect|off_track_execution",
-      "severity": "low|medium|high|critical",
-      "description": "How the AI's actions diverged from user intent",
-      "evidence": "Specific quote showing the misalignment"
-    }
-  ]
-}
-```
-
-**Example Analysis**:
-
-User prompt: "Fix all test errors. IMPORTANT: Check if tests are failing because features were intentionally removed - if so, update the tests, don't reimplement the features."
-
-AI action: Reimplemented removed features to make tests pass
-
-Analysis:
-```json
-{
-  "status": "failure",
-  "intent_summary": "Fix test errors by updating tests to match intentionally removed features, not by reimplementing features",
-  "alignment_assessment": "AI completely violated the core constraint by reimplementing removed features instead of updating tests",
-  "structured_outcome": {
-    "explicit_goals_met": 1,
-    "explicit_goals_total": 1,
-    "constraints_respected": false,
-    "context_considered": false,
-    "approach_aligned": false,
-    "execution_time": "487s"
-  },
-  "issues_identified": [{
-    "category": "constraint_violated",
-    "severity": "critical",
-    "description": "AI reimplemented removed features despite explicit instruction to update tests instead",
-    "evidence": "Removed .txt file creation from OutputCaptureService - Now only creates JSON files"
-  }]
-}
-```
-
-**CRITICAL RULES**:
-- Focus on INTENT, not just task completion
-- Technical success with intent failure = FAILURE
-- Always extract implicit requirements from context
-- A perfectly executing AI that solves the wrong problem has failed
-- Return ONLY the JSON, no other text

package/prompts/code-review.md

@@ -1,97 +0,0 @@
----
-title: Code Review
-author: Adam Powers <apowers@ato.ms>
-creationDate: 20250815
-tags: []
----
-
-**Role & Context**: 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.
-
-**Objective**: Perform a comprehensive multi-pass code review identifying issues and improvement opportunities. Write the code review to {{reviewFile "outputFile"}}.
-
-**Specific Requirements**:
-- **Pass 1 - Critical Issues**: Security, correctness, data loss risks
-- **Pass 2 - Code Quality**: 
-  {{editor "codeReviewConcerns"}}
-- **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
-
-**Format & Structure**: 
-```markdown
-# Code Review Report - {{date}}
-
-## 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]
-...
-```
-
-**Examples**: Included in format above
-
-**Constraints**: 
-- 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
-
-**Success Criteria**: 
-- All significant issues caught and correctly prioritized
-- Fixes are specific and implementable
-- Report enables systematic remediation
-- No false positives that waste developer time
-
-Write the report to {{reviewFile "outputFile"}}.

package/prompts/debugging-error-message.md

@@ -1,75 +0,0 @@
----
-title: Debugging Error Message
-author: Adam Powers <apowers@ato.ms>
-creationDate: 20250814
-tags: []
----
-
-**Role & Context**: You are a debugging specialist with expertise in error analysis, root cause identification, and systematic problem-solving in software systems.
-
-**Objective**: Diagnose and fix all errors that occur when {{input "errorCondition"}}.
-
-**Specific Requirements**:
-- 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
-
-**Format & Structure**: 
-```markdown
-## Error Analysis for: {{errorCondition}}
-
-### Complete Error Output
-```
-{{editor "errorText"}}
-```
-
-### 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]
-```
-
-**Examples**: 
-```
-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
-```
-
-**Constraints**: 
-- 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
-
-**Success Criteria**: 
-- Original error condition no longer produces any errors
-- All fixes address root causes
-- No new errors introduced
-- Clear documentation of what was wrong and how it was fixed