@ekkos/cli 1.3.2 → 1.3.5

package/templates/plan-template.md

@@ -1,306 +0,0 @@
-# Implementation Plan: [Feature Name]
-
-## Overview
-**Technical implementation plan for [Feature Name] based on the specification.**
-
-## Architecture Overview
-
-### System Components
-- **Frontend**: React components and state management
-- **API Layer**: Next.js API routes and middleware
-- **AI Services**: AI provider integration and processing
-- **Database**: Supabase data storage and queries
-- **External APIs**: Third-party service integrations
-
-### Data Flow
-```
-User Input → Frontend → API Route → AI Processing → Database → Response
-```
-
-## Technical Stack
-
-### Frontend
-- **Framework**: Next.js 15.5.2 with React 19
-- **Styling**: Tailwind CSS
-- **State Management**: React hooks and context
-- **Type Safety**: TypeScript
-
-### Backend
-- **Runtime**: Node.js with Next.js API routes
-- **Database**: Supabase (PostgreSQL)
-- **AI Providers**: OpenAI, Gemini (Google AI)
-- **Authentication**: Supabase Auth (planned)
-
-### External Services
-- **YouTube API**: Content extraction
-- **AI APIs**: OpenAI, Google AI (Gemini)
-- **Content Processing**: Custom extraction services
-
-## Implementation Phases
-
-### Phase 1: Foundation Setup
-**Duration**: 1-2 days
-
-#### Tasks
-- [ ] **Database Schema**: Create/modify database tables
-- [ ] **API Contracts**: Define request/response interfaces
-- [ ] **Type Definitions**: Create TypeScript interfaces
-- [ ] **Environment Setup**: Configure required environment variables
-
-#### Deliverables
-- Database migration scripts
-- TypeScript interface definitions
-- API endpoint specifications
-- Environment configuration
-
-### Phase 2: Core Implementation
-**Duration**: 3-5 days
-
-#### Backend Implementation
-- [ ] **API Routes**: Implement Next.js API endpoints
-- [ ] **AI Integration**: Connect to AI providers
-- [ ] **Data Processing**: Implement content processing logic
-- [ ] **Error Handling**: Implement comprehensive error handling
-
-#### Frontend Implementation
-- [ ] **UI Components**: Create React components
-- [ ] **State Management**: Implement data flow
-- [ ] **User Interface**: Design and implement user interactions
-- [ ] **Responsive Design**: Ensure mobile compatibility
-
-#### Deliverables
-- Working API endpoints
-- Functional UI components
-- AI integration working
-- Basic error handling
-
-### Phase 3: Integration and Testing
-**Duration**: 2-3 days
-
-#### Integration Tasks
-- [ ] **End-to-End Testing**: Test complete user workflows
-- [ ] **AI Provider Testing**: Validate AI accuracy and performance
-- [ ] **Error Scenario Testing**: Test failure modes and recovery
-- [ ] **Performance Testing**: Validate response times and throughput
-
-#### Quality Assurance
-- [ ] **Code Review**: Review all implementation code
-- [ ] **Security Review**: Validate security measures
-- [ ] **Accessibility Review**: Ensure accessibility compliance
-- [ ] **Documentation**: Update technical documentation
-
-#### Deliverables
-- Fully tested feature
-- Performance benchmarks
-- Security validation
-- Updated documentation
-
-## Database Schema
-
-### New Tables
-```sql
--- Example table for new feature
-CREATE TABLE feature_table (
-  id UUID DEFAULT gen_random_uuid() PRIMARY KEY,
-  user_id TEXT NOT NULL,
-  data JSONB NOT NULL,
-  created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),
-  updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
-);
-```
-
-### Modified Tables
-- **content_items**: Add new fields if needed
-- **users**: Add new fields if needed
-
-## API Design
-
-### New Endpoints
-- **POST /api/feature**: Create new feature item
-- **GET /api/feature**: List feature items
-- **PUT /api/feature/[id]**: Update feature item
-- **DELETE /api/feature/[id]**: Delete feature item
-
-### Request/Response Examples
-```typescript
-// POST /api/feature
-interface CreateFeatureRequest {
-  title: string;
-  content: string;
-  // ... other fields
-}
-
-interface CreateFeatureResponse {
-  id: string;
-  // ... response fields
-}
-```
-
-## AI Integration
-
-### AI Provider Selection
-- **Primary**: OpenAI (for main processing)
-- **Fallback**: Mock provider (for development)
-- **Future**: Anthropic (for additional capabilities)
-
-### AI Processing Pipeline
-1. **Content Analysis**: Analyze input content
-2. **Feature Extraction**: Extract relevant features
-3. **AI Processing**: Apply AI algorithms
-4. **Result Validation**: Validate AI outputs
-5. **Response Generation**: Format final response
-
-### Cost Considerations
-- **OpenAI API**: ~$0.01-0.10 per request
-- **Gemini API**: ~$0.005-0.05 per request
-- **Expected Volume**: 100-1000 requests/day
-- **Monthly Cost**: $10-100 estimated
-
-## Frontend Components
-
-### New Components
-- **FeatureForm**: Form for creating/editing features
-- **FeatureList**: List view of features
-- **FeatureDetail**: Detailed view of individual feature
-- **FeatureCard**: Card component for feature display
-
-### State Management
-- **Context**: FeatureContext for global state
-- **Hooks**: Custom hooks for data fetching
-- **Local State**: Component-level state management
-
-## Error Handling
-
-### Error Types
-- **Validation Errors**: Input validation failures
-- **AI Errors**: AI provider failures
-- **Network Errors**: API communication failures
-- **Database Errors**: Data persistence failures
-
-### Error Recovery
-- **Retry Logic**: Automatic retry for transient failures
-- **Fallback Strategies**: Alternative approaches when primary fails
-- **User Feedback**: Clear error messages and recovery options
-- **Logging**: Comprehensive error logging and monitoring
-
-## Performance Considerations
-
-### Optimization Strategies
-- **Caching**: Implement appropriate caching strategies
-- **Lazy Loading**: Load components and data on demand
-- **Debouncing**: Prevent excessive API calls
-- **Compression**: Compress API responses
-
-### Monitoring
-- **Response Times**: Track API response times
-- **Error Rates**: Monitor error frequencies
-- **AI Performance**: Track AI accuracy and costs
-- **User Metrics**: Monitor user engagement
-
-## Security Considerations
-
-### Authentication
-- **User Verification**: Verify user identity
-- **Session Management**: Manage user sessions
-- **Token Validation**: Validate authentication tokens
-
-### Authorization
-- **Access Control**: Control feature access
-- **Data Isolation**: Ensure user data isolation
-- **Permission Checks**: Validate user permissions
-
-### Data Protection
-- **Input Validation**: Validate all inputs
-- **Output Sanitization**: Sanitize outputs
-- **Privacy Compliance**: Ensure data privacy
-- **Audit Logging**: Log security-relevant events
-
-## Testing Strategy
-
-### Unit Testing
-- **Component Tests**: Test React components
-- **API Tests**: Test API endpoints
-- **Service Tests**: Test business logic
-- **AI Tests**: Test AI integration
-
-### Integration Testing
-- **End-to-End Tests**: Test complete workflows
-- **API Integration**: Test API interactions
-- **Database Integration**: Test data persistence
-- **External Service Integration**: Test third-party services
-
-### Performance Testing
-- **Load Testing**: Test under expected load
-- **Stress Testing**: Test under high load
-- **AI Performance**: Test AI response times
-- **Database Performance**: Test query performance
-
-## Deployment Plan
-
-### Environment Setup
-- **Development**: Local development environment
-- **Staging**: Pre-production testing environment
-- **Production**: Live production environment
-
-### Deployment Process
-1. **Code Review**: Review all changes
-2. **Testing**: Run comprehensive tests
-3. **Staging Deployment**: Deploy to staging
-4. **Production Deployment**: Deploy to production
-5. **Monitoring**: Monitor deployment health
-
-### Rollback Strategy
-- **Database Rollback**: Rollback database changes
-- **Code Rollback**: Rollback code changes
-- **Configuration Rollback**: Rollback configuration changes
-- **Monitoring**: Monitor rollback success
-
-## Success Metrics
-
-### Technical Metrics
-- **Response Time**: < 2 seconds for API calls
-- **Error Rate**: < 1% error rate
-- **Uptime**: > 99.9% uptime
-- **AI Accuracy**: > 90% accuracy
-
-### User Metrics
-- **Adoption Rate**: % of users using feature
-- **Satisfaction**: User satisfaction scores
-- **Engagement**: Feature usage frequency
-- **Retention**: User retention impact
-
-### Business Metrics
-- **Cost per Operation**: Cost efficiency
-- **Revenue Impact**: Revenue generation
-- **User Growth**: User acquisition impact
-- **Competitive Advantage**: Market positioning
-
-## Risk Mitigation
-
-### Technical Risks
-- **AI Provider Outage**: Implement fallback providers
-- **Database Issues**: Implement backup and recovery
-- **Performance Issues**: Implement monitoring and scaling
-- **Security Vulnerabilities**: Implement security reviews
-
-### Business Risks
-- **User Adoption**: Implement user feedback loops
-- **Cost Overruns**: Implement cost monitoring
-- **Competitive Pressure**: Implement rapid iteration
-- **Regulatory Issues**: Implement compliance monitoring
-
-## Future Enhancements
-
-### Planned Improvements
-- **Advanced AI Features**: Enhanced AI capabilities
-- **Mobile App**: Native mobile application
-- **API Expansion**: Additional API endpoints
-- **Integration**: Third-party integrations
-
-### Research Areas
-- **AI Optimization**: Improve AI accuracy and cost
-- **User Experience**: Enhance user interface
-- **Performance**: Optimize system performance
-- **Scalability**: Improve system scalability
-
-

