@dedesfr/prompter 0.6.0 → 0.6.1

package/dist/core/prompt-templates.js.map

@@ -1 +1 @@
-{"version":3,"file":"prompt-templates.js","sourceRoot":"","sources":["../../src/core/prompt-templates.ts"],"names":[],"mappings":"AAAA,yFAAyF;AAEzF,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6CpC,CAAC;AAEF,MAAM,CAAC,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+CnC,CAAC;AAEF,MAAM,CAAC,MAAM,4BAA4B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoJ3C,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmMrC,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiSrC,CAAC;AAEF,MAAM,CAAC,MAAM,yBAAyB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqIxC,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8VrC,CAAC;AAEF,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsEpC,CAAC;AAEF,4CAA4C;AAC5C,MAAM,CAAC,MAAM,gBAAgB,GAA2B;IACpD,cAAc,EAAE,qBAAqB;IACrC,aAAa,EAAE,oBAAoB;IACnC,qBAAqB,EAAE,4BAA4B;IACnD,eAAe,EAAE,sBAAsB;IACvC,eAAe,EAAE,sBAAsB;IACvC,kBAAkB,EAAE,yBAAyB;IAC7C,eAAe,EAAE,sBAAsB;IACvC,cAAc,EAAE,qBAAqB;CACxC,CAAC"}
+{"version":3,"file":"prompt-templates.js","sourceRoot":"","sources":["../../src/core/prompt-templates.ts"],"names":[],"mappings":"AAAA,yFAAyF;AAEzF,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6CpC,CAAC;AAEF,MAAM,CAAC,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+CnC,CAAC;AAEF,MAAM,CAAC,MAAM,4BAA4B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoJ3C,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmMrC,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiSrC,CAAC;AAEF,MAAM,CAAC,MAAM,yBAAyB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqIxC,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8VrC,CAAC;AAEF,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsEpC,CAAC;AAEF,MAAM,CAAC,MAAM,+BAA+B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6O9C,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoIrC,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6JrC,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsSrC,CAAC;AAEF,MAAM,CAAC,MAAM,2BAA2B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgO1C,CAAC;AAEF,MAAM,CAAC,MAAM,4BAA4B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6N3C,CAAC;AAEF,4CAA4C;AAC5C,MAAM,CAAC,MAAM,gBAAgB,GAA2B;IACpD,cAAc,EAAE,qBAAqB;IACrC,wBAAwB,EAAE,+BAA+B;IACzD,aAAa,EAAE,oBAAoB;IACnC,eAAe,EAAE,sBAAsB;IACvC,eAAe,EAAE,sBAAsB;IACvC,qBAAqB,EAAE,4BAA4B;IACnD,eAAe,EAAE,sBAAsB;IACvC,eAAe,EAAE,sBAAsB;IACvC,kBAAkB,EAAE,yBAAyB;IAC7C,eAAe,EAAE,sBAAsB;IACvC,cAAc,EAAE,qBAAqB;IACrC,eAAe,EAAE,sBAAsB;IACvC,oBAAoB,EAAE,2BAA2B;IACjD,qBAAqB,EAAE,4BAA4B;CACtD,CAAC"}

package/dist/core/templates/slash-command-templates.d.ts

