ultra-dex 1.7.3 → 2.2.0

package/lib/templates/embedded.js

@@ -0,0 +1,141 @@
+import { githubTreeUrl } from '../config/urls.js';
+
+export const CORE_CURSOR_RULE = `# Ultra-Dex Core Rules
+
+> Load this as your base ruleset. Add domain-specific rules as needed.
+
+## Project Philosophy
+
+- Build production-ready from day 1
+- Every task: 4-9 hours with clear acceptance criteria
+- 21-step verification for features (simplified for fixes)
+- Code > Documentation (but document decisions)
+
+## Code Standards
+
+- TypeScript strict mode always
+- Zod validation at all API boundaries
+- Error handling: never swallow errors silently
+- Logging: structured JSON, include request IDs
+- Tests: minimum 80% coverage for business logic
+
+## Architecture Defaults
+
+- Next.js App Router (or specified framework)
+- PostgreSQL with Prisma ORM
+- NextAuth.js for authentication
+- Stripe for payments
+- Vercel for deployment
+
+## Task Completion Checklist (Quick 5-Step)
+
+1. Does it work? (Manual test)
+2. Are there tests? (Automated)
+3. Is it secure? (No secrets exposed, inputs validated)
+4. Is it documented? (Code comments for complex logic)
+5. Is it deployable? (No breaking changes)
+
+## When to Use Full 21-Step
+
+- New features affecting multiple files
+- Security-sensitive changes
+- Database schema changes
+- API contract changes
+
+## File Naming
+
+- Components: PascalCase (UserProfile.tsx)
+- Utilities: camelCase (formatDate.ts)
+- API routes: kebab-case (/api/user-profile)
+- Database: snake_case (user_profiles)
+`;
+
+export const AGENT_INSTRUCTIONS_EMBEDDED = `# Ultra-Dex AI Agent Quick Reference
+
+## Agent Selection
+
+| Task | Agent | Use When |
+|------|-------|----------|
+| Architecture decisions | @CTO | Tech stack, scaling, trade-offs |
+| Task breakdown | @Planner | Feature to atomic tasks |
+| API endpoints | @Backend | REST/GraphQL, middleware |
+| React components | @Frontend | UI, state, forms |
+| Schema design | @Database | Models, migrations, queries |
+| Auth flows | @Security | Login, sessions, permissions |
+| CI/CD setup | @DevOps | Deploy, monitoring, infra |
+| Code review | @Reviewer | PR review, quality gates |
+| Test coverage | @Testing | Unit, integration, E2E |
+| Bug fixing | @Debugger | Root cause, fixes |
+
+## Quick Start Prompts
+
+### @Backend - API Endpoint
+Act as @Backend. Context: [paste CONTEXT.md]
+Task: Create POST /api/users endpoint with validation.
+Requirements: Zod schema, error handling, rate limiting.
+
+### @Database - Schema Design
+Act as @Database. Context: [paste CONTEXT.md]
+Task: Design User and Organization tables with relationships.
+Requirements: Prisma schema, indexes, soft deletes.
+
+### @Frontend - Component
+Act as @Frontend. Context: [paste CONTEXT.md]
+Task: Create UserProfile component with edit form.
+Requirements: React Hook Form, Zod validation, loading states.
+
+## 21-Step Verification (Quick 5)
+
+1. Does it work? (Manual test)
+2. Are there tests? (80%+ coverage)
+3. Is it secure? (Inputs validated, no secrets)
+4. Is it documented? (Complex logic commented)
+5. Is it deployable? (No breaking changes)
+
+---
+Full agents: ${githubTreeUrl('agents')}
+`;
+
+export const VERIFICATION_CHECKLIST = `# Ultra-Dex 21-Step Verification Checklist
+
+## Quick 5 (Every Task)
+- [ ] 1. Does it work? (Manual test)
+- [ ] 2. Are there tests? (Unit tests passing)
+- [ ] 3. Is it secure? (No secrets, inputs validated)
+- [ ] 4. Is it documented? (Comments for complex logic)
+- [ ] 5. Is it deployable? (No breaking changes)
+
+## Full 21 (New Features)
+
+### Understanding (1-4)
+- [ ] 1. Requirements clear?
+- [ ] 2. Assumptions documented?
+- [ ] 3. Logic flow mapped?
+- [ ] 4. Subtasks identified?
+
+### Implementation (5-10)
+- [ ] 5. Setup complete?
+- [ ] 6. Code written?
+- [ ] 7. Comments added?
+- [ ] 8. Unit tests passing?
+- [ ] 9. Bugs fixed?
+- [ ] 10. Integration verified?
+
+### Quality (11-16)
+- [ ] 11. Acceptance criteria met?
+- [ ] 12. UX acceptable?
+- [ ] 13. Performance acceptable?
+- [ ] 14. Security reviewed?
+- [ ] 15. Code refactored?
+- [ ] 16. Errors handled?
+
+### Delivery (17-21)
+- [ ] 17. API documented?
+- [ ] 18. Committed?
+- [ ] 19. Build passing?
+- [ ] 20. Deploy ready?
+- [ ] 21. Final verified?
+
+---
+Use Quick 5 for bug fixes. Use Full 21 for new features.
+`;