package/templates/shared/hooks-enabled.json

@@ -1,22 +0,0 @@
-{
-  "schemaVersion": 1,
-  "updatedAt": "2026-01-18T00:00:00Z",
-  "targets": {
-    "claude": {
-      "user-prompt-submit": true,
-      "assistant-response": true,
-      "stop": true,
-      "session-start": true
-    },
-    "cursor": {
-      "enabled": true
-    },
-    "windsurf": {
-      "enabled": true
-    }
-  },
-  "redaction": {
-    "enabled": true,
-    "mode": "safe"
-  }
-}

package/templates/shared/session-words.json

@@ -1,45 +0,0 @@
-{
-  "schemaVersion": 2,
-  "updatedAt": "2026-01-18T00:00:00Z",
-  "adjectives": [
-    "ace", "big", "blu", "coy", "dex",
-    "eco", "fab", "gem", "hex", "ice",
-    "jet", "key", "lux", "max", "neo",
-    "oak", "pop", "rad", "sky", "top",
-    "uno", "vex", "wax", "xen", "zen",
-    "hot", "red", "nox", "sol", "vim",
-    "ash", "dew", "fog", "glo", "ink",
-    "joy", "koi", "lit", "mox", "nix",
-    "orb", "pix", "qix", "rox", "sly",
-    "tek", "ulu", "vox", "wiz", "zap"
-  ],
-  "nouns": [
-    "ant", "bat", "cat", "dog", "elk",
-    "fox", "gnu", "hen", "imp", "jay",
-    "kit", "lex", "moo", "nub", "owl",
-    "pug", "ram", "sun", "tux", "urn",
-    "van", "web", "yak", "zed", "ape",
-    "bee", "cod", "doe", "eel", "fin",
-    "gup", "hog", "ion", "jab", "keg",
-    "log", "mud", "net", "oat", "pod",
-    "rye", "sap", "tar", "vat", "wok",
-    "box", "cub", "dip", "gem", "hub"
-  ],
-  "verbs": [
-    "ask", "bet", "cut", "dig", "eat",
-    "fix", "get", "hit", "jab", "key",
-    "let", "mix", "nap", "opt", "pop",
-    "run", "set", "tap", "use", "vet",
-    "win", "zip", "zap", "add", "bid",
-    "dub", "end", "fly", "gig", "hum",
-    "jog", "lob", "map", "net", "orb",
-    "pay", "rip", "sip", "tag", "vow",
-    "wag", "yap", "bow", "cue", "dip",
-    "fan", "hop", "jam", "nod", "tug"
-  ],
-  "rules": {
-    "format": "{adj}-{noun}-{verb}",
-    "minPerList": 25,
-    "maxPerList": 500
-  }
-}

