feature-analyzer

Files (1)

• SKILL.md

SKILL.md (first lines)

## Purpose

Transform into a systematic feature analysis agent that:
1. **Extracts** functional capabilities from external codebases
2. **Maps** features to abstract categories (not implementation details)
3. **Compares** against Lattice's existing capabilities
4. **Identifies** gaps and opportunities
5. **Proposes** integration strategies (functional, not copied code)

## Core Principle: Functional Equivalence, Not Code Copying

**CRITICAL:** This skill focuses on WHAT systems do, not HOW they're named or structured.

```
ANALYZE: "This system has X capability"
NOT:     "Copy class FooBarManager from external project"

PROPOSE: "Lattice needs capability to transform paths along splines"
NOT:     "Add PathAlongSplineModifier like external project"
```

Trade dress protection: Extract functional requirements only. Never copy:
- Class/function names
- Variable naming conventions
- API surface structure
- Marketing terminology

## Analysis Protocol

### Phase 1: External Project Deep Dive

For each external project, extract:

```yaml
project_analysis:
  # 1. Core Capabilities
  capabilities:
    - category: animation
      features:
        - name: "Keyframe interpolation"
          description: "Interpolate between keyframes with various easing"
          parameters: [easing_type, tension, overshoot]
        - name: "Path-based animation"
          description: "Animate objects along bezier paths"
          parameters: [path_data, orientation, timing]

  # 2. Data Structures (abstract)
  data_model:
    - entity: "Composition"
      attributes: [dimensions, duration, frame_rate, layers]
    - entity: "Layer"
      attributes: [transform, timing, content, effects]

  # 3. Algorithms (functional description)
  algorithms:
    - name: "Curve evaluation"
      purpose: "Sample bezier curves at arbitrary t values"
      inputs: [control_points, parameter_t]
      outputs: [point_on_curve]

  # 4. Integration Points
  interfaces:
    - input_formats: [json, binary]
    - output_formats: [rendered_video, json_export]
    - api_patterns: [sync, async, streaming]
```

### Phase 2: Lattice Capability Mapping

Map extracted features to Lattice's current system:

```yaml
lattice_mapping:
  # Types (Lean4/PureScript)
  types_location: lattice-core/lean/Lattice/**/*.lean

  # Services (Implementation)
  services_location: lattice-core/purescript/src/Lattice/Services/**/*.purs

  # UI Components
  ui_location: ui/src/components/**/*.vue

  # Engine
  engine_location: ui/src/engine/**/*.ts
```

### Phase 3: Gap Analysis Report

Generate structured comparison:

```markdown
## Feature Comparison: [External Project] vs Lattice

### Category: Animation

| Feature | External | Lattice | Gap |
|---------|----------|---------|-----|
| Keyframe interpolation | Yes (bezier, spring) | Yes (bezier) | Spring physics |
| Path animation | Yes | Yes | Parity |
| Expression system | Yes (JS-based) | Yes (safe DSL) | Lattice better |

### Category: Effects

| Feature | External | Lattice | Gap |
|---------|----------|---------|-----|
| Blur variants | 5 types | 5 types | Parity |
| Distortion | 12 types | 8 types | +4 needed |

### Missing Features (Prioritized)
1. **Spring physics** - High value for natural motion
2. **Morphing** - Medium value for shape transitions
3. **Audio waveform** - Low value, niche use case
```

### Phase 4: Integration Proposals

For each gap, propose functional integration:

```yaml

From justinfleek/ComfyUI-Lattice-Compositor, MIT.

More from justinfleek/ComfyUI-Lattice-Compositor