@decaf-ts/mcp-server 0.4.9 → 0.4.16

package/lib/esm/prompts/jsdocs/class-prompt.js

@@ -1,52 +0,0 @@
-import { z } from "zod";
-import { BaseJSDocPrompt, Footer } from "./constants.js";
-import { PromptBuilder } from "./../../builders/prompt-builder.js";
-import { ReasoningLevel } from "./../../constants.js";
-const promptName = "ts.jsdoc.class";
-const argsSchema = z.object({});
-export const TsDocClassPrompt = PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Class JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript class according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setReasoning(ReasoningLevel.BASIC)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${BaseJSDocPrompt}
-document the entire class and each of its functions including always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.
-Include @class tags when applicable.
-include @param tags in the class documentation and its type definitions
-Include detailed @description for all properties.
-Include @template tags when necessary.
-Do NOT document the constructor, but include the constructor arguments as @param in the class documentation
-For methods and functions:
-- include @description and @summary tags as defined for the target. also document every argument, including its type definition, and return type, referencing @template tags when necessary.
-- create a usage example under the @example tag on the class documentation
-- create mermaid sequence diagrams under the @mermaid tag;
-
-The order of tags (when applicable) should be as follows:
-1 - @description;
-2 - @summary;
-3 - @template;
-4 - @param;
-5 - @return;
-6 - @class
-7 - @example
-8 - @mermaid;
-
-ignore @mermaid for methods with less that 15 lines and constructors.
-Respond only with the full JSDoc comment block for the class and its methods.
-NEVER user @memberOf in the class or any of it's methods
-if the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information
-never omit or change any code, including the constructor
-${Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-        _meta: {},
-    };
-    return result;
-});
-//# sourceMappingURL=class-prompt.js.map

package/lib/esm/prompts/jsdocs/class-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"class-prompt.js","sourceRoot":"","sources":["../../../../src/prompts/jsdocs/class-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,eAAe,EAAE,MAAM,EAAE,uBAAoB;AAOtD,OAAO,EAAE,aAAa,EAAE,2CAAsC;AAC9D,OAAO,EAAE,cAAc,EAAE,6BAAwB;AAEjD,MAAM,UAAU,GAAG,gBAAgB,CAAC;AAEpC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGhC,MAAM,CAAC,MAAM,gBAAgB,GAAkB,aAAa,CAAC,OAAO;KACjE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,qBAAqB,CAAC;KAC/B,cAAc,CACb,4FAA4F,CAC7F;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,YAAY,CAAC,cAAc,CAAC,KAAK,CAAC;KAClC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,eAAe;;;;;;;;;;;;;;;;;;;;;;;;;;;EA2BrC,MAAM,EAAE,CAAC;IACL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;QACrE,KAAK,EAAE,EAAE;KACV,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/esm/prompts/jsdocs/const-prompt.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const TsDocConstPrompt: PromptBuilder;

package/lib/esm/prompts/jsdocs/const-prompt.js

@@ -1,24 +0,0 @@
-import { z } from "zod";
-import { BaseJSDocPrompt, ConstantsPrompt, Footer } from "./constants.js";
-import { PromptBuilder } from "./../../builders/prompt-builder.js";
-const promptName = "ts.jsdoc.const";
-const argsSchema = z.object({});
-export const TsDocConstPrompt = PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Const JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript constant according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${BaseJSDocPrompt}
-${ConstantsPrompt}
-${Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-    };
-    return result;
-});
-//# sourceMappingURL=const-prompt.js.map