package/templates/skills/ekkOS_Deep_Recall/Skill.md

@@ -1,282 +0,0 @@
----
-name: ekkOS_Deep_Recall
-description: Deep memory retrieval across sessions and projects. Activate when user says "yesterday", "last week", "remember when", "what did we discuss", "we worked on X before", "bring context from [project]", or asks about past decisions, fixes, or discussions. Combines time-based recall with semantic search.
-allowed-tools:
-  - mcp__ekkos-memory__ekkOS_Recall
-  - mcp__ekkos-memory__ekkOS_Search
-  - mcp__ekkos-memory__ekkOS_Context
----
-
-# ekkOS_Deep_Recall
-
-You are augmented with **ekkOS_ memory** - and you can recall conversations, decisions, and solutions from any point in history.
-
-## Why This Skill Exists
-
-Users reference past work in many ways:
-- By time: "yesterday", "last week", "a month ago"
-- By topic: "remember when we fixed the auth bug?"
-- By project: "bring context from the API project"
-- By outcome: "what solution did we use for caching?"
-
-This skill searches across all memory layers to find what they need.
-
-## When To Activate
-
-| Trigger | Action |
-|---------|--------|
-| "yesterday", "last week", "recently" | Time-based recall |
-| "remember when we...", "we discussed..." | Semantic search |
-| "what did we decide about X" | Decision search |
-| "we fixed this before" | Solution/pattern search |
-| "bring context from [project]" | Cross-project recall |
-| "what do you know about X" | Full memory search |
-
-## Instructions
-
-### For Time-Based Queries
-
-Parse the time reference and call recall:
-
-```
-"yesterday"        → ekkOS_Recall({ days_ago: 1 })
-"last week"        → ekkOS_Recall({ days_ago: 7 })
-"a few days ago"   → ekkOS_Recall({ days_ago: 3 })
-"last month"       → ekkOS_Recall({ days_ago: 30 })
-```
-
-Options:
-```javascript
-ekkOS_Recall({
-  days_ago: 1,                    // How far back
-  limit: 20,                      // Max results
-  llm_summarize: true,            // AI summary
-  include_patterns: true,         // Include forged patterns
-  include_file_changes: true,     // Include files touched
-  group_by_sessions: true         // Group by session
-})
-```
-
-### For Topic-Based Queries
-
-Use semantic search:
-
-```javascript
-ekkOS_Search({
-  query: "authentication token refresh implementation",
-  sources: ["episodic", "patterns", "semantic"]
-})
-```
-
-### For Decision Queries
-
-Search with decision extraction:
-
-```javascript
-ekkOS_Recall({
-  semantic_query: "decision about caching strategy",
-  extract_decisions: true
-})
-```
-
-### For Cross-Project Context
-
-Search codebase layer:
-
-```javascript
-ekkOS_Search({
-  query: "rate limiting implementation",
-  sources: ["codebase", "patterns"]
-})
-```
-
-## Response Format
-
-### Time-Based Results
-
-```
-🧠 **Yesterday's Sessions**
-
-**Session 1** (10:30 AM - 12:15 PM)
-- Working on: CI/CD pipeline setup
-- Completed: GitHub Actions configuration
-- Left off: Fixing failing auth test
-
-**Session 2** (3:00 PM - 5:00 PM)
-- Working on: User service refactoring
-- Decision: Use Redis over Memcached
-- Files: src/services/user.ts, src/cache/redis.ts
-
----
-Would you like to continue any of these?
-```
-
-### Topic-Based Results
-
-```
-🧠 **Found: Caching Bug Fix** (2 weeks ago)
-
-**The Problem**: Cache not invalidating on updates
-**Root Cause**: Object reference used as key instead of ID
-**Solution**: Changed to immutable entity ID as cache key
-
-**Pattern Forged**: "Always use immutable IDs as cache keys"
-Confidence: 0.95 | Applied 12 times successfully
-
-Want me to apply this pattern to your current issue?
-```
-
-### Decision Results
-
-```
-🧠 **Decision: Caching Strategy** (January 5th)
-
-**Context**: Choosing between Redis and Memcached
-**Decision**: Redis
-**Reasons**:
-- Persistence for cache warmth
-- Pub/sub for invalidation
-- Lua scripting for atomic operations
-
-**Who decided**: You, after weighing trade-offs
-**Outcome**: Working well, no regrets mentioned
-
-Is this the decision you were looking for?
-```
-
-## Example Scenarios
-
-### Scenario 1: Yesterday's Work
-```
-User: "What were we working on yesterday?"
-
-You: ekkOS_Recall({ days_ago: 1, group_by_sessions: true })
-
-     🧠 Yesterday (January 10th):
-
-     **Session 1** (10:30 AM)
-     - API rate limiting implementation
-     - Sliding window algorithm complete
-     - Left off: Edge case testing
-
-     **Session 2** (3:00 PM)
-     - Dashboard component refactoring
-     - Split into smaller components
-     - Forged: "Component composition pattern"
-
-     Continue where you left off?
-```
-
-### Scenario 2: Remember When
-```
-User: "Remember when we fixed that weird auth bug?"
-
-You: ekkOS_Search({
-       query: "authentication bug fix",
-       sources: ["episodic", "patterns"]
-     })
-
-     🧠 Found it! (3 weeks ago)
-
-     **Bug**: JWT tokens expiring early
-     **Cause**: Timezone mismatch in expiry calculation
-     **Fix**: Use UTC consistently across all time ops
-
-     Pattern: "auth-jwt-timezone-fix"
-     Applied successfully 5 times since
-
-     Is this what you were thinking of?
-```
-
-### Scenario 3: Past Decision
-```
-User: "What did we decide about the database schema?"
-
-You: ekkOS_Recall({
-       semantic_query: "database schema decision",
-       extract_decisions: true
-     })
-
-     🧠 **Schema Decisions** (found 3)
-
-     1. **Users table** (Jan 5)
-        - Soft deletes with deleted_at
-        - UUID primary keys
-        - Email unique constraint
-
-     2. **Orders table** (Jan 8)
-        - Denormalized totals for performance
-        - Status enum, not string
-        - Foreign key to users
-
-     3. **Products table** (Jan 10)
-        - JSON column for attributes
-        - Full-text search enabled
-
-     Want details on any of these?
-```
-
-### Scenario 4: Cross-Project
-```
-User: "How did we implement rate limiting in the API project?"
-
-You: ekkOS_Search({
-       query: "rate limiting implementation",
-       sources: ["codebase", "patterns"]
-     })
-
-     🧠 **Rate Limiting** (from api-project)
-
-     **Approach**: Token bucket algorithm
-     **Storage**: Redis with TTL
-     **Limits**: 100 req/min per API key
-
-     **Files**:
-     - src/middleware/rateLimit.ts
-     - src/redis/tokenBucket.ts
-
-     **Pattern**: "rate-limit-token-bucket"
-     Works in: api-project, dashboard-api
-
-     Want me to apply this pattern here?
-```
-
-## When No Results Found
-
-```
-🧠 I couldn't find anything about [topic].
-
-Possible reasons:
-- We haven't discussed this before
-- It was before ekkOS was set up
-- The search terms didn't match
-
-Try:
-1. Different keywords?
-2. Broader time range?
-3. Check a specific project?
-```
-
-## Combining with Current Context
-
-After recall, offer to load full context:
-
-```
-"Would you like me to load the full session context?
- This brings back all the details from that conversation."
-
-→ ekkOS_Context({ task: "continue X from recalled session" })
-```
-
-## Success Metrics
-
-You're using this skill well when:
-- Time references trigger automatic recall
-- Topic searches find relevant past work
-- Decisions are surfaced with context
-- Users feel like you "remember everything"
-- Cross-project patterns are reusable
-
----
-
-**Mantra**: The past is never lost - search for it, find it, use it.