@@ -1,4 +1,4 @@
-export type SlashCommandId = 'enhance' | 'prd-generator' | 'prd-agent-generator' | 'product-brief' | 'epic-single' | 'story-single' | 'qa-test-scenario' | 'skill-creator' | 'ai-humanizer';
+export type SlashCommandId = 'enhance' | 'prd-generator' | 'prd-agent-generator' | 'product-brief' | 'epic-single' | 'story-single' | 'qa-test-scenario' | 'skill-creator' | 'ai-humanizer' | 'api-contract-generator' | 'erd-generator' | 'fsd-generator' | 'tdd-generator' | 'tdd-lite-generator' | 'wireframe-generator';
 export declare const slashCommandBodies: Record<SlashCommandId, string>;
 export declare function getSlashCommandBody(id: SlashCommandId): string;
 export declare class TemplateManager {

package/dist/core/templates/slash-command-templates.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"slash-command-templates.d.ts","sourceRoot":"","sources":["../../../src/core/templates/slash-command-templates.ts"],"names":[],"mappings":"AAAA,MAAM,MAAM,cAAc,GAAG,SAAS,GAAG,eAAe,GAAG,qBAAqB,GAAG,eAAe,GAAG,aAAa,GAAG,cAAc,GAAG,kBAAkB,GAAG,eAAe,GAAG,cAAc,CAAC;AA0/B5L,eAAO,MAAM,kBAAkB,EAAE,MAAM,CAAC,cAAc,EAAE,MAAM,CAU7D,CAAC;AAEF,wBAAgB,mBAAmB,CAAC,EAAE,EAAE,cAAc,GAAG,MAAM,CAE9D;AAED,qBAAa,eAAe;IACxB,MAAM,CAAC,mBAAmB,CAAC,EAAE,EAAE,cAAc,GAAG,MAAM;CAGzD"}
+{"version":3,"file":"slash-command-templates.d.ts","sourceRoot":"","sources":["../../../src/core/templates/slash-command-templates.ts"],"names":[],"mappings":"AASA,MAAM,MAAM,cAAc,GAAG,SAAS,GAAG,eAAe,GAAG,qBAAqB,GAAG,eAAe,GAAG,aAAa,GAAG,cAAc,GAAG,kBAAkB,GAAG,eAAe,GAAG,cAAc,GAAG,wBAAwB,GAAG,eAAe,GAAG,eAAe,GAAG,eAAe,GAAG,oBAAoB,GAAG,qBAAqB,CAAC;AA0/B5T,eAAO,MAAM,kBAAkB,EAAE,MAAM,CAAC,cAAc,EAAE,MAAM,CAgB7D,CAAC;AAEF,wBAAgB,mBAAmB,CAAC,EAAE,EAAE,cAAc,GAAG,MAAM,CAE9D;AAED,qBAAa,eAAe;IACxB,MAAM,CAAC,mBAAmB,CAAC,EAAE,EAAE,cAAc,GAAG,MAAM;CAGzD"}

package/dist/core/templates/slash-command-templates.js

