@ekkos/cli 1.3.1 → 1.3.5

package/templates/rules/00-hooks-contract.mdc

@@ -1,89 +0,0 @@
----
-priority: 100
-globs: ["**/*"]
-alwaysApply: true
----
-
-# 🔒 Cursor Hooks Contract
-
-⚠️ **MANDATORY**: Hooks run automatically - you don't call them manually
-
-## Hook Architecture
-
-**Dumb Hooks, Smart Backend** - Hooks just capture data, backend does analysis
-
-### user-prompt-submit.sh (Runs BEFORE Response)
-
-**Triggers**: When user sends a message
-**Does**:
-
-- Captures start time
-- Retrieves patterns from MCP gateway (automatic)
-- Displays patterns to user
-- Saves patterns to `.cursor/state/` for badge
-
-**You see**:
-
-```
-🧠 ekkOS™_Retrieving [18ms]
-✓ 3 patterns loaded from memory
-```
-
-### stop.sh (Runs AFTER Response)
-
-**Triggers**: When your response completes
-**Does**:
-
-- Captures conversation to memory API
-- Generates badge with metrics
-- Triggers async analysis (pattern detection, success judgment)
-- Displays badge at end
-
-**You see**:
-
-```
-[ekkOS_CAPTURE] ✓ Saved (ID: abc123...)
-[reflex:uuid] badge
-```
-
-## What You Do
-
-**✅ DO**:
-
-- Display `_ekkos_stream_message` when present in tool responses
-- Call `forge_insight` when solving problems
-- Show ekkOS branded messages
-
-**❌ DON'T**:
-
-- Manually call capture scripts (hooks do this)
-- Generate badges yourself (hooks do this)
-- Worry about pattern retrieval (MCP gateway does this)
-
-## Hook Flow
-
-```
-User sends message
-    ↓
-user-prompt-submit.sh runs
-    ↓
-Patterns retrieved and displayed
-    ↓
-You respond (using patterns)
-    ↓
-stop.sh runs
-    ↓
-Conversation captured + badge generated
-```
-
-## Trust the Hooks
-
-Hooks are:
-
-- ✅ Fully portable (POSIX-compliant)
-- ✅ Bulletproof (fallbacks for missing tools)
-- ✅ Fast (non-blocking, cloud-first)
-- ✅ Automatic (you never call them)
-
-**Your job**: Use the patterns hooks provide, forge insights when you solve problems
-

package/templates/rules/30-ekkos-core.mdc