package/lib/templates/prompts/generate-plan.js

@@ -0,0 +1,147 @@
+/**
+ * Prompt templates for ultra-dex generate command
+ * Generates a full 34-section implementation plan from an idea
+ */
+
+export const SYSTEM_PROMPT = `You are an expert SaaS architect and product strategist. Your job is to take a simple product idea and generate a complete, production-ready implementation plan.
+
+You MUST output a complete plan covering all 34 sections of the Ultra-Dex framework. Each section must be actionable and specific - no generic placeholders.
+
+QUALITY STANDARDS:
+- All acceptance criteria MUST be measurable (not "should work well" → use "<200ms response time")
+- All estimates MUST include buffer (+20% for unknowns)
+- All code examples MUST be production-ready (error handling, edge cases)
+- All API endpoints MUST include request/response examples
+- All database schemas MUST include indexes and constraints
+
+SPECIFICITY RULES:
+- Product Vision: ≤15 words, memorable
+- Feature descriptions: User story + acceptance criteria + edge cases
+- Task definitions: Single responsibility, testable completion
+- Time estimates: 4-9 hours per atomic task
+
+OUTPUT FORMAT:
+- Use markdown with proper headers (## Section X: Title)
+- Use tables for structured data
+- Use code blocks with language tags
+- Use checkboxes (- [ ]) for action items`;
+
+export const USER_PROMPT_TEMPLATE = `Generate a complete Ultra-Dex implementation plan for this idea:
+
+**IDEA:** {{IDEA}}
+
+Generate ALL 34 sections with specific, actionable content:
+
+## SECTION 1: HIGH-LEVEL SUMMARY
+### 1.1 Product Vision (One-liner)
+### 1.2 Problem Statement
+### 1.3 Solution Overview
+### 1.4 Target Market
+### 1.5 Unique Value Proposition
+### 1.6 Success Metrics
+
+## SECTION 2: CORE FEATURES
+### 2.1 Core Production Features (P0)
+### 2.2 Enhanced Features (P1)
+### 2.3 Future Features (P2/P3)
+
+## SECTION 3: PRODUCT DESCRIPTION
+
+## SECTION 4: USER PERSONAS
+(Include 2-3 detailed personas with goals, frustrations, tech comfort)
+
+## SECTION 5: USER JOURNEYS
+(Map key user flows with touchpoints)
+
+## SECTION 6: SCREEN MAP
+(List all screens/pages with purpose)
+
+## SECTION 7: WIREFRAMES DESCRIPTION
+(Describe layout for key screens)
+
+## SECTION 8: NAVIGATION STRUCTURE
+
+## SECTION 9: UI/UX SPECIFICATIONS
+(Design tokens, component library choice, accessibility requirements)
+
+## SECTION 10: DATA MODEL
+(Complete database schema with Prisma syntax, indexes, relationships)
+
+## SECTION 11: API BLUEPRINT
+(REST endpoints with methods, request/response examples)
+
+## SECTION 12: SYSTEM ARCHITECTURE
+(Monolith/microservices decision, component diagram)
+
+## SECTION 13: THIRD-PARTY INTEGRATIONS
+(APIs, services with specific providers)
+
+## SECTION 14: AUTHENTICATION & AUTHORIZATION
+(Auth flow, RBAC, session management - be specific about provider)
+
+## SECTION 15: TECH STACK
+(Frontend, backend, database, hosting - with specific versions)
+
+## SECTION 16: IMPLEMENTATION PLAN
+(Atomic tasks with 4-9 hour estimates, dependencies)
+
+## SECTION 17: MILESTONES & TIMELINE
+(Sprint breakdown with deliverables)
+
+## SECTION 18: RISK ASSESSMENT
+(Technical and business risks with mitigations)
+
+## SECTION 19: DEPLOYMENT PLAN
+(CI/CD, environments, rollback strategy)
+
+## SECTION 20: TESTING STRATEGY
+(Unit, integration, E2E approach with coverage targets)
+
+## SECTION 21: SECURITY GUIDELINES
+(OWASP top 10 mitigations, data protection)
+
+## SECTION 22: PERFORMANCE REQUIREMENTS
+(Response times, concurrent users, optimization strategy)
+
+## SECTION 23: MONITORING & LOGGING
+(Observability stack, alerts, dashboards)
+
+## SECTION 24: DOCUMENTATION PLAN
+
+## SECTION 25: MAINTENANCE PLAN
+
+## SECTION 26: COST ESTIMATION
+(Infrastructure, API costs with specific pricing)
+
+## SECTION 27: ERROR HANDLING
+(Error codes, user messaging, recovery flows)
+
+## SECTION 28: LEGAL & COMPLIANCE
+(Privacy policy, ToS, GDPR considerations)
+
+## SECTION 29: SEO STRATEGY
+
+## SECTION 30: INTERNATIONALIZATION
+
+## SECTION 31: FEATURE FLAGS
+
+## SECTION 32: REAL-TIME FEATURES
+(WebSocket/SSE architecture if needed)
+
+## SECTION 33: AI/ML FEATURES
+(If applicable)
+
+## SECTION 34: SUPPORT SYSTEM
+(Help docs, feedback collection)
+
+Be thorough and specific. This plan will be used directly for implementation.`;
+
+export function generateUserPrompt(idea) {
+  return USER_PROMPT_TEMPLATE.replace('{{IDEA}}', idea);
+}
+
+export default {
+  SYSTEM_PROMPT,
+  USER_PROMPT_TEMPLATE,
+  generateUserPrompt,
+};

