learnings-log

What this skill does

# 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 showing WRONG vs RIGHT approach for Order Items counting
  - Added: Complete CRM example matching the user's actual use case (Companies → Contacts/Deals)
  - Added: "When to Use Rollup on Whole Table" section (rare cases like dashboards)
  - Updated: Setup steps to emphasize creating Relation first
  - Added: Common Rollup Patterns table with real-world examples
- `data-modeling/SKILL.md` - Section: "Relation & Lookup Pattern"
  - Added: IMPORTANT note that rollups should operate on relations, not tables
  - Added: Cross-reference to computed-columns skill for detailed guidance

**Key Learning**: Rollups should almost always operate on a Relation column, not directly on a table. Rollups on relations automatically filter to only related rows, while rollups on entire tables aggregate ALL rows (rarely useful).

**Impact**: Prevents a critical common mistake that would cause rollups to show meaningless global totals instead of per-row aggregations. This is especially important in CRM apps, order systems, and any app with one-to-many relationships. Makes the Relation → Rollup pattern explicit and teachable.

---

### 2025-12-31: Action Button Ordering and Multiple Actions

**Context**: Task required adding an email button to send location information. The Edit button was appearing as the primary (leftmost) button, and the new Email Info button was secondary. Needed to understand how action ordering works in Glide.

**Tip Provided**:
> "In 'Actions' anywhere in Glide the top 'action' is the left most button. So in the current app we have Edit at the top and edit is the main thing seen. If we don't need to be able to edit that page, we should just remove this button. Alternatively, you can move edit below another action to get the other action to appear first."

**Skills Updated**:
- `layout/SKILL.md` - Section: "Actions"
  - Created: New "Action Button Ordering" subsection at top of Actions section
  - Added: Core rule - top action in list = leftmost button in UI
  - Added: Visual example showing list order vs UI display order
  - Added: Step-by-step instructions for reordering actions via drag-and-drop
  - Added: Guidance on making an action primary (move to top or remove others)
  - Added: Common use case about removing/reordering default Edit action

**Key Learning**: In Glide's actions list, the top action appears as the leftmost button in the UI. To control button prominence, drag actions to reorder them or remove unwanted actions.

**Impact**: Prevents confusion about why buttons appear in unexpected order. Makes it clear how to prioritize custom actions over default actions like Edit. Essential for creating intuitive UIs with multiple action buttons.

---

### 2025-12-31: Send Email Action - Recipient Field Configuration

**Context**: Send Email action wasn't working because the To, Cc, and Bcc fields weren't configured correctly for the use case of emailing location information to the logged-in user.

**Tip Provided**:
> "Send Email action isn't working because the to, cc, and bcc field aren't configured correctly. For this case, use the user's email address as the To field and clear the others"

**Skills Updated**:
- `layout/SKILL.md` - Section: "Email Actions"
  - Added: New "Configuring Send Email action" subsection
  - Added: Detailed guidance for each recipient field (To, Cc, Bcc)
  - Added: How to send to logged-in user (User / Email binding)
  - Added: How to send to specific person (email column from data)
  - Added: Guidance on when to clear optional fields (Cc/Bcc)
  - Added: Common mistake note about leaving fields configured unnecessarily
  - Added: Complete example for emailing to logged-in user with cleared Cc/Bcc

**Key Learning**: Send Email actions require careful configuration of recipient fields. For sending to the logged-in user, use `User / Email` for the To field and clear Cc/Bcc if not needed.

**Impact**: Prevents Send Email actions from failing due to misconfigured recipient fields. Clarifies the difference between required (To) and optional (Cc/Bcc) fields. Makes it clear how to bind to the logged-in user's email address.

---

### 2025-12-31: Reordering Actions via Drag-and-Drop

**Context**: Needed to make the Email Info action the primary button by moving it above the Edit action in the actions list. Initial attempt didn't work because the method wasn't clear.

**Tip Provided**:
> "You still haven't ordered the actions correctly. You need to drag Email Info action above the 'Add Action' piece"

**Skills Updated**:
- `layout/SKILL.md` - Section: "Action Button Ordering"
  - Added: Specific instruction to drag actions to reorder them
  - Added: Note that actions can be moved above or below each other
  - Added: Clarification that UI button order updates automatically

**Key Learning**: To reorder actions in Glide, click and drag the action in the actions list to move it above or below other actions.

**Impact**: Makes the reordering mechanism explicit. Prevents confusion about how to actually change action order once you understand the top-to-bottom = left-to-right rule.

---

### 2025-12-31: Using CMD+Z to Undo Mistakes

**Context**: Accidentally deleted the Email Info action while trying to reorder actions. Needed to quickly restore it without rebuilding.

**Tip Provided**:
> "Stop you just deleted the email action, quick CMD+Z to get it back"

**Skills Updated**:
- `glide/SKILL.md` - Section: "Browser Automation Tips > Keyboard shortcuts"
  - Added: CMD+Z / CTRL+Z to keyboard shortcuts list
  - Created: New "Undo mistakes" subsection
  - Added: Explanation of Glide's undo functionality
  - Added: Common scenarios where undo is useful (deleted action, removed component, changed setting)
  - Added: Important note about undo only working for recent actions in current session

**Key Learning**: Glide Builder supports standard undo functionality with CMD+Z (macOS) or CTRL+Z (Windows) to revert recent changes.

**Impact**: Prevents need to rebuild components/act