Pattern Detection

Kyew can analyze your memories to detect repeated patterns - approaches you use frequently that could be codified as skills.

How Pattern Detection Works

The analyze_patterns tool examines your memories looking for:

• Similar observations - Memories about the same topic
• Consistent outcomes - Repeated successful approaches
• Domain clustering - Related work in the same area

Confidence Scoring

Patterns are scored by confidence (0-1):

• 0.9+ - Very strong pattern, highly recommended
• 0.7-0.9 - Good pattern, worth reviewing
• 0.5-0.7 - Potential pattern, needs more data
• <0.5 - Weak pattern, probably coincidental

Using Pattern Analysis

"analyze patterns in the cloudflare domain"

{
  "patterns": [
    {
      "description": "CORS debugging approach",
      "memory_count": 4,
      "confidence": 0.88,
      "memory_ids": ["mem-1", "mem-2", "mem-3", "mem-4"],
      "suggested_skill_name": "Cloudflare CORS Debugging"
    }
  ]
}

Filter by Time

"analyze patterns from the last 30 days"

Limit Results

"show top 5 patterns in testing domain"

Pattern to Skill Workflow

1. Accumulate memories - Store observations as you work
2. Analyze patterns - Run pattern detection periodically
3. Review patterns - Check if detected patterns are valid
4. Generate skills - Create skills from strong patterns
5. Approve skills - Review and activate generated skills

Requirements

For reliable pattern detection:

• Minimum 3 memories - Need multiple data points
• Consistent domains - Use the same domain names
• Specific observations - Vague memories don't cluster well

Best Practices

Store Memories Consistently

# Good - consistent domain and detail
remember in cloudflare domain: Fixed CORS by adding header
remember in cloudflare domain: CORS issue resolved with Access-Control-*
remember in cloudflare domain: Workers CORS needed explicit headers

# Less effective - inconsistent
remember: Fixed CORS
remember in cf domain: headers issue
remember: something with workers

Review Before Generating

Not every pattern should become a skill. Review patterns for:

• Is this actually a consistent approach?
• Would this help in future situations?
• Is it specific enough to be useful?

Run Analysis Periodically

As you accumulate memories, run analysis to surface patterns:

# After a week of work
analyze patterns from last 7 days

# After finishing a project
analyze patterns in project-name domain