package/lib/templates/prompts/review-code.js

@@ -0,0 +1,57 @@
+/**
+ * Prompt templates for ultra-dex review command
+ * Reviews code against the implementation plan
+ */
+
+export const SYSTEM_PROMPT = `You are a code auditor for the Ultra-Dex framework. Your job is to compare the actual codebase against the implementation plan and report:
+
+1. ALIGNMENT - What matches the plan
+2. DEVIATIONS - What differs from the plan
+3. GAPS - What's missing from the plan
+4. SUGGESTIONS - How to get back on track
+
+OUTPUT FORMAT:
+Return a JSON object with this structure:
+{
+  "alignmentScore": 0-100,
+  "summary": "One paragraph overview",
+  "sections": {
+    "database": { "score": 0-100, "status": "aligned|deviated|missing", "notes": "..." },
+    "api": { "score": 0-100, "status": "aligned|deviated|missing", "notes": "..." },
+    "auth": { "score": 0-100, "status": "aligned|deviated|missing", "notes": "..." },
+    "frontend": { "score": 0-100, "status": "aligned|deviated|missing", "notes": "..." },
+    "security": { "score": 0-100, "status": "aligned|deviated|missing", "notes": "..." },
+    "testing": { "score": 0-100, "status": "aligned|deviated|missing", "notes": "..." }
+  },
+  "criticalIssues": ["issue1", "issue2"],
+  "suggestions": ["suggestion1", "suggestion2"],
+  "nextSteps": ["step1", "step2"]
+}
+
+Be strict but fair. Focus on production-readiness.`;
+
+export const USER_PROMPT_TEMPLATE = `Review this codebase against the implementation plan:
+
+## IMPLEMENTATION PLAN:
+{{PLAN}}
+
+## CODEBASE STRUCTURE:
+{{STRUCTURE}}
+
+## KEY FILES:
+{{FILES}}
+
+Analyze alignment and return the JSON report.`;
+
+export function generateReviewPrompt(plan, structure, files) {
+  return USER_PROMPT_TEMPLATE
+    .replace('{{PLAN}}', plan)
+    .replace('{{STRUCTURE}}', structure)
+    .replace('{{FILES}}', files);
+}
+
+export default {
+  SYSTEM_PROMPT,
+  USER_PROMPT_TEMPLATE,
+  generateReviewPrompt,
+};

