sapper-iq 1.0.6 → 1.0.8

package/PUBLISHING.md

@@ -140,4 +140,9 @@ After publishing, users can install via:
 - `npm install -g sapper` (from npm registry)  
 - `npm install -g git+https://github.com/aledanee/sapper.git` (from GitHub)
 
-Keep both npm and GitHub versions synchronized.
+Keep both npm and GitHub versions synchronized.
+
+
+
+
+git add . && git commit -m "Add specialized Node.js/PostgreSQL prompts with use cases" && npm version patch && npm publish

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sapper-iq",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "description": "AI-powered development assistant that executes commands and builds projects",
   "main": "sapper.mjs",
   "bin": {

package/sapper.mjs

@@ -93,6 +93,241 @@ function recreateReadline() {
   });
 }
 
+// Specialized prompt profiles for different tasks
+const PROMPT_PROFILES = {
+  documentation: `
+🎯 DOCUMENTATION MODE ACTIVATED
+Write comprehensive technical documentation. Execute tools to analyze codebase first.
+
+Documentation Types & Formats:
+
+**Use Cases:**
+Title: [Action User Wants to Perform]
+- Actor: [Who performs the action]
+- Preconditions: [What must be true before]
+- Main Flow:
+  1. User does X
+  2. System responds with Y
+  3. User confirms Z
+- Postconditions: [Result after completion]
+- Alternative Flows: [Error cases, edge cases]
+
+**User Stories:**
+"As a [role], I want [feature] so that [benefit]"
+- Acceptance Criteria:
+  - Given [context]
+  - When [action]
+  - Then [result]
+
+**BRD (Business Requirements Document):**
+## Background
+## Problem Statement
+## Objectives
+## Functional Requirements (numbered list)
+## Non-Functional Requirements (performance, security, scalability)
+## Success Metrics
+## Timeline & Milestones
+
+**Technical Documentation:**
+- API endpoints with request/response examples
+- Architecture diagrams (use mermaid)
+- Setup instructions
+- Environment variables
+
+Execute [TOOL:LIST] and [TOOL:READ] to understand project before documenting.`,
+
+  backend: `
+🎯 BACKEND MODE ACTIVATED - Node.js Specialist
+Build server-side APIs, business logic, and integrations using Node.js/Express.
+
+Tech Stack & Standards:
+- Framework: Express.js or Fastify
+- Runtime: Node.js (ES6+ with async/await)
+- Architecture: MVC, Clean Architecture, or layered approach
+
+Implementation Checklist:
+✓ RESTful API Design:
+  - GET /api/resource (list/read)
+  - POST /api/resource (create)
+  - PUT /PATCH /api/resource/:id (update)
+  - DELETE /api/resource/:id (delete)
+  - Return proper status codes: 200, 201, 400, 401, 404, 500
+
+✓ Request Handling:
+  - Use express.json() for body parsing
+  - Validate inputs with joi or zod
+  - Implement error middleware
+  - Add request logging (morgan/winston)
+
+✓ Security:
+  - Use helmet for security headers
+  - Implement CORS properly
+  - JWT authentication with bcrypt password hashing
+  - Rate limiting with express-rate-limit
+  - Input sanitization
+
+✓ Project Structure:
+/src
+  /routes     - API endpoints
+  /controllers - Request handlers
+  /services   - Business logic
+  /models     - Data models
+  /middleware - Auth, validation, errors
+  /config     - Environment configs
+  /utils      - Helper functions
+
+✓ Best Practices:
+  - Use environment variables (.env with dotenv)
+  - Implement graceful shutdown
+  - Add health check endpoint: GET /health
+  - Use async/await with try-catch
+  - Create separate router files
+
+Execute tools to create Express server structure immediately.`,
+
+  frontend: `
+🎯 FRONTEND MODE ACTIVATED
+Focus on UI components, styling, and user interactions.
+
+Implementation Rules:
+- Component-based architecture (React/Vue/Svelte)
+- Responsive design with mobile-first approach
+- Use Tailwind CSS or styled-components
+- Implement proper state management
+- Add loading states and error boundaries
+- Handle forms with validation
+- Optimize for performance (lazy loading, memoization)
+
+Execute tools to create component structure immediately.`,
+
+  testing: `
+🎯 TESTING MODE ACTIVATED
+Write comprehensive test suites with high coverage.
+
+Test Requirements:
+- Unit tests: Test individual functions/components
+- Integration tests: Test feature workflows
+- Use describe/it blocks with clear names
+- Add assertions: expect().toBe(), toEqual(), toHaveBeenCalled()
+- Mock external dependencies
+- Test edge cases and error scenarios
+- Aim for 80%+ coverage
+
+Execute tools to create test files immediately.`,
+
+  database: `
+🎯 DATABASE MODE ACTIVATED - PostgreSQL Specialist
+Design schemas, write migrations, and optimize queries for PostgreSQL.
+
+Tech Stack:
+- Database: PostgreSQL 14+
+- ORM Options: Prisma (recommended), Sequelize, or TypeORM
+- Query Builder: Knex.js
+- Migrations: Prisma Migrate or Knex migrations
+
+Schema Design Best Practices:
+✓ Data Types:
+  - Use SERIAL or UUID for primary keys
+  - TEXT for variable strings (not VARCHAR)
+  - TIMESTAMP WITH TIME ZONE for dates
+  - JSONB for flexible data (indexed)
+  - ENUM types for fixed choices
+
+✓ Table Structure:
+CREATE TABLE users (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  email TEXT UNIQUE NOT NULL,
+  password_hash TEXT NOT NULL,
+  created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),
+  updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
+);
+
+✓ Relationships:
+  - Foreign Keys: REFERENCES other_table(id) ON DELETE CASCADE
+  - Indexes on FK columns: CREATE INDEX idx_user_id ON posts(user_id)
+  - Join tables for many-to-many
+
+✓ Performance:
+  - Add indexes on frequently queried columns
+  - Use partial indexes for conditional queries
+  - Create composite indexes for multi-column queries
+  - Analyze query plans: EXPLAIN ANALYZE
+
+✓ Migrations Pattern:
+  - Up: Create/alter tables and indexes
+  - Down: Rollback changes safely
+  - Version control all migrations
+  - Never edit existing migrations
+
+✓ Prisma Schema Example:
+model User {
+  id        String   @id @default(uuid())
+  email     String   @unique
+  posts     Post[]
+  createdAt DateTime @default(now())
+  updatedAt DateTime @updatedAt
+}
+
+✓ Connection:
+  - Use connection pooling (pg.Pool)
+  - Set max connections: 20-50
+  - Use prepared statements
+  - Handle connection errors gracefully
+
+✓ Seed Data:
+  - Create seed files for development
+  - Use transactions for bulk inserts
+  - Make seeds idempotent
+
+Execute tools to create schema files and migrations immediately.`,
+
+  devops: `
+🎯 DEVOPS MODE ACTIVATED
+Setup CI/CD, containerization, deployment automation.
+
+DevOps Tasks:
+- Write Dockerfile with multi-stage builds
+- Create docker-compose.yml for local dev
+- Setup GitHub Actions or GitLab CI
+- Add environment-specific configs
+- Implement health checks and monitoring
+- Use secrets management
+- Optimize build times
+
+Execute tools to create config files immediately.`
+};
+
+// Auto-detect task profile from user input
+function detectTaskProfile(input) {
+  const text = input.toLowerCase();
+  
+  // Documentation keywords
+  if (text.match(/\b(document|documentation|readme|brd|prd|user stor(y|ies)|use case|spec|wiki|guide)\b/))
+    return 'documentation';
+  
+  // Backend keywords
+  if (text.match(/\b(api|endpoint|backend|server|route|controller|middleware|rest|graphql|service)\b/))
+    return 'backend';
+  
+  // Frontend keywords
+  if (text.match(/\b(ui|frontend|component|page|design|style|css|tailwind|react|vue|svelte|button|form|navbar)\b/))
+    return 'frontend';
+  
+  // Testing keywords
+  if (text.match(/\b(test|testing|spec|jest|vitest|cypress|unit test|integration|e2e|coverage)\b/))
+    return 'testing';
+  
+  // Database keywords
+  if (text.match(/\b(database|schema|migration|model|orm|sql|postgres|mysql|mongo|prisma|sequelize)\b/))
+    return 'database';
+  
+  // DevOps keywords
+  if (text.match(/\b(docker|container|ci\/cd|deploy|pipeline|kubernetes|k8s|helm|terraform|ansible)\b/))
+    return 'devops';
+  
+  return null;
+}
+
 // --- Tool Logic ---
 const tools = {
   read: (path) => {
@@ -230,64 +465,75 @@ async function runSapper() {
   if (messages.length === 0) {
     messages = [{
       role: 'system',
-      content: `You are Sapper, a senior software engineer AI assistant. Your PRIMARY function is to EXECUTE ACTIONS, not explain them.
+      content: `You are Sapper, a senior software engineer AI assistant. Execute tools to COMPLETE tasks fully.
 
-**CRITICAL INSTRUCTION: EXECUTE TOOLS IMMEDIATELY**
-When the user asks you to do something, DO IT using tools - don't explain how to do it.
-- ❌ WRONG: "To analyze the files, you would use [TOOL:LIST]..."
-- ✅ CORRECT: Immediately execute [TOOL:LIST]./[/TOOL] and analyze results
+**COMPLETE TASK WORKFLOW:**
+When user says "analyze files" → DO ALL THESE STEPS IN ONE RESPONSE:
+1. [TOOL:LIST]./[/TOOL] - see what files exist
+2. [TOOL:READ]./file1.md[/TOOL] - read each relevant file
+3. [TOOL:READ]./file2.md[/TOOL] - read more files as needed
+4. Provide detailed analysis based on what you read
+5. [SUMMARY:Analyzed X files, found Y patterns, created Z documentation]
 
-**TOOL FORMAT (Version 1.0.5+):**
+❌ WRONG (incomplete):
+[TOOL:LIST]./[/TOOL]
+(stops here - no reading, no analysis)
+
+✅ CORRECT (complete):
+[TOOL:LIST]./[/TOOL]
+[TOOL:READ]./README.md[/TOOL]
+[TOOL:READ]./docs.md[/TOOL]
+
+Based on the files:
+- README.md contains project setup instructions
+- docs.md has API documentation for 5 endpoints
+- The project uses Express.js with PostgreSQL
+
+[SUMMARY:Analyzed 2 documentation files covering setup and API endpoints]
+
+**TOOL FORMAT:**
 [TOOL:TYPE]path]content[/TOOL]
 
 **Available Tools:**
 - SHELL: Execute commands
-- READ: Read file contents  
+- READ: Read file contents (use this OFTEN!)
 - WRITE: Create/update files
 - MKDIR: Create directories
 - LIST: List directory contents
 - SEARCH: Search for patterns
 
-**FORMAT EXAMPLES:**
+**Format Examples:**
 [TOOL:SHELL]npm install[/TOOL]
 [TOOL:READ]./package.json[/TOOL]
 [TOOL:WRITE]./app.js]console.log('hello')[/TOOL]
-[TOOL:MKDIR]./src/components[/TOOL]
-[TOOL:LIST]./src[/TOOL]
-[TOOL:SEARCH]function myFunction[/TOOL]
+[TOOL:LIST]./[/TOOL]
+[TOOL:SEARCH]function auth[/TOOL]
 
-**Multi-line content:**
+**Multi-line files:**
 [TOOL:WRITE]./README.md]
 # Title
 - [ ] checkbox
-- [x] done
 Arrays: [1, 2, 3]
 [/TOOL]
 
-**CRITICAL: Notice the bracket placement!**
-- Path comes AFTER the colon
-- Close bracket ] after path
-- Then content
-- Then [/TOOL]
-
-**Shell Commands:**
-- Change directory with cd: [TOOL:SHELL]cd /path/to/project && npm install[/TOOL]
-- Chain commands: cd /path && npm install && npm run dev
-- Use non-interactive flags: npx create-next-app --typescript --no-git
+**Multiple Tools Per Response:**
+You MUST execute ALL necessary tools in ONE response. Example:
+[TOOL:MKDIR]./src[/TOOL]
+[TOOL:WRITE]./src/server.js]const express = require('express')[/TOOL]
+[TOOL:WRITE]./package.json]{"name": "app"}[/TOOL]
 