package/lib/esm/prompts/jsdocs/const-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"const-prompt.js","sourceRoot":"","sources":["../../../../src/prompts/jsdocs/const-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,eAAe,EAAE,eAAe,EAAE,MAAM,EAAE,uBAAoB;AAOvE,OAAO,EAAE,aAAa,EAAE,2CAAsC;AAE9D,MAAM,UAAU,GAAG,gBAAgB,CAAC;AAEpC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGhC,MAAM,CAAC,MAAM,gBAAgB,GAAkB,aAAa,CAAC,OAAO;KACjE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,qBAAqB,CAAC;KAC/B,cAAc,CACb,+FAA+F,CAChG;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,eAAe;EACrC,eAAe;EACf,MAAM,EAAE,CAAC;IAEL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;KACtE,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/esm/prompts/jsdocs/constants.d.ts

@@ -1,4 +0,0 @@
-export declare const BaseJSDocPrompt = "You're a senior TypeScript developer writing JSDoc documentation for a class to be used with better-docs. Given the module code:\nGenerate a JSDoc comment block for a TypeScript module file using better-docs formatting:";
-export declare const TypesPrompt = "document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.\n  Include @interface and @typeDef an @template tags when appropriate.\n  Include detailed @description for all properties.\n  For methods, include @description and @summary tags as defined for the target. also document every argument, including its type definition, and return type, referencing @template tags when necessary.\n\n  The order of tags  (when applicable) should be as follows:\n1 - @description;\n2 - @summary;\n3 - @template;\n4 - @param;\n5 - @return;\n6 - @interface or @typeDef followed by the interface or type name;\n8 - @memberOf referencing the appropriate module using the appropriate syntax\n\nOutput only the completed JSDoc comment block for the type or interface.\nrefer to the module it belongs with @memberOf this the `@memberOf module:<module_name>` syntax\nnever omit or change any code\nif the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information";
-export declare const ConstantsPrompt = "document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.\nInclude @const and @typeDef tags when appropriate.\nInclude detailed @description for all properties.\n- For enums, include @enum and @readonly, and add inline documentation for each member\n- For object-like constants:\n    - Create a @typedef with @property for each key\n    - Reference it in the constant using @type\n    - Alternatively, document each key inline if small\n\nThe order of tags  (when applicable) should be as follows:\n1 - @description;\n2 - @summary;\n3 - @template;\n4 - @property;\n6 - @const followed by the const or enum name;\n8 - @memberOf referencing the appropriate module using the appropriate syntax\n\nRespond with the JSDoc comment block(s) for both the typedef and the constant or enum.\nrefer to the module it belongs with @memberOf this the `@memberOf module:<module_name>` syntax\nnever omit or change any code\nif the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information";
-export declare const Footer = "NOTES:\n - when document a function/method parameters, and there is a template type involved, ALWAYS reference it using the @template tag;\n - when documenting a function type as a parameter, ALWAYS use the function(type1,type2):return_type syntax;\n ";

package/lib/esm/prompts/jsdocs/constants.js

@@ -1,46 +0,0 @@
-export const BaseJSDocPrompt = `You're a senior TypeScript developer writing JSDoc documentation for a class to be used with better-docs. Given the module code:
-Generate a JSDoc comment block for a TypeScript module file using better-docs formatting:`;
-export const TypesPrompt = `document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.
-  Include @interface and @typeDef an @template tags when appropriate.
-  Include detailed @description for all properties.
-  For methods, include @description and @summary tags as defined for the target. also document every argument, including its type definition, and return type, referencing @template tags when necessary.
-
-  The order of tags  (when applicable) should be as follows:
-1 - @description;
-2 - @summary;
-3 - @template;
-4 - @param;
-5 - @return;
-6 - @interface or @typeDef followed by the interface or type name;
-8 - @memberOf referencing the appropriate module using the appropriate syntax
-
-Output only the completed JSDoc comment block for the type or interface.
-refer to the module it belongs with @memberOf this the \`@memberOf module:<module_name>\` syntax
-never omit or change any code
-if the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information`;
-export const ConstantsPrompt = `document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.
-Include @const and @typeDef tags when appropriate.
-Include detailed @description for all properties.
-- For enums, include @enum and @readonly, and add inline documentation for each member
-- For object-like constants:
-    - Create a @typedef with @property for each key
-    - Reference it in the constant using @type
-    - Alternatively, document each key inline if small
-
-The order of tags  (when applicable) should be as follows:
-1 - @description;
-2 - @summary;
-3 - @template;
-4 - @property;
-6 - @const followed by the const or enum name;
-8 - @memberOf referencing the appropriate module using the appropriate syntax
-
-Respond with the JSDoc comment block(s) for both the typedef and the constant or enum.
-refer to the module it belongs with @memberOf this the \`@memberOf module:<module_name>\` syntax
-never omit or change any code
-if the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information`;
-export const Footer = `NOTES:
- - when document a function/method parameters, and there is a template type involved, ALWAYS reference it using the @template tag;
- - when documenting a function type as a parameter, ALWAYS use the function(type1,type2):return_type syntax;
- `;
-//# sourceMappingURL=constants.js.map

package/lib/esm/prompts/jsdocs/constants.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"constants.js","sourceRoot":"","sources":["../../../../src/prompts/jsdocs/constants.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,eAAe,GAAG;0FAC2D,CAAC;AAE3F,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;;;;;;;gIAiBqG,CAAC;AAEjI,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;gIAoBiG,CAAC;AAEjI,MAAM,CAAC,MAAM,MAAM,GAAG;;;EAGpB,CAAC"}

package/lib/esm/prompts/jsdocs/decorator-prompt.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const TsDocDecoratorPrompt: PromptBuilder;

package/lib/esm/prompts/jsdocs/decorator-prompt.js

@@ -1,42 +0,0 @@
-import { z } from "zod";
-import { BaseJSDocPrompt, Footer } from "./constants.js";
-import { PromptBuilder } from "./../../builders/prompt-builder.js";
-const promptName = "ts.jsdoc.decorator";
-const argsSchema = z.object({});
-export const TsDocDecoratorPrompt = PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Decorator JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript Decorator according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${BaseJSDocPrompt}
-document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.
-Include @function an @template tags when appropriate.
-Include detailed @description for all properties.
-For methods, include @description and @summary tags as defined for the target. also document every argument, including its type definition, and return type, referencing @template tags when necessary.
-create mermaid sequence diagrams under the @mermaid tag;
-
-The order of tags (when applicable) should be as follows:
-1 - @description;
-2 - @summary;
-3 - @template;
-4 - @param including type definitions;
-5 - @return;
-6 - @function followed by the interface or type name;
-7 - @mermaid with the sequence diagram for the function if it has over 10 lines
-8 - @category one of: "Decorators", "Class Decorators", "Method Decorators", "Property Decorators", "Parameter Decorators"
-Output only the full JSDoc comment block for the function.
-DO NOT refer to the module it belongs with @memberOf
-never omit or change any code
-if the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information
-${Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-    };
-    return result;
-});
-//# sourceMappingURL=decorator-prompt.js.map