package/lib/templates/prompts/section-prompts.js

@@ -0,0 +1,275 @@
+/**
+ * Section Prompts for 34-Section Implementation Plan Generation
+ * These prompts guide the AI to generate each section properly
+ */
+
+export const SECTION_STRUCTURE = `
+## SECTION 1: HIGH-LEVEL SUMMARY
+### 1.1 Product Vision (One-liner)
+### 1.2 Problem Statement
+### 1.3 Solution Overview
+### 1.4 Target Market
+### 1.5 Unique Value Proposition
+### 1.6 Success Metrics (Key)
+
+## SECTION 2: CORE FEATURES
+### 2.1 Feature List (Priority-Ordered)
+### 2.2 Feature Details
+### 2.3 MVP Scope
+### 2.4 Post-MVP Features
+
+## SECTION 3: USER STORIES
+### 3.1 User Journey Maps
+### 3.2 User Stories by Role
+### 3.3 Acceptance Criteria
+
+## SECTION 4: USER PERSONAS
+### 4.1 Primary Persona
+### 4.2 Secondary Personas
+### 4.3 Anti-Personas
+
+## SECTION 5: COMPETITIVE ANALYSIS
+### 5.1 Direct Competitors
+### 5.2 Indirect Competitors
+### 5.3 Differentiators
+### 5.4 SWOT Analysis
+
+## SECTION 6: SCREEN MAP
+### 6.1 Information Architecture
+### 6.2 Navigation Structure
+### 6.3 Key Screens List
+### 6.4 User Flows
+
+## SECTION 7: WIREFRAMES
+### 7.1 Low-Fidelity Wireframes
+### 7.2 Key Screen Descriptions
+### 7.3 Interaction Notes
+
+## SECTION 8: DESIGN SYSTEM
+### 8.1 Color Palette
+### 8.2 Typography
+### 8.3 Component Library
+### 8.4 Accessibility Guidelines
+
+## SECTION 9: UI/UX SPECIFICATIONS
+### 9.1 Design Principles
+### 9.2 Responsive Breakpoints
+### 9.3 Animation Guidelines
+### 9.4 Form Patterns
+
+## SECTION 10: DATA MODEL
+### 10.1 Entity Relationship Diagram
+### 10.2 Database Schema
+### 10.3 Indexes and Constraints
+### 10.4 Data Migrations Strategy
+
+## SECTION 11: API BLUEPRINT
+### 11.1 API Architecture
+### 11.2 Endpoint Documentation
+### 11.3 Authentication Flow
+### 11.4 Rate Limiting
+
+## SECTION 12: SYSTEM ARCHITECTURE
+### 12.1 High-Level Architecture
+### 12.2 Component Diagram
+### 12.3 Data Flow
+### 12.4 Third-Party Integrations
+
+## SECTION 13: AUTHENTICATION & AUTHORIZATION
+### 13.1 Auth Strategy
+### 13.2 Role-Based Access Control
+### 13.3 Session Management
+### 13.4 OAuth Providers
+
+## SECTION 14: PAYMENT INTEGRATION
+### 14.1 Payment Provider
+### 14.2 Pricing Plans
+### 14.3 Subscription Management
+### 14.4 Billing Workflows
+
+## SECTION 15: TECH STACK
+### 15.1 Frontend
+### 15.2 Backend
+### 15.3 Database
+### 15.4 Infrastructure
+### 15.5 Development Tools
+
+## SECTION 16: IMPLEMENTATION PLAN
+### 16.1 Phase Breakdown
+### 16.2 Sprint Planning
+### 16.3 Task Breakdown (Atomic Tasks)
+### 16.4 Dependencies
+
+## SECTION 17: TIMELINE
+### 17.1 Milestone Schedule
+### 17.2 Critical Path
+### 17.3 Buffer Time
+
+## SECTION 18: RISK ASSESSMENT
+### 18.1 Technical Risks
+### 18.2 Business Risks
+### 18.3 Mitigation Strategies
+
+## SECTION 19: DEPLOYMENT PLAN
+### 19.1 Environment Setup
+### 19.2 CI/CD Pipeline
+### 19.3 Deployment Checklist
+### 19.4 Rollback Strategy
+
+## SECTION 20: TESTING STRATEGY
+### 20.1 Testing Pyramid
+### 20.2 Unit Tests
+### 20.3 Integration Tests
+### 20.4 E2E Tests
+### 20.5 Coverage Targets
+
+## SECTION 21: SECURITY GUIDELINES
+### 21.1 Security Checklist
+### 21.2 OWASP Considerations
+### 21.3 Data Protection
+### 21.4 Vulnerability Scanning
+
+## SECTION 22: PERFORMANCE REQUIREMENTS
+### 22.1 Performance Targets
+### 22.2 Caching Strategy
+### 22.3 Database Optimization
+### 22.4 CDN Configuration
+
+## SECTION 23: MONITORING & LOGGING
+### 23.1 Logging Strategy
+### 23.2 Monitoring Tools
+### 23.3 Alerting Rules
+### 23.4 Dashboards
+
+## SECTION 24: MAINTENANCE PLAN
+### 24.1 Update Schedule
+### 24.2 Dependency Management
+### 24.3 Technical Debt Tracking
+
+## SECTION 25: DOCUMENTATION
+### 25.1 Code Documentation
+### 25.2 API Documentation
+### 25.3 User Documentation
+### 25.4 Runbooks
+
+## SECTION 26: ANALYTICS
+### 26.1 Analytics Strategy
+### 26.2 Key Metrics
+### 26.3 Tracking Implementation
+### 26.4 Reporting
+
+## SECTION 27: ERROR HANDLING
+### 27.1 Error Strategy
+### 27.2 User-Facing Errors
+### 27.3 System Errors
+### 27.4 Error Recovery
+
+## SECTION 28: LEGAL & COMPLIANCE
+### 28.1 Privacy Policy
+### 28.2 Terms of Service
+### 28.3 GDPR Compliance
+### 28.4 Data Retention
+
+## SECTION 29: SEO
+### 29.1 SEO Strategy
+### 29.2 Meta Tags
+### 29.3 Sitemap
+### 29.4 Structured Data
+
+## SECTION 30: INTERNATIONALIZATION
+### 30.1 i18n Strategy
+### 30.2 Supported Languages
+### 30.3 Localization Workflow
+
+## SECTION 31: ACCESSIBILITY
+### 31.1 WCAG Compliance Level
+### 31.2 Accessibility Checklist
+### 31.3 Testing Tools
+
+## SECTION 32: FEATURE FLAGS
+### 32.1 Feature Flag Strategy
+### 32.2 Flag Categories
+### 32.3 Rollout Process
+
+## SECTION 33: AI/ML INTEGRATION
+### 33.1 AI Features (if applicable)
+### 33.2 Model Selection
+### 33.3 Training Data
+### 33.4 Fallback Strategy
+
+## SECTION 34: FUTURE ROADMAP
+### 34.1 Version 2.0 Features
+### 34.2 Long-term Vision
+### 34.3 Scalability Plan
+`;
+
+export const USER_PROMPT_TEMPLATE = `
+Generate a complete Ultra-Dex implementation plan for the following idea:
+
+**IDEA:** {{IDEA}}
+
+## Requirements
+
+1. Fill out ALL 34 sections completely - no shortcuts
+2. Be specific to this exact product idea
+3. Use the default tech stack unless the idea requires something different:
+   - Frontend: Next.js 15 + TypeScript + Tailwind CSS
+   - Backend: Next.js API Routes + Prisma ORM
+   - Database: PostgreSQL
+   - Auth: NextAuth.js
+   - Payments: Stripe
+   - Hosting: Vercel
+4. Break down implementation into 4-9 hour atomic tasks
+5. Include realistic time estimates with +20% buffer
+6. Add code examples for database schema, API endpoints, and key components
+
+## Output Format
+
+Start with a header:
+
+\`\`\`
+═══════════════════════════════════════════════════════════════
+PROJECT: [Derived project name]
+GENERATED: [Current date]
+IDEA: {{IDEA}}
+═══════════════════════════════════════════════════════════════
+\`\`\`
+
+Then output all 34 sections following this structure:
+
+${SECTION_STRUCTURE}
+
+Be thorough, specific, and production-ready. This plan should be immediately actionable by a development team.
+`;
+
+export const QUICK_START_PROMPT = `
+Based on the implementation plan you just generated, create a concise QUICK-START.md file that:
+
+1. Summarizes the idea in 2 sentences
+2. Lists the top 3 problems solved
+3. Shows the 5 core features (priority ordered)
+4. Displays the tech stack in a table
+5. Lists the first 3 tasks to get started
+
+Keep it under 50 lines. Make it scannable.
+`;
+
+export const CONTEXT_PROMPT = `
+Based on the implementation plan, create a CONTEXT.md file for AI agents that includes:
+
+1. Project Overview (name, status, current focus)
+2. Quick Summary (what it does, for whom)
+3. Key Technical Decisions (stack choices)
+4. Current Phase (what's being built now)
+5. Links to resources
+
+This file will be used to give AI coding agents context about the project.
+Keep it under 40 lines.
+`;
+
+export default {
+  SECTION_STRUCTURE,
+  USER_PROMPT_TEMPLATE,
+  QUICK_START_PROMPT,
+  CONTEXT_PROMPT,
+};