@@ -1,188 +0,0 @@
----
-priority: 100
-globs: ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"]
----
-
-# 🧠 ekkOS™ Memory Integration [CRITICAL]
-
-## Golden Loop Enforcement
-
-⚠️ MANDATORY WORKFLOW - NO EXCEPTIONS
-
-### Phase 1: RETRIEVE (⚠️ CURSOR: YOU MUST DO THIS)
-
-🔴 **FIRST THING EVERY RESPONSE**: Call `ekkOS_Search` with the user's query!
-
-```typescript
-// ALWAYS call this BEFORE doing anything else
-mcp__ekkos-memory__ekkOS_Search({
-  query: "<user's question or task>",
-  limit: 5
-})
-```
-
-Then check response for: `_ekkos_patterns`, `_ekkos_stream_message`
-
-**Why?** Cursor has no hooks. Claude Code auto-retrieves via hooks - you don't.
-You MUST manually retrieve or the Golden Loop breaks.
-
-### Phase 2: APPLY (Use Retrieved Patterns)
-
-When patterns found → Apply them (PROVEN solutions, not suggestions)
-Output: `[ekkOS_APPLY] Using pattern: "Pattern Name"`
-
-### Phase 3: MEASURE (Track Outcomes)
-
-Pattern worked? → success | Pattern failed? → failure
-Output: `[ekkOS_MEASURE] Pattern "X" outcome: success/failure`
-
-### Phase 4: LEARN (Forge New Patterns)
-
-🔴 MANDATORY: Call `forge_insight` when you solve ANY problem
-
-**When to forge**:
-
-- Fixed bug (non-obvious) → forge
-- Found better approach → forge
-- Discovered gotcha/pitfall → forge
-- User corrected you → forge
-- Solved problem (>1 attempt) → forge
-
-**Tool call**:
-
-```typescript
-mcp__ekkos-memory__forge_insight({
-  title: "Clear Title",
-  problem: "What failed?",
-  solution: "How you fixed it",
-  tags: ["tech", "tags"],
-});
-```
-
-Output: `[ekkOS_LEARN] Forged: "Pattern Title"`
-
-### Phase 5: CAPTURE (Cursor: Limited)
-
-⚠️ **Cursor limitation**: No automatic capture like Claude Code hooks.
-Conversations are captured when MCP tools are called (search_memory, forge_insight).
-For full capture, use Claude Code or the ekkOS dashboard.
-
-## MCP Tools (31 Total - YOU call these)
-
-### 🔴 MANDATORY - Use Proactively
-
-| Tool | Trigger | Description |
-|------|---------|-------------|
-| `ekkOS_Search` | Before ANY technical question | Search all 11 memory layers |
-| `ekkOS_Forge` | When you fix bug, learn, get corrected | Create pattern from solution |
-| `ekkOS_Directive` | User says "always/never/prefer/avoid" | Create MUST/NEVER/PREFER/AVOID rules |
-| `ekkOS_Outcome` | Pattern worked or failed | Track success/failure |
-| `ekkOS_Detect` | After responding | Auto-detect patterns used |
-| `ekkOS_Summary` | Show MCP activity | Get activity summary |
-| `ekkOS_Conflict` | Before destructive action | Check for conflicts |
-| `ekkOS_Reflect` | Analyze response quality | Find improvement opportunities |
-
-### 📚 Recall & Context
-
-| Tool | Description |
-|------|-------------|
-| `ekkOS_Recall` | "What did we discuss yesterday?" |
-| `ekkOS_Context` | Get task-specific context |
-| `ekkOS_Codebase` | Find code patterns in project |
-| `ekkOS_Capture` | Manual event capture |
-| `ekkOS_Track` | Track pattern application |
-| `ekkOS_Stats` | Memory layer statistics |
-
-### 📊 Schema Awareness
-
-| Tool | Description |
-|------|-------------|
-| `ekkOS_IndexSchema` | Index database schemas (Supabase/Prisma/TS) |
-| `ekkOS_GetSchema` | Get schema for a specific table/type |
-
-### 📋 Plan Management
-
-| Tool | Description |
-|------|-------------|
-| `ekkOS_Plan` | Create structured plan |
-| `ekkOS_Plans` | List user's plans |
-| `ekkOS_PlanStatus` | Change plan state |
-| `ekkOS_PlanStep` | Mark step complete |
-| `ekkOS_Generate` | AI-generate plan |
-| `ekkOS_SaveTemplate` | Save as reusable template |
-| `ekkOS_Templates` | List templates |
-| `ekkOS_FromTemplate` | Create from template |
-
-### 🔐 Secrets Management
-
-| Tool | Description |
-|------|-------------|
-| `ekkOS_StoreSecret` | Encrypt and store credentials |
-| `ekkOS_GetSecret` | Retrieve and decrypt |
-| `ekkOS_ListSecrets` | List metadata (no values) |
-| `ekkOS_DeleteSecret` | Permanently delete |
-| `ekkOS_RotateSecret` | Update with new value |
-
-### 💾 Portability
-
-| Tool | Description |
-|------|-------------|
-| `ekkOS_Export` | Backup patterns, directives, plans |
-| `ekkOS_Import` | Restore from backup |
-
-## Proactive Tool Triggers
-
-### Always Use `ekkOS_Search` When:
-- User asks technical question
-- User mentions past discussion
-- Topic involves architecture, config, debugging
-- You're about to make a decision
-
-### Always Use `ekkOS_Forge` When:
-- Fixed bug (especially non-obvious)
-- Discovered better approach
-- Found pitfall or gotcha
-- User corrected you
-- Made architectural decision
-- Something DIDN'T work (anti-pattern)
-
-### Always Use `ekkOS_Directive` When:
-- User says "always..." → MUST
-- User says "never..." → NEVER
-- User says "I prefer..." → PREFER
-- User says "don't..." → AVOID
-
-### Always Use `ekkOS_Conflict` When:
-- About to delete files/data
-- About to deploy to production
-- About to modify config files
-
-## Enforcement
-
-⚠️ Violating Golden Loop = System failure
-Every conversation MUST follow: RETRIEVE → APPLY → MEASURE → LEARN → CAPTURE
-
----
-
-## 🔴 MANDATORY RESPONSE FORMAT (NO EXCEPTIONS)
-
-**Every response MUST end with a timestamp footer:**
-
-```
----
-🧠 **ekkOS_™** · 📅 YYYY-MM-DD H:MM AM/PM TZ
-```
-
-**Example:**
-```
----
-🧠 **ekkOS_™** · 📅 2025-12-08 2:30 PM PST
-```
-
-**Why this matters:**
-- Timestamps track when patterns were applied
-- 3-Judge evaluations need temporal context
-- Future agents can trace learning timeline
-- Golden Loop metrics require time-based correlation
-
-**⚠️ MISSING TIMESTAMP = INCOMPLETE LOOP = SYSTEM DEGRADATION**

package/templates/rules/31-ekkos-messages.mdc

@@ -1,78 +0,0 @@
----
-priority: 100
-globs: ["**/*"]
----
-
-# ekkOS™ Branded Message Templates
-
-## Stream Message Fields (Display All Present)
-
-```
-_ekkos_stream_message     → Display FIRST (🧠 Retrieving/🔄 Applying/✅ Learned)
-_ekkos_learning_message   → Display AFTER solution (🔥 Learning - pattern detected)
-_ekkos_session_summary    → Display AT END (📊 Summary at turns 5/10/20/50)
-```
-
-## Message Examples
-
-### Before Response:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🧠 ekkOS™_Retrieving [18ms]
-✓ 3 patterns loaded from memory
-  • "Pattern Name" (94% success, 12 uses)
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### When Learning:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🔥 ekkOS™_Learning
-New pattern detected: "Title"
-Confidence: 60% (forming)
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### When Pattern Saved:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-✅ ekkOS™_Learned
-Pattern saved: "Title"
-Confidence: 85% | Success: 100%
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### When Reusing:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🔄 ekkOS™_Applying
-Using pattern from 2 messages ago
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### Session Summary:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📊 ekkOS™_Session_Summary
-Memory Activity:
-  Retrieved: 5 patterns
-  Applied: 3 patterns
-  Learned: 2 new patterns
-  Confidence: +8% overall
-
-Your AI is getting smarter.
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-## Requirements
-
-- ALWAYS use ekkOS™ branding (with ™)
-- ALWAYS show retrieval before response
-- ALWAYS show learning when it happens
-- Keep messages concise but visible
-

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.