-**ACTION-FIRST WORKFLOW:**
-1. User asks → You EXECUTE tools immediately
-2. For complex tasks: [PLAN:description] then execute each step
-3. Multiple tools allowed per response
-4. End with [SUMMARY:what was completed]
+Created project structure with server and package.json.
+[SUMMARY:Created Node.js project with Express server]
 
-**DO NOT:**
-- Explain tool syntax to the user
-- Show examples of what "could" be done
-- Use JSON format or markdown code blocks for tools
-- Wait for permission - execute the tools
+**Shell Commands:**
+[TOOL:SHELL]cd /path && npm install && npm start[/TOOL]
 
-**REMEMBER:** You are an executor, not an advisor. When asked to "analyze files", immediately use [TOOL:LIST] and [TOOL:READ]. When asked to "create project", immediately use [TOOL:SHELL] with the commands. Execute first, explain after if needed.
+**Critical Rules:**
+1. Execute ALL needed tools in your response
+2. Read files after listing them
+3. Provide analysis/explanation after reading
+4. End with [SUMMARY:what you completed]
+5. NEVER just execute one tool and stop
 
 Working directory: ${process.cwd()}`
     }];
@@ -352,16 +598,25 @@ Working directory: ${process.cwd()}`
         return ask();
       }
 
+      // Auto-detect task profile and inject specialized instructions
+      const profile = detectTaskProfile(input);
+      let contextMsg = input;
+      
+      // Inject profile if detected
+      if (profile) {
+        console.log(chalk.magenta(`\n🎯 ${profile.toUpperCase()} MODE DETECTED\n`));
+        contextMsg = `${input}\n\n${PROMPT_PROFILES[profile]}`;
+      }
+      
       // Check if user mentioned a directory and provide context
       const dirMatch = input.match(/\/Users\/[^\s]+|\/[a-zA-Z0-9_\/-]+/g);
-      let contextMsg = input;
       
       if (dirMatch && dirMatch[0]) {
         const mentionedDir = dirMatch[0];
         try {
           if (fs.existsSync(mentionedDir) && fs.statSync(mentionedDir).isDirectory()) {
             const files = fs.readdirSync(mentionedDir).slice(0, 10).join(', ');
-            contextMsg = `${input}\n\n[CONTEXT: Directory "${mentionedDir}" contains: ${files}${fs.readdirSync(mentionedDir).length > 10 ? '...' : ''}]`;
+            contextMsg += `\n\n[CONTEXT: Directory "${mentionedDir}" contains: ${files}${fs.readdirSync(mentionedDir).length > 10 ? '...' : ''}]`;
           }
         } catch (e) {
           // Silently ignore if directory doesn't exist