package/lib/templates/prompts/system-prompt.md

@@ -0,0 +1,58 @@
+# Ultra-Dex System Prompt for Implementation Plan Generation
+
+You are an expert SaaS architect and implementation planner. Your task is to generate a comprehensive, production-ready implementation plan for a SaaS application based on a simple idea.
+
+## Your Role
+
+You are acting as a senior technical architect with expertise in:
+- Full-stack SaaS development
+- Database design and optimization
+- API architecture and security
+- User experience and interface design
+- DevOps and deployment strategies
+- Business model and monetization
+
+## Output Requirements
+
+Generate a **complete 34-section implementation plan** following the Ultra-Dex framework. The output must be:
+
+1. **Production-Ready**: Every detail should be actionable, not theoretical
+2. **Specific**: Use concrete numbers, technologies, and timelines
+3. **Comprehensive**: Cover all 34 sections without shortcuts
+4. **Realistic**: Include honest time estimates with buffer (+20% minimum)
+
+## Quality Standards
+
+### For Every Section:
+- Provide specific, measurable acceptance criteria
+- Include concrete examples and code snippets where applicable
+- Reference real technologies (not "a database" but "PostgreSQL with Prisma ORM")
+- Estimate realistic timelines in 4-9 hour atomic tasks
+
+### For Technical Decisions:
+- Default stack: Next.js 15 + TypeScript + Prisma + PostgreSQL + NextAuth.js + Stripe + Vercel
+- All API endpoints must include request/response examples
+- All database schemas must include indexes and constraints
+- All estimates must include buffer for unknowns
+
+### For Business Decisions:
+- Include competitive analysis
+- Provide pricing strategy with justification
+- Define clear success metrics (MRR, users, engagement)
+
+## Output Format
+
+Output must be valid Markdown following the exact section structure provided. Include:
+- All section headers exactly as specified (## SECTION X: TITLE)
+- Tables for comparison data
+- Checklists (- [ ]) for action items
+- Code blocks with language tags
+- Proper heading hierarchy
+
+## Important Notes
+
+- Do NOT skip or merge sections
+- Do NOT use placeholder text like "[TBD]" or "[Fill in later]"
+- Do NOT provide generic advice - be specific to the idea
+- Include edge cases and error handling considerations
+- Consider security implications throughout