learnings-log

# Learnings Log

This skill tracks all successful expert tips that have been integrated into the plugin's knowledge base. Each entry records what was learned and which skills were updated.

## Purpose

- **Historical record**: See what tips have been provided
- **Pattern detection**: Identify common issues or knowledge gaps
- **Validation**: Verify learnings are being properly integrated
- **Evolution tracking**: Understand how the plugin's knowledge grows

## Log Format

Each learning entry should include:
- **Date**: When the tip was provided
- **Context**: What was stuck or going wrong
- **Tip**: The expert guidance provided
- **Skills Updated**: Which skill files were modified
- **Key Learning**: Summary of what was learned

## Learning Entries

### 2026-01-06: Rollups Should Operate on Relations, Not Whole Tables

**Context**: Attempting to add rollup columns to a CRM app to show insights like count of contacts per company and sum of deal amounts. Was about to create rollups that would operate directly on entire tables, which would have shown global totals instead of per-company totals.

**Tip Provided**:
> "Rollups should mainly be used in coordination with a relation or query column and rarely the whole table. For example using a rollup and selecting a table and a column in that table will count the number of rows in that table. If you did that against a relation it would count the number of related items it found which is much more useful in many cases. Ex Orders > Order items. If i related from the order to order items, i could then count the number of order items in that order versus counting all order items in the table."

**Skills Updated**:
- `computed-columns/SKILL.md` - Section: "Rollup Columns"
  - Added: "CRITICAL CONCEPT" callout that rollups should operate on Relation columns
  - Added: Explanation of why (rollups on relations auto-filter to related rows)
  - Added: "Why Use Relations with Rollups" section with pattern diagram
  - Added: Example s