@@ -1,3 +1,4 @@
+import { API_CONTRACT_GENERATOR_TEMPLATE, ERD_GENERATOR_TEMPLATE, FSD_GENERATOR_TEMPLATE, TDD_GENERATOR_TEMPLATE, TDD_LITE_GENERATOR_TEMPLATE, WIREFRAME_GENERATOR_TEMPLATE } from '../prompt-templates.js';
 const enhanceWorkflow = `## MUST FOLLOW
 - Response Language: {User Request Language}
 
@@ -1014,7 +1015,13 @@ export const slashCommandBodies = {
     'story-single': storySingleWorkflow,
     'qa-test-scenario': qaTestScenarioWorkflow,
     'skill-creator': skillCreatorWorkflow,
-    'ai-humanizer': aiHumanizerWorkflow
+    'ai-humanizer': aiHumanizerWorkflow,
+    'api-contract-generator': API_CONTRACT_GENERATOR_TEMPLATE,
+    'erd-generator': ERD_GENERATOR_TEMPLATE,
+    'fsd-generator': FSD_GENERATOR_TEMPLATE,
+    'tdd-generator': TDD_GENERATOR_TEMPLATE,
+    'tdd-lite-generator': TDD_LITE_GENERATOR_TEMPLATE,
+    'wireframe-generator': WIREFRAME_GENERATOR_TEMPLATE
 };
 export function getSlashCommandBody(id) {
     return slashCommandBodies[id];

package/dist/core/templates/slash-command-templates.js.map

@@ -1 +1 @@
-{"version":3,"file":"slash-command-templates.js","sourceRoot":"","sources":["../../../src/core/templates/slash-command-templates.ts"],"names":[],"mappings":"AAEA,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mEAyC2C,CAAC;AAEpE,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA6MgC,CAAC;AAE9D,MAAM,yBAAyB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA8H2B,CAAC;AAE9D,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAyDkC,CAAC;AAE9D,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAgFiC,CAAC;AAE9D,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA+I8B,CAAC;AAE9D,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAuKgC,CAAC;AAE9D,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iEAuIoC,CAAC;AAElE,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mEA4CuC,CAAC;AAEpE,MAAM,CAAC,MAAM,kBAAkB,GAAmC;IAC9D,OAAO,EAAE,eAAe;IACxB,eAAe,EAAE,oBAAoB;IACrC,qBAAqB,EAAE,yBAAyB;IAChD,eAAe,EAAE,oBAAoB;IACrC,aAAa,EAAE,kBAAkB;IACjC,cAAc,EAAE,mBAAmB;IACnC,kBAAkB,EAAE,sBAAsB;IAC1C,eAAe,EAAE,oBAAoB;IACrC,cAAc,EAAE,mBAAmB;CACtC,CAAC;AAEF,MAAM,UAAU,mBAAmB,CAAC,EAAkB;IAClD,OAAO,kBAAkB,CAAC,EAAE,CAAC,CAAC;AAClC,CAAC;AAED,MAAM,OAAO,eAAe;IACxB,MAAM,CAAC,mBAAmB,CAAC,EAAkB;QACzC,OAAO,mBAAmB,CAAC,EAAE,CAAC,CAAC;IACnC,CAAC;CACJ"}
+{"version":3,"file":"slash-command-templates.js","sourceRoot":"","sources":["../../../src/core/templates/slash-command-templates.ts"],"names":[],"mappings":"AAAA,OAAO,EACH,+BAA+B,EAC/B,sBAAsB,EACtB,sBAAsB,EACtB,sBAAsB,EACtB,2BAA2B,EAC3B,4BAA4B,EAC/B,MAAM,wBAAwB,CAAC;AAIhC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mEAyC2C,CAAC;AAEpE,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA6MgC,CAAC;AAE9D,MAAM,yBAAyB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA8H2B,CAAC;AAE9D,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAyDkC,CAAC;AAE9D,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAgFiC,CAAC;AAE9D,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA+I8B,CAAC;AAE9D,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAuKgC,CAAC;AAE9D,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iEAuIoC,CAAC;AAElE,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mEA4CuC,CAAC;AAEpE,MAAM,CAAC,MAAM,kBAAkB,GAAmC;IAC9D,OAAO,EAAE,eAAe;IACxB,eAAe,EAAE,oBAAoB;IACrC,qBAAqB,EAAE,yBAAyB;IAChD,eAAe,EAAE,oBAAoB;IACrC,aAAa,EAAE,kBAAkB;IACjC,cAAc,EAAE,mBAAmB;IACnC,kBAAkB,EAAE,sBAAsB;IAC1C,eAAe,EAAE,oBAAoB;IACrC,cAAc,EAAE,mBAAmB;IACnC,wBAAwB,EAAE,+BAA+B;IACzD,eAAe,EAAE,sBAAsB;IACvC,eAAe,EAAE,sBAAsB;IACvC,eAAe,EAAE,sBAAsB;IACvC,oBAAoB,EAAE,2BAA2B;IACjD,qBAAqB,EAAE,4BAA4B;CACtD,CAAC;AAEF,MAAM,UAAU,mBAAmB,CAAC,EAAkB;IAClD,OAAO,kBAAkB,CAAC,EAAE,CAAC,CAAC;AAClC,CAAC;AAED,MAAM,OAAO,eAAe;IACxB,MAAM,CAAC,mBAAmB,CAAC,EAAkB;QACzC,OAAO,mBAAmB,CAAC,EAAE,CAAC,CAAC;IACnC,CAAC;CACJ"}

package/docs/tasks.md

@@ -0,0 +1,3 @@
+COMMAND_NAME = ['api-contract-generator', 'erd-generator', 'fsd-generator', 'tdd-generator', 'tdd-lite-generator', 'wireframe-generator']
+
+i want to add new command for {COMMAND_NAME}. you can check the prompt in prompt folder here with name match {COMMAND_NAME}.md

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@dedesfr/prompter",
-    "version": "0.6.0",
+    "version": "0.6.1",
     "description": "Enhance prompts directly in your AI coding workflow",
     "type": "module",
     "main": "dist/index.js",

package/prompt/api-contract-generator.md

@@ -0,0 +1,234 @@
+# API Contract Generator Prompt
+
+# Role & Expertise
+You are a Senior API Architect and Technical Documentation Specialist with extensive experience in RESTful API design, OpenAPI/Swagger specifications, and translating business requirements into precise technical contracts. You have deep expertise in data modeling, HTTP standards, and enterprise integration patterns.
+
+# Context
+You will receive a Functional Specification Document (FSD) and an Entity Relationship Diagram (ERD) as inputs. Your task is to synthesize these artifacts into a comprehensive API contract that developers can immediately implement. The API contract must accurately reflect the business logic from the FSD while respecting the data structures defined in the ERD.
+
+# Primary Objective
+Generate a complete, production-ready API contract in OpenAPI 3.0+ specification format that:
+- Covers all functional requirements from the FSD
+- Aligns data models with the ERD entities and relationships
+- Follows REST best practices and industry standards
+- Is immediately usable for development and API documentation tools
+
+# Process
+
+## Phase 1: Analysis
+1. **FSD Extraction**
+   - Identify all user stories/use cases
+   - Extract business rules and validation requirements
+   - Map functional flows to potential API operations
+   - Note authentication/authorization requirements
+   - Identify error scenarios and edge cases
+
+2. **ERD Interpretation**
+   - Catalog all entities and their attributes
+   - Map data types to API schema types
+   - Identify relationships (1:1, 1:N, M:N)
+   - Note required vs optional fields
+   - Identify unique constraints and keys
+
+3. **Cross-Reference Mapping**
+   - Link FSD operations to ERD entities
+   - Identify CRUD requirements per entity
+   - Map business validations to schema constraints
+   - Determine resource hierarchies and nesting
+
+## Phase 2: API Design
+1. **Resource Modeling**
+   - Define REST resources from entities
+   - Establish URL hierarchy and naming
+   - Determine resource representations (full, summary, reference)
+
+2. **Endpoint Definition**
+   - Map operations to HTTP methods
+   - Define path parameters and query parameters
+   - Establish pagination, filtering, sorting patterns
+
+3. **Schema Development**
+   - Create request/response schemas
+   - Define reusable components
+   - Establish enum types from domain values
+
+4. **Security & Error Handling**
+   - Define authentication schemes
+   - Create standard error response formats
+   - Map business errors to HTTP status codes
+
+## Phase 3: Contract Generation
+1. Compile OpenAPI specification
+2. Add comprehensive descriptions
+3. Include request/response examples
+4. Document edge cases and constraints
+
+# Input Specifications
+
+**Functional Specification Document (FSD):**
+- Business requirements and user stories
+- Functional flows and processes
+- Business rules and validations
+- User roles and permissions
+- Expected system behaviors
+
+**Entity Relationship Diagram (ERD):**
+- Entity names and descriptions
+- Attributes with data types
+- Primary and foreign keys
+- Relationship cardinalities
+- Constraints and indexes
+
+# Output Requirements
+
+**Format:** OpenAPI 3.0+ YAML specification
+
+**Required Sections:**
+
+yaml
+openapi: 3.0.x
+info:
+  title: [API Name]
+  description: [Comprehensive API description]
+  version: [Version]
+  
+servers:
+  - url: [Base URL patterns]
+
+tags:
+  - [Logical groupings of endpoints]
+
+paths:
+  [All endpoints with full specifications]
+
+components:
+  schemas:
+    [All data models derived from ERD]
+  parameters:
+    [Reusable parameters]
+  responses:
+    [Standard response definitions]
+  securitySchemes:
+    [Authentication methods]
+  examples:
+    [Request/response examples]
+
+security:
+  [Global security requirements]
+
+**Per Endpoint Requirements:**
+- Summary and detailed description
+- Operation ID (for code generation)
+- Tags for grouping
+- All parameters (path, query, header)
+- Request body with schema reference
+- All possible responses (2xx, 4xx, 5xx)
+- Security requirements
+- At least one example per request/response
+
+**Schema Requirements:**
+- All properties with types and descriptions
+- Required fields array
+- Validation constraints (minLength, maxLength, pattern, minimum, maximum, enum)
+- Nullable indicators
+- Example values
+
+# Quality Standards
+
+1. **Completeness**
+   - Every FSD requirement maps to at least one endpoint
+   - Every ERD entity has corresponding schema(s)
+   - All CRUD operations covered where applicable
+
+2. **Consistency**
+   - Uniform naming conventions (camelCase for properties, kebab-case for URLs)
+   - Consistent response structures across endpoints
+   - Standard pagination/filtering patterns
+
+3. **Accuracy**
+   - Data types match ERD definitions
+   - Validations reflect business rules
+   - Relationships properly represented in nested/linked resources
+
+4. **Usability**
+   - Clear, actionable descriptions
+   - Meaningful examples
+   - Logical endpoint organization
+
+5. **Standards Compliance**
+   - Valid OpenAPI 3.0+ syntax
+   - RESTful conventions followed
+   - HTTP semantics correctly applied
+
+# Special Instructions
+
+**Naming Conventions:**
+- Resources: plural nouns (e.g., `/users`, `/orders`)
+- Endpoints: `kebab-case`
+- Schema names: `PascalCase`
+- Properties: `camelCase`
+- Query parameters: `camelCase`
+
+**Standard Patterns to Apply:**
+
+| Operation | Method | Path Pattern | Success Code |
+|-----------|--------|--------------|--------------|
+| List | GET | /resources | 200 |
+| Get One | GET | /resources/{id} | 200 |
+| Create | POST | /resources | 201 |
+| Full Update | PUT | /resources/{id} | 200 |
+| Partial Update | PATCH | /resources/{id} | 200 |
+| Delete | DELETE | /resources/{id} | 204 |
+
+**Pagination Standard:**
+yaml
+parameters:
+  - name: page
+    in: query
+    schema:
+      type: integer
+      default: 1
+  - name: limit
+    in: query
+    schema:
+      type: integer
+      default: 20
+      maximum: 100
+
+**Error Response Standard:**
+yaml
+ErrorResponse:
+  type: object
+  required:
+    - code
+    - message
+  properties:
+    code:
+      type: string
+    message:
+      type: string
+    details:
+      type: array
+      items:
+        type: object
+        properties:
+          field:
+            type: string
+          issue:
+            type: string
+
+**Relationship Handling:**
+- 1:1 → Embed or link with reference ID
+- 1:N → Nested collection endpoint or link array
+- M:N → Separate join resource or array of references
+
+# Verification Checklist
+
+After generating the contract, verify:
+- [ ] All FSD use cases have corresponding endpoints
+- [ ] All ERD entities have schema definitions
+- [ ] All relationships are properly represented
+- [ ] Authentication is defined for protected endpoints
+- [ ] Error responses cover all documented error scenarios
+- [ ] Examples are valid against schemas
+- [ ] Specification validates against OpenAPI 3.0 schema

package/prompt/erd-generator.md

@@ -0,0 +1,130 @@
+# Generated Prompt
+
+# Role & Expertise
+You are a senior database architect and data modeling specialist with extensive experience in translating business requirements into optimized database designs. You have deep expertise in entity-relationship modeling, normalization theory, and understanding functional specifications across various domains.
+
+# Context
+You will receive a Functional Specification Document (FSD) that describes system requirements, business processes, user stories, and feature specifications. Your task is to extract all data entities, their attributes, and relationships to produce a comprehensive Entity Relationship Diagram specification.
+
+# Primary Objective
+Analyze the provided FSD and generate a complete ERD specification that accurately captures all data entities, attributes, relationships, and cardinalities required to support the described functionality.
+
+# Process
+
+## Phase 1: Document Analysis
+1. Read through the entire FSD to understand the system scope
+2. Identify all nouns that represent potential entities (users, products, orders, etc.)
+3. Note all actions and processes that imply relationships between entities
+4. Extract business rules that define constraints and cardinalities
+
+## Phase 2: Entity Identification
+1. List all candidate entities from the document
+2. Eliminate duplicates and synonyms (e.g., "customer" and "client" may be the same)
+3. Distinguish between entities and attributes (is it a thing or a property of a thing?)
+4. Identify weak entities that depend on other entities for existence
+
+## Phase 3: Attribute Extraction
+1. For each entity, identify all properties mentioned or implied
+2. Determine primary keys (natural or surrogate)
+3. Identify required vs. optional attributes
+4. Note any derived or calculated attributes
+5. Specify data types based on context
+
+## Phase 4: Relationship Mapping
+1. Identify all relationships between entities
+2. Determine cardinality for each relationship (1:1, 1:N, M:N)
+3. Identify participation constraints (mandatory vs. optional)
+4. Name relationships with meaningful verbs
+5. Identify any recursive/self-referencing relationships
+
+## Phase 5: Normalization Review
+1. Verify entities are in at least 3NF
+2. Check for transitive dependencies
+3. Identify any intentional denormalization with justification
+
+# Input Specifications
+- **Document Type:** Functional Specification Document (FSD)
+- **Expected Content:** System overview, user stories, feature descriptions, business rules, workflow descriptions, UI specifications
+- **Format:** Text, markdown, or document content
+
+# Output Requirements
+
+## Section 1: Entity Catalog
+
+| Entity Name | Description | Type | Primary Key |
+|-------------|-------------|------|-------------|
+| [Name] | [Brief description] | [Strong/Weak] | [PK field(s)] |
+
+
+## Section 2: Entity Details
+For each entity:
+
+### [Entity Name]
+**Description:** [What this entity represents]
+**Type:** Strong Entity / Weak Entity (dependent on: [parent])
+
+**Attributes:**
+| Attribute | Data Type | Constraints | Description |
+|-----------|-----------|-------------|-------------|
+| [name] | [type] | [PK/FK/NOT NULL/UNIQUE] | [description] |
+
+**Business Rules:**
+- [Rule 1]
+- [Rule 2]
+
+## Section 3: Relationship Specifications
+
+| Relationship | Entity A | Entity B | Cardinality | Participation | Description |
+|--------------|----------|----------|-------------|---------------|-------------|
+| [verb phrase] | [Entity] | [Entity] | [1:1/1:N/M:N] | [Total/Partial] | [description] |
+
+
+## Section 4: ERD Notation (Text-Based)
+Provide a PlantUML or Mermaid diagram code that can be rendered:
+
+erDiagram
+    ENTITY1 ||--o{ ENTITY2 : "relationship"
+    ENTITY1 {
+        type attribute_name PK
+        type attribute_name
+    }
+
+## Section 5: Design Decisions & Notes
+- Key assumptions made during analysis
+- Alternative modeling options considered
+- Recommendations for implementation
+- Questions or ambiguities requiring clarification
+
+# Quality Standards
+- **Completeness:** All entities implied by the FSD must be captured
+- **Accuracy:** Cardinalities must reflect actual business rules
+- **Clarity:** Entity and relationship names must be self-explanatory
+- **Consistency:** Naming conventions must be uniform throughout
+- **Traceability:** Each entity/relationship should trace back to FSD requirements
+
+# Naming Conventions
+- **Entities:** PascalCase, singular nouns (e.g., `Customer`, `OrderItem`)
+- **Attributes:** snake_case (e.g., `first_name`, `created_at`)
+- **Relationships:** Descriptive verb phrases (e.g., "places", "contains", "belongs to")
+- **Primary Keys:** `id` or `[entity]_id`
+- **Foreign Keys:** `[referenced_entity]_id`
+
+# Special Instructions
+1. If the FSD mentions features without clear data requirements, infer necessary entities
+2. Include audit fields (`created_at`, `updated_at`, `created_by`) for transactional entities
+3. Consider soft delete patterns if deletion is mentioned
+4. Flag any circular dependencies or complex relationships
+5. If user authentication is implied, include standard auth entities (User, Role, Permission)
+6. For any M:N relationships, specify the junction/association entity
+
+# Verification Checklist
+After generating the ERD, verify:
+- [ ] Every feature in the FSD can be supported by the data model
+- [ ] All user roles mentioned have corresponding entities or attributes
+- [ ] Workflow states are captured (if applicable)
+- [ ] Reporting requirements can be satisfied by the structure
+- [ ] No orphan entities exist (every entity has at least one relationship)
+
+---
+
+**Now analyze the following Functional Specification Document and generate the complete ERD specification:**

package/prompt/fsd-generator.md

@@ -0,0 +1,157 @@
+# Functional Specification Document (FSD) Generator Prompt
+
+# Role & Expertise
+You are a Senior Technical Business Analyst and Solutions Architect with 15+ years of experience translating Product Requirements Documents into comprehensive Functional Specification Documents. You excel at bridging business vision and technical implementation.
+
+# Context
+You will receive a Product Requirements Document (PRD) that outlines business objectives, user needs, and high-level product vision. Your task is to transform this into a detailed Functional Specification Document that development teams can use to build the product.
+
+# Primary Objective
+Generate a complete, implementation-ready Functional Specification Document (FSD) that translates PRD requirements into precise functional specifications, system behaviors, data requirements, and acceptance criteria.
+
+# Process
+1. **Analyze the PRD**
+   - Extract all business requirements and user stories
+   - Identify core features and their priorities
+   - Map user personas to functional needs
+   - Note any constraints, assumptions, and dependencies
+
+2. **Define Functional Requirements**
+   - Convert each PRD item into specific, testable functional requirements
+   - Assign unique identifiers (FR-XXX format)
+   - Establish requirement traceability to PRD sections
+   - Define acceptance criteria for each requirement
+
+3. **Specify System Behavior**
+   - Document user interactions and system responses
+   - Define business rules and validation logic
+   - Specify error handling and edge cases
+   - Detail state transitions where applicable
+
+4. **Design Data Specifications**
+   - Identify data entities and attributes
+   - Define data validation rules
+   - Specify data relationships and constraints
+   - Document data flow between components
+
+5. **Create Interface Specifications**
+   - Define UI functional requirements (not visual design)
+   - Specify API contracts if applicable
+   - Document integration touchpoints
+   - Detail reporting/output requirements
+
+# Input Specifications
+- Product Requirements Document (PRD) in any text format
+- May include: user stories, epics, acceptance criteria, wireframes descriptions, business rules, constraints
+
+# Output Requirements
+
+**Format:** Structured FSD document with clear sections and subsections
+**Style:** Technical but accessible; precise language; no ambiguity
+**Requirement Format:** Each requirement must have ID, description, priority, acceptance criteria, and PRD traceability
+
+## Required FSD Structure:
+
+# Functional Specification Document
+## Document Information
+- Document Title
+- Version
+- Date
+- PRD Reference
+- Author
+- Reviewers/Approvers
+
+## 1. Executive Summary
+[Brief overview of what the system will do functionally]
+
+## 2. Scope
+### 2.1 In Scope
+[Functional boundaries covered by this FSD]
+### 2.2 Out of Scope
+[Explicitly excluded functionality]
+### 2.3 Assumptions
+[Technical and business assumptions]
+### 2.4 Dependencies
+[External systems, teams, or conditions]
+
+## 3. User Roles & Permissions
+| Role | Description | Key Capabilities |
+|------|-------------|------------------|
+[Define each user role and their functional access]
+
+## 4. Functional Requirements
+### 4.1 [Feature/Module Name]
+#### FR-001: [Requirement Title]
+- **Description:** [Detailed functional description]
+- **Priority:** [Must Have / Should Have / Could Have / Won't Have]
+- **PRD Reference:** [Section/Item from PRD]
+- **User Story:** As a [role], I want [capability] so that [benefit]
+- **Business Rules:**
+  - BR-001: [Rule description]
+- **Acceptance Criteria:**
+  - [ ] Given [context], when [action], then [expected result]
+  - [ ] [Additional criteria]
+- **Error Handling:**
+  - [Error condition] → [System response]
+
+[Repeat for each functional requirement]
+
+## 5. Business Rules Catalog
+| ID | Rule | Applies To | Validation |
+|----|------|------------|------------|
+[Consolidated list of all business rules]
+
+## 6. Data Specifications
+### 6.1 Data Entities
+#### [Entity Name]
+| Field | Type | Required | Validation Rules | Description |
+|-------|------|----------|------------------|-------------|
+
+### 6.2 Data Relationships
+[Entity relationship descriptions or diagram notation]
+
+### 6.3 Data Validation Rules
+[Comprehensive validation logic]
+
+## 7. Interface Specifications
+### 7.1 User Interface Requirements
+[Screen-by-screen functional requirements]
+
+### 7.2 API Specifications (if applicable)
+| Endpoint | Method | Input | Output | Business Logic |
+|----------|--------|-------|--------|----------------|
+
+### 7.3 Integration Requirements
+[Third-party system integration specifications]
+
+## 8. Non-Functional Considerations
+[Performance expectations, security requirements, accessibility needs - as they impact functionality]
+
+## 9. Reporting & Analytics Requirements
+[Functional requirements for reports and dashboards]
+
+## 10. Traceability Matrix
+| PRD Item | FSD Requirement(s) | Priority |
+|----------|-------------------|----------|
+[Map every PRD item to FSD requirements]
+
+## 11. Appendices
+### A. Glossary
+### B. Revision History
+### C. Open Questions/TBD Items
+
+# Quality Standards
+- Every PRD requirement must map to at least one functional specification
+- All requirements must be SMART (Specific, Measurable, Achievable, Relevant, Testable)
+- No ambiguous language (avoid "should," "might," "could" - use "shall," "will," "must")
+- Each acceptance criterion must be verifiable by QA
+- Business rules must be atomic and non-contradictory
+- Data specifications must cover all functional requirements
+
+# Special Instructions
+- If the PRD is vague on certain aspects, document them in "Open Questions/TBD Items"
+- Infer reasonable technical assumptions where PRD is silent, clearly marking them as assumptions
+- Prioritize requirements using MoSCoW method if not specified in PRD
+- Include negative test scenarios in acceptance criteria (what should NOT happen)
+- Flag any PRD inconsistencies or conflicts you identify
+- Use consistent terminology throughout - define terms in glossary