package/lib/esm/prompts/jsdocs/decorator-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"decorator-prompt.js","sourceRoot":"","sources":["../../../../src/prompts/jsdocs/decorator-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,eAAe,EAAE,MAAM,EAAE,uBAAoB;AAOtD,OAAO,EAAE,aAAa,EAAE,2CAAsC;AAE9D,MAAM,UAAU,GAAG,oBAAoB,CAAC;AAExC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGhC,MAAM,CAAC,MAAM,oBAAoB,GAAkB,aAAa,CAAC,OAAO;KACrE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,yBAAyB,CAAC;KACnC,cAAc,CACb,gGAAgG,CACjG;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,eAAe;;;;;;;;;;;;;;;;;;;;EAoBrC,MAAM,EAAE,CAAC;IAEL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;KACtE,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/esm/prompts/jsdocs/enum-prompt.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const TsDocEnumPrompt: PromptBuilder;

package/lib/esm/prompts/jsdocs/enum-prompt.js

@@ -1,24 +0,0 @@
-import { z } from "zod";
-import { BaseJSDocPrompt, ConstantsPrompt, Footer } from "./constants.js";
-import { PromptBuilder } from "./../../builders/prompt-builder.js";
-const promptName = "ts.jsdoc.enum";
-const argsSchema = z.object({});
-export const TsDocEnumPrompt = PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Enum JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript enum according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${BaseJSDocPrompt}
-${ConstantsPrompt}
-${Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-    };
-    return result;
-});
-//# sourceMappingURL=enum-prompt.js.map

