Menu
Historical record of expert tips and learnings that have been integrated into the plugin skills. Consult this when patterns emerge or to understand the evolution of knowledge.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | learnings-log |
| description | Historical record of expert tips and learnings that have been integrated into the plugin skills. Consult this when patterns emerge or to understand the evolution of knowledge. |
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.
Each learning entry should include:
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"
data-modeling/SKILL.md - Section: "Relation & Lookup Pattern"
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.
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"
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.
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"
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.
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"
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.
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"
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/actions that are accidentally deleted. Provides a safety net during browser automation. Critical for recovering from automation errors without starting over.
Context: Task required adding a button to send an email with location information. Initially selected "Compose email" action, but this would open the user's email app rather than send programmatically.
Tip Provided:
"Send email uses Glide's built in email service to send emails. Compose email opens the users default email app to send an email. For most cases we want to use the Send Email action unless the user specifically asks to open their email app."
Skills Updated:
layout/SKILL.md - Section: "Actions"
Key Learning: "Send Email" and "Compose Email" are two distinct actions with different behaviors - Send Email uses Glide's service to send programmatically (recommended default), while Compose Email opens the user's email app (use only when explicitly requested).
Impact: Prevents confusion about which email action to use. Ensures automated email features work correctly without requiring user interaction. Makes the distinction clear between programmatic sending and manual composition.
This learnings log was created as part of the self-learning /tip command feature.
Purpose: Enable the plugin to learn from expert feedback and continuously improve its knowledge base.
Context: Builder agent needed to add a 'created date' column to the locations table. Manual column creation via UI clicks can be slow and less reliable.
Tip Provided:
"Whenever you need to add a column it will always need done via browser automation. You can navigate to a table and then use the keyboard shortcut CMD+SHIFT+ENTER to create a new column. This is much faster"
Skills Updated:
data-modeling/SKILL.md - Section: "Creating Columns via UI"
glide/SKILL.md - Section: "Data Editor > Adding Columns"
glide/SKILL.md - Section: "Browser Automation Tips > Keyboard shortcuts"
Key Learning: CMD+SHIFT+ENTER is the fastest and most reliable way to add columns in Glide when using browser automation.
Impact: Significantly speeds up column creation workflows. Makes automation more efficient and reduces reliance on fragile UI click sequences. This is especially valuable when adding multiple columns or when building apps with complex data models.
When you update skills based on a tip, also add an entry to this log:
### YYYY-MM-DD: [Brief Title]
**Context**: [What was stuck or going wrong]
**Tip Provided**:
> [The user's tip in their own words]
**Skills Updated**:
- `skill-name/SKILL.md` - Section: [section name]
- Added: [brief description of what was added]
**Key Learning**: [One-sentence summary of the core insight]
**Impact**: [Why this matters / what problem this prevents]
---
Periodically review this log to identify:
### 2025-01-15: Emoji Picker Navigation
**Context**: Builder agent was stuck trying to select an app icon, kept failing to click the right emoji from the category view.
**Tip Provided**:
> "Don't browse the emoji categories. Always use the search box - type the emoji name like 'rocket' or 'checkmark' and click the result. It's much faster and more reliable."
**Skills Updated**:
- `glide/SKILL.md` - Section: "Creating New App"
- Added: Detailed guidance on emoji picker search workflow
- Added: Note about avoiding category browsing
- `layout/SKILL.md` - Section: "UI Navigation Patterns"
- Added: General emoji picker usage pattern
**Key Learning**: Glide's emoji picker is optimized for search, not browsing - category navigation is unreliable for automation.
**Impact**: Prevents future failures when setting app icons or using emoji fields. Makes icon selection deterministic.
---
As tips accumulate, track:
The /tip command automatically:
Consider adding:
Audit Glide apps for performance issues and optimization opportunities. Use when analyzing app performance, identifying bottlenecks in data structure or layout, or providing recommendations for improving app speed and user experience. Automatically triggered when user provides a Glide app URL for audit, including read-only support-mode URLs of the form https://go.glideapps.com/support/{uuid}. Can also produce an optional plain-language, customer-facing version of the report on request, for sharing directly with the customer who reported the issue.
Get detailed explanations of Glide features - computed columns, workflows, components, data modeling, AI features, and more
Use the Glide API for programmatic data operations - REST API v2 and @glideapps/tables npm package. Use when importing data, bulk operations, automating data sync, or building integrations with Glide tables.
Create computed columns in Glide - Math, If-Then-Else, Relations, Rollups, Lookups, Templates. Use when adding calculations, formulas, lookups, or linking tables with relations.
Design Glide data models - tables, columns, column types, and calculation architecture. Use when creating tables, designing data structures, choosing column types, or planning relationships.
**The primary skill for building Glide apps.** Covers the full workflow, agent coordination, and browser automation. Use when building, creating, or modifying any Glide app. Read this first for any Glide project.