package/lib/esm/prompts/jsdocs/enum-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"enum-prompt.js","sourceRoot":"","sources":["../../../../src/prompts/jsdocs/enum-prompt.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,eAAe,EAAE,eAAe,EAAE,MAAM,EAAE,uBAAoB;AAOvE,OAAO,EAAE,aAAa,EAAE,2CAAsC;AAE9D,MAAM,UAAU,GAAG,eAAe,CAAC;AAEnC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGhC,MAAM,CAAC,MAAM,eAAe,GAAkB,aAAa,CAAC,OAAO;KAChE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,oBAAoB,CAAC;KAC9B,cAAc,CACb,2FAA2F,CAC5F;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,eAAe;EACrC,eAAe;EACf,MAAM,EAAE,CAAC;IAEL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;KACtE,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/esm/prompts/jsdocs/function-prompt.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const TsDocFunctionPrompt: PromptBuilder;

package/lib/esm/prompts/jsdocs/function-prompt.js

@@ -1,43 +0,0 @@
-import { z } from "zod";
-import { BaseJSDocPrompt, Footer } from "./constants.js";
-import { PromptBuilder } from "./../../builders/prompt-builder.js";
-const promptName = "ts.jsdoc.function";
-const argsSchema = z.object({});
-export const TsDocFunctionPrompt = PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Function JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript function according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${BaseJSDocPrompt}
-document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.
-Include @function an @template tags when appropriate.
-Include detailed @description for all properties.
-For methods, include @description and @summary tags as defined for the target. also document every argument, including its type definition, and return type, referencing @template tags when necessary.
-create mermaid sequence diagrams under the @mermaid tag;
-
-The order of tags (when applicable) should be as follows:
-1 - @description;
-2 - @summary;
-3 - @template;
-4 - @param including type definitions;
-5 - @return;
-6 - @function followed by the interface or type name;
-7 - @mermaid with the sequence diagram for the function if ithas over 10 lines
-8 - @memberOf referencing the appropriate module using the appropriate syntax
-
-Output only the full JSDoc comment block for the function.
-refer to the module it belongs with @memberOf this the \`@memberOf module:<module_name>\` syntax
-never omit or change any code
-if the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information
-${Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-    };
-    return result;
-});
-//# sourceMappingURL=function-prompt.js.map

package/lib/esm/prompts/jsdocs/function-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"function-prompt.js","sourceRoot":"","sources":["../../../../src/prompts/jsdocs/function-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,eAAe,EAAE,MAAM,EAAE,uBAAoB;AAOtD,OAAO,EAAE,aAAa,EAAE,2CAAsC;AAE9D,MAAM,UAAU,GAAG,mBAAmB,CAAC;AAEvC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGhC,MAAM,CAAC,MAAM,mBAAmB,GAAkB,aAAa,CAAC,OAAO;KACpE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,wBAAwB,CAAC;KAClC,cAAc,CACb,+FAA+F,CAChG;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,eAAe;;;;;;;;;;;;;;;;;;;;;EAqBrC,MAAM,EAAE,CAAC;IAEL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;KACtE,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/esm/prompts/jsdocs/interface-prompt.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const TsDocInterfacePrompt: PromptBuilder;

package/lib/esm/prompts/jsdocs/interface-prompt.js

@@ -1,24 +0,0 @@
-import { z } from "zod";
-import { BaseJSDocPrompt, Footer, TypesPrompt } from "./constants.js";
-import { PromptBuilder } from "./../../builders/prompt-builder.js";
-const promptName = "ts.jsdoc.interface";
-const argsSchema = z.object({});
-export const TsDocInterfacePrompt = PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Interface JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript interface according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${BaseJSDocPrompt}
-${TypesPrompt}
-${Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-    };
-    return result;
-});
-//# sourceMappingURL=interface-prompt.js.map

package/lib/esm/prompts/jsdocs/interface-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"interface-prompt.js","sourceRoot":"","sources":["../../../../src/prompts/jsdocs/interface-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,eAAe,EAAE,MAAM,EAAE,WAAW,EAAE,uBAAoB;AAOnE,OAAO,EAAE,aAAa,EAAE,2CAAsC;AAE9D,MAAM,UAAU,GAAG,oBAAoB,CAAC;AAExC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGhC,MAAM,CAAC,MAAM,oBAAoB,GAAkB,aAAa,CAAC,OAAO;KACrE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,yBAAyB,CAAC;KACnC,cAAc,CACb,gGAAgG,CACjG;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,eAAe;EACrC,WAAW;EACX,MAAM,EAAE,CAAC;IAEL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;KACtE,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/esm/prompts/jsdocs/types-prompt.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const TsDocTypeePrompt: PromptBuilder;

package/lib/esm/prompts/jsdocs/types-prompt.js

@@ -1,24 +0,0 @@
-import { z } from "zod";
-import { BaseJSDocPrompt, Footer, TypesPrompt } from "./constants.js";
-import { PromptBuilder } from "./../../builders/prompt-builder.js";
-const promptName = "ts.jsdoc.type";
-const argsSchema = z.object({});
-export const TsDocTypeePrompt = PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Type JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript type according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${BaseJSDocPrompt}
-${TypesPrompt}
-${Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-    };
-    return result;
-});
-//# sourceMappingURL=types-prompt.js.map

package/lib/esm/prompts/jsdocs/types-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"types-prompt.js","sourceRoot":"","sources":["../../../../src/prompts/jsdocs/types-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,eAAe,EAAE,MAAM,EAAE,WAAW,EAAE,uBAAoB;AAOnE,OAAO,EAAE,aAAa,EAAE,2CAAsC;AAE9D,MAAM,UAAU,GAAG,eAAe,CAAC;AAEnC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGhC,MAAM,CAAC,MAAM,gBAAgB,GAAkB,aAAa,CAAC,OAAO;KACjE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,oBAAoB,CAAC;KAC9B,cAAc,CACb,2FAA2F,CAC5F;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,eAAe;EACrC,WAAW;EACX,MAAM,EAAE,CAAC;IAEL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;KACtE,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/esm/tools/example-tool/index.d.ts

@@ -1,2 +0,0 @@
-import { ToolBuilder } from "../../builders/tool-builder";
-export declare const ExampleTool: ToolBuilder;

package/lib/esm/tools/example-tool/index.js

@@ -1,29 +0,0 @@
-import { ToolBuilder } from "./../../builders/tool-builder.js";
-import { z } from "zod";
-import { ReasoningLevel, EffortLevel, Cost } from "./../../constants.js";
-// A tiny example tool that reverses an input string. Useful as a smoke/example tool.
-export const ExampleTool = ToolBuilder.builder
-    .setName("example-tool")
-    .setTitle("Example: Reverse String Tool")
-    .setDescription("Reverses the provided `text` input and returns the result.")
-    .setInputSchema(z.object({ text: z.string() }))
-    .setCb(async (args, _extra) => {
-    const text = args?.text ?? "";
-    const reversed = String(text).split("").reverse().join("");
-    return {
-        // Human-readable content for models and UIs
-        content: [
-            {
-                type: "text",
-                text: reversed,
-            },
-        ],
-        // Structured content matching the declared outputSchema: { result: string }
-        structuredContent: { result: reversed },
-    };
-})
-    .setReasoning(ReasoningLevel.NONE)
-    .setEffort(EffortLevel.NONE)
-    .setCost(Cost.FREE);
-// Named export already provided above; avoid default exports per repository policy.
-//# sourceMappingURL=index.js.map

package/lib/esm/tools/example-tool/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../src/tools/example-tool/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,WAAW,EAAE,yCAAoC;AAC1D,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,cAAc,EAAE,WAAW,EAAE,IAAI,EAAE,6BAAwB;AAOpE,qFAAqF;AACrF,MAAM,CAAC,MAAM,WAAW,GAAG,WAAW,CAAC,OAAO;KAC3C,OAAO,CAAC,cAAc,CAAC;KACvB,QAAQ,CAAC,8BAA8B,CAAC;KACxC,cAAc,CAAC,4DAA4D,CAAC;KAC5E,cAAc,CAAC,CAAC,CAAC,MAAM,CAAC,EAAE,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC;KAC9C,KAAK,CAAC,KAAK,EAAE,IAAS,EAAE,MAA8D,EAAE,EAAE;IACzF,MAAM,IAAI,GAAG,IAAI,EAAE,IAAI,IAAI,EAAE,CAAC;IAC9B,MAAM,QAAQ,GAAG,MAAM,CAAC,IAAI,CAAC,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAC3D,OAAO;QACL,4CAA4C;QAC5C,OAAO,EAAE;YACP;gBACE,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE,QAAQ;aACf;SACF;QACD,4EAA4E;QAC5E,iBAAiB,EAAE,EAAE,MAAM,EAAE,QAAQ,EAAE;KACjC,CAAC;AACX,CAAC,CAAC;KACD,YAAY,CAAC,cAAc,CAAC,IAAI,CAAC;KACjC,SAAS,CAAC,WAAW,CAAC,IAAI,CAAC;KAC3B,OAAO,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEtB,oFAAoF"}

package/lib/prompts/example-prompt/index.cjs

@@ -1,21 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.ExamplePrompt = void 0;
-const zod_1 = require("zod");
-const prompt_builder_1 = require("./../../builders/prompt-builder.cjs");
-const constants_1 = require("./../../constants.cjs");
-const promptName = "example.prompt.echo";
-const argsSchema = zod_1.z.object({ text: zod_1.z.string().optional() });
-exports.ExamplePrompt = prompt_builder_1.PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Example: Echo Prompt")
-    .setDescription("Returns a short prompt containing the provided `text` as a user message.")
-    .setArgsSchema(argsSchema)
-    .setReasoning(constants_1.ReasoningLevel.BASIC)
-    .setCb((args, _extra) => {
-    const text = args?.text ?? "(no text provided)";
-    const messages = [{ role: "user", content: { type: "text", text } }];
-    return { messages, _meta: {} };
-});
-// Named export already provided above; avoid default exports per repository policy.
-//# sourceMappingURL=index.js.map

package/lib/prompts/example-prompt/index.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const ExamplePrompt: PromptBuilder;

package/lib/prompts/example-prompt/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/prompts/example-prompt/index.ts"],"names":[],"mappings":";;;AAAA,6BAAwB;AACxB,wEAA8D;AAO9D,qDAAoE;AAEpE,MAAM,UAAU,GAAG,qBAAqB,CAAC;AAEzC,MAAM,UAAU,GAAG,OAAC,CAAC,MAAM,CAAC,EAAE,IAAI,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC;AAGhD,QAAA,aAAa,GAAG,8BAAa,CAAC,OAAO;KAC/C,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,sBAAsB,CAAC;KAChC,cAAc,CAAC,0EAA0E,CAAC;KAC1F,aAAa,CAAC,UAAiB,CAAC;KAChC,YAAY,CAAC,0BAAc,CAAC,KAAK,CAAC;KAClC,KAAK,CACJ,CACE,IAAU,EACV,MAA8D,EAC7C,EAAE;IACnB,MAAM,IAAI,GAAG,IAAI,EAAE,IAAI,IAAI,oBAAoB,CAAC;IAChD,MAAM,QAAQ,GAAG,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE,CAAC,CAAC;IACrE,OAAO,EAAE,QAAQ,EAAE,KAAK,EAAE,EAAE,EAAS,CAAC;AACxC,CAAC,CACF,CAAC;AAEJ,oFAAoF"}

package/lib/prompts/interactive-jsdoc/index.cjs

@@ -1,21 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.InteractiveJsDocPrompt = void 0;
-const zod_1 = require("zod");
-const prompt_builder_1 = require("./../../builders/prompt-builder.cjs");
-const constants_1 = require("./../../constants.cjs");
-const promptName = "interactive.jsdoc.assistant";
-const argsSchema = zod_1.z.object({ code: zod_1.z.string().optional(), astObject: zod_1.z.any().optional() });
-exports.InteractiveJsDocPrompt = prompt_builder_1.PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Interactive JSDoc Assistant")
-    .setDescription("Produce a ready-to-insert JSDoc block for a provided code snippet or AST object.")
-    .setArgsSchema(argsSchema)
-    .setReasoning(constants_1.ReasoningLevel.BASIC)
-    .setCb((args, _extra) => {
-    const code = args?.code ?? "";
-    const prompt = `Generate a complete JSDoc comment block for the following code. Respond only with the full JSDoc block.\n\n${code}`;
-    const result = { messages: [{ role: "user", content: { type: "text", text: prompt } }], _meta: {} };
-    return result;
-});
-//# sourceMappingURL=index.js.map

package/lib/prompts/interactive-jsdoc/index.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const InteractiveJsDocPrompt: PromptBuilder;

package/lib/prompts/interactive-jsdoc/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/prompts/interactive-jsdoc/index.ts"],"names":[],"mappings":";;;AAAA,6BAAwB;AACxB,wEAA8D;AAO9D,qDAAiD;AAEjD,MAAM,UAAU,GAAG,6BAA6B,CAAC;AAEjD,MAAM,UAAU,GAAG,OAAC,CAAC,MAAM,CAAC,EAAE,IAAI,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,EAAE,SAAS,EAAE,OAAC,CAAC,GAAG,EAAE,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC;AAG/E,QAAA,sBAAsB,GAAG,8BAAa,CAAC,OAAO;KACxD,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,6BAA6B,CAAC;KACvC,cAAc,CAAC,kFAAkF,CAAC;KAClG,aAAa,CAAC,UAAiB,CAAC;KAChC,YAAY,CAAC,0BAAc,CAAC,KAAK,CAAC;KAClC,KAAK,CAAC,CAAC,IAAU,EAAE,MAA8D,EAAmB,EAAE;IACrG,MAAM,IAAI,GAAG,IAAI,EAAE,IAAI,IAAI,EAAE,CAAC;IAC9B,MAAM,MAAM,GAAG,8GAA8G,IAAI,EAAE,CAAC;IACpI,MAAM,MAAM,GAAoB,EAAE,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC,EAAE,KAAK,EAAE,EAAE,EAAS,CAAC;IAC5H,OAAO,MAAM,CAAC;AAChB,CAAC,CAAC,CAAC"}

package/lib/prompts/jsdocs/class-prompt.cjs

@@ -1,55 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.TsDocClassPrompt = void 0;
-const zod_1 = require("zod");
-const constants_1 = require("./constants.cjs");
-const prompt_builder_1 = require("./../../builders/prompt-builder.cjs");
-const constants_2 = require("./../../constants.cjs");
-const promptName = "ts.jsdoc.class";
-const argsSchema = zod_1.z.object({});
-exports.TsDocClassPrompt = prompt_builder_1.PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Class JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript class according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setReasoning(constants_2.ReasoningLevel.BASIC)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${constants_1.BaseJSDocPrompt}
-document the entire class and each of its functions including always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.
-Include @class tags when applicable.
-include @param tags in the class documentation and its type definitions
-Include detailed @description for all properties.
-Include @template tags when necessary.
-Do NOT document the constructor, but include the constructor arguments as @param in the class documentation
-For methods and functions:
-- include @description and @summary tags as defined for the target. also document every argument, including its type definition, and return type, referencing @template tags when necessary.
-- create a usage example under the @example tag on the class documentation
-- create mermaid sequence diagrams under the @mermaid tag;
-
-The order of tags (when applicable) should be as follows:
-1 - @description;
-2 - @summary;
-3 - @template;
-4 - @param;
-5 - @return;
-6 - @class
-7 - @example
-8 - @mermaid;
-
-ignore @mermaid for methods with less that 15 lines and constructors.
-Respond only with the full JSDoc comment block for the class and its methods.
-NEVER user @memberOf in the class or any of it's methods
-if the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information
-never omit or change any code, including the constructor
-${constants_1.Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-        _meta: {},
-    };
-    return result;
-});
-//# sourceMappingURL=class-prompt.js.map

package/lib/prompts/jsdocs/class-prompt.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const TsDocClassPrompt: PromptBuilder;

package/lib/prompts/jsdocs/class-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"class-prompt.js","sourceRoot":"","sources":["../../../src/prompts/jsdocs/class-prompt.ts"],"names":[],"mappings":";;;AAAA,6BAAwB;AACxB,+CAAsD;AAOtD,wEAA8D;AAC9D,qDAAiD;AAEjD,MAAM,UAAU,GAAG,gBAAgB,CAAC;AAEpC,MAAM,UAAU,GAAG,OAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGnB,QAAA,gBAAgB,GAAkB,8BAAa,CAAC,OAAO;KACjE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,qBAAqB,CAAC;KAC/B,cAAc,CACb,4FAA4F,CAC7F;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,YAAY,CAAC,0BAAc,CAAC,KAAK,CAAC;KAClC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,2BAAe;;;;;;;;;;;;;;;;;;;;;;;;;;;EA2BrC,kBAAM,EAAE,CAAC;IACL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;QACrE,KAAK,EAAE,EAAE;KACV,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/prompts/jsdocs/const-prompt.cjs

@@ -1,27 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.TsDocConstPrompt = void 0;
-const zod_1 = require("zod");
-const constants_1 = require("./constants.cjs");
-const prompt_builder_1 = require("./../../builders/prompt-builder.cjs");
-const promptName = "ts.jsdoc.const";
-const argsSchema = zod_1.z.object({});
-exports.TsDocConstPrompt = prompt_builder_1.PromptBuilder.builder
-    .setName(promptName)
-    .setTitle("Const JSDocs Prompt")
-    .setDescription("Generate JSDoc comments for a TypeScript constant according to a curated template and prompt.")
-    .setArgsSchema(argsSchema)
-    .setCb((
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-args, 
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-extra) => {
-    const prompt = `${constants_1.BaseJSDocPrompt}
-${constants_1.ConstantsPrompt}
-${constants_1.Footer}`;
-    const result = {
-        messages: [{ role: "user", content: { type: "text", text: prompt } }],
-    };
-    return result;
-});
-//# sourceMappingURL=const-prompt.js.map

package/lib/prompts/jsdocs/const-prompt.d.ts

@@ -1,2 +0,0 @@
-import { PromptBuilder } from "../../builders/prompt-builder";
-export declare const TsDocConstPrompt: PromptBuilder;

package/lib/prompts/jsdocs/const-prompt.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"const-prompt.js","sourceRoot":"","sources":["../../../src/prompts/jsdocs/const-prompt.ts"],"names":[],"mappings":";;;AAAA,6BAAwB;AACxB,+CAAuE;AAOvE,wEAA8D;AAE9D,MAAM,UAAU,GAAG,gBAAgB,CAAC;AAEpC,MAAM,UAAU,GAAG,OAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;AAGnB,QAAA,gBAAgB,GAAkB,8BAAa,CAAC,OAAO;KACjE,OAAO,CAAC,UAAU,CAAC;KACnB,QAAQ,CAAC,qBAAqB,CAAC;KAC/B,cAAc,CACb,+FAA+F,CAChG;KACA,aAAa,CAAC,UAAiB,CAAC;KAChC,KAAK,CACJ;AACE,6DAA6D;AAC7D,IAAU;AACV,6DAA6D;AAC7D,KAA6D,EAC7D,EAAE;IACF,MAAM,MAAM,GAAG,GAAG,2BAAe;EACrC,2BAAe;EACf,kBAAM,EAAE,CAAC;IAEL,MAAM,MAAM,GAAoB;QAC9B,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,CAAC;KACtE,CAAC;IAEF,OAAO,MAAM,CAAC;AAChB,CAAC,CACF,CAAC"}

package/lib/prompts/jsdocs/constants.cjs

@@ -1,49 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Footer = exports.ConstantsPrompt = exports.TypesPrompt = exports.BaseJSDocPrompt = void 0;
-exports.BaseJSDocPrompt = `You're a senior TypeScript developer writing JSDoc documentation for a class to be used with better-docs. Given the module code:
-Generate a JSDoc comment block for a TypeScript module file using better-docs formatting:`;
-exports.TypesPrompt = `document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.
-  Include @interface and @typeDef an @template tags when appropriate.
-  Include detailed @description for all properties.
-  For methods, include @description and @summary tags as defined for the target. also document every argument, including its type definition, and return type, referencing @template tags when necessary.
-
-  The order of tags  (when applicable) should be as follows:
-1 - @description;
-2 - @summary;
-3 - @template;
-4 - @param;
-5 - @return;
-6 - @interface or @typeDef followed by the interface or type name;
-8 - @memberOf referencing the appropriate module using the appropriate syntax
-
-Output only the completed JSDoc comment block for the type or interface.
-refer to the module it belongs with @memberOf this the \`@memberOf module:<module_name>\` syntax
-never omit or change any code
-if the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information`;
-exports.ConstantsPrompt = `document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.
-Include @const and @typeDef tags when appropriate.
-Include detailed @description for all properties.
-- For enums, include @enum and @readonly, and add inline documentation for each member
-- For object-like constants:
-    - Create a @typedef with @property for each key
-    - Reference it in the constant using @type
-    - Alternatively, document each key inline if small
-
-The order of tags  (when applicable) should be as follows:
-1 - @description;
-2 - @summary;
-3 - @template;
-4 - @property;
-6 - @const followed by the const or enum name;
-8 - @memberOf referencing the appropriate module using the appropriate syntax
-
-Respond with the JSDoc comment block(s) for both the typedef and the constant or enum.
-refer to the module it belongs with @memberOf this the \`@memberOf module:<module_name>\` syntax
-never omit or change any code
-if the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information`;
-exports.Footer = `NOTES:
- - when document a function/method parameters, and there is a template type involved, ALWAYS reference it using the @template tag;
- - when documenting a function type as a parameter, ALWAYS use the function(type1,type2):return_type syntax;
- `;
-//# sourceMappingURL=constants.js.map

package/lib/prompts/jsdocs/constants.d.ts

@@ -1,4 +0,0 @@
-export declare const BaseJSDocPrompt = "You're a senior TypeScript developer writing JSDoc documentation for a class to be used with better-docs. Given the module code:\nGenerate a JSDoc comment block for a TypeScript module file using better-docs formatting:";
-export declare const TypesPrompt = "document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.\n  Include @interface and @typeDef an @template tags when appropriate.\n  Include detailed @description for all properties.\n  For methods, include @description and @summary tags as defined for the target. also document every argument, including its type definition, and return type, referencing @template tags when necessary.\n\n  The order of tags  (when applicable) should be as follows:\n1 - @description;\n2 - @summary;\n3 - @template;\n4 - @param;\n5 - @return;\n6 - @interface or @typeDef followed by the interface or type name;\n8 - @memberOf referencing the appropriate module using the appropriate syntax\n\nOutput only the completed JSDoc comment block for the type or interface.\nrefer to the module it belongs with @memberOf this the `@memberOf module:<module_name>` syntax\nnever omit or change any code\nif the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information";
-export declare const ConstantsPrompt = "document the target code, always including the @description tag with a short description of the target, and a@summary tag with a more detailed one.\nInclude @const and @typeDef tags when appropriate.\nInclude detailed @description for all properties.\n- For enums, include @enum and @readonly, and add inline documentation for each member\n- For object-like constants:\n    - Create a @typedef with @property for each key\n    - Reference it in the constant using @type\n    - Alternatively, document each key inline if small\n\nThe order of tags  (when applicable) should be as follows:\n1 - @description;\n2 - @summary;\n3 - @template;\n4 - @property;\n6 - @const followed by the const or enum name;\n8 - @memberOf referencing the appropriate module using the appropriate syntax\n\nRespond with the JSDoc comment block(s) for both the typedef and the constant or enum.\nrefer to the module it belongs with @memberOf this the `@memberOf module:<module_name>` syntax\nnever omit or change any code\nif the element is already documented, only restructure, correct, or add to the documentation. NEVER remove existing information";
-export declare const Footer = "NOTES:\n - when document a function/method parameters, and there is a template type involved, ALWAYS reference it using the @template tag;\n - when documenting a function type as a parameter, ALWAYS use the function(type1,type2):return_type syntax;\n ";