**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.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
**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.
Glide App Building
Start here when building a Glide app. This skill covers the overall workflow, agent coordination, and technical details for browser automation.
Build Workflow Summary
Clarify use case - Understand what the user wants
Create app first - Get browser auth done early (blank app)
Get API key - Go to Data Editor, retrieve token from Users table (before spawning data agents)
Analyze file (if provided) - Use file-analysis agent
Create tables via API - Use data agent (faster than UI, in parallel)
Build screens - Use build agent for Playwright automation (in parallel)
Design review - Apply design skill to evaluate and improve screens
QA verification - Use qa agent to verify features actually work
Finalize - Access settings, testing, publish
Agents
Agent
Purpose
When to Use
build
Browser automation via Playwright
Creating apps, adding screens, configuring UI
file-analysis
Analyze spreadsheets/data files
User provides a file to build from
data
Glide API operations
Creating tables, importing data, bulk operations
design-review
Critique screens for design quality
After building screens, to improve component choices and layouts
qa
Verify features actually work
Before telling user the app is ready
app-research
Explore and document existing apps
Understanding an app's structure, answering questions about it
Parallel Builds (Multi-Browser) - Maximize Speed
The plugin supports 6 concurrent browser sessions. Browser automation is slow, so parallelize aggressively.
Parallel Strategy for New Apps
Phase 1: Setup (Sequential)
User provides use case
Create blank app (browser 1)
Go to Data Editor and retrieve API key immediately
Click "Data" tab in Glide Builder
Open Users table (or any existing table)
Click "Show API"
Copy the secret token
Store in .glide/config.json under apiKey
Do this BEFORE spawning data agents - prevents multiple agents trying to get the key in parallel
Phase 2: Data Creation (Highly Parallel)
Spawn N data agents in parallel to create all tables (up to 6 concurrent)
Each agent creates and links one table to the app with real or sample data
Example: "Create the Tasks table using browser 1, create the Projects table using browser 2, create the Users table using browser 3"
WAIT for all tables to exist - screens cannot be built without their backing tables
Phase 3: Screen Building (Highly Parallel)
Once all tables exist, spawn up to 6 build agents in parallel
Each agent builds screens for one data table (collection + detail view)
Can start immediately after Phase 2 completes
Example: "Build screens for Tasks using browser 1, build screens for Projects using browser 2, build screens for Users using browser 3"
Agents design collections, detail views, and forms independently
Phase 4: Design Review (One Screen at a Time)
Review ONE screen at a time, not the whole app (much more efficient)
Reuse the same browser from build agents (alternate between building and reviewing)
As each build agent finishes a screen, spawn design-review for that screen only
Example workflow:
Builder finishes Tasks screen on browser 1
Design-review agent reviews Tasks using browser 1 (while other builders continue on browsers 2-6)
Get feedback, pass to builder
Builder implements feedback on Tasks (browser 1)
Meanwhile, another builder finishes Projects on browser 2
Design-review reviews Projects on browser 2
Keep design review focused on one screen at a time for speed
Phase 5: Implement Feedback (Parallel)
Spawn build agents to apply design improvements (up to 6)
Different agents apply feedback to different screens simultaneously
Example: "Implement design feedback for Tasks using browser 1, implement feedback for Projects using browser 2"
Phase 6: QA (Parallel)
Run qa agents on different features in parallel (up to 6)
Test each screen/feature independently
Example: "Test Tasks creation using browser 5, test Projects editing using browser 6"
How to Spawn Parallel Agents
CRITICAL: Each parallel agent must use a different browser number.
"Create the Tasks table using browser 1"
"Create the Projects table using browser 2"
"Create the Users table using browser 3"
Browser assignment rules:
Use browsers 1-6 only
Each agent gets a unique browser number (no sharing)
Example: If spawning 3 data agents, assign browsers 1, 2, 3
Use ONLY its assigned browser instance (mcp__plugin_glide_browser-N__browser_* tools)
Work independently without blocking others
Complete when the task is done
Key Rules for Parallelization
Get API token early - Create one table in the first browser, grab the token from Data Editor
Each agent needs the app ID - Pass appId to all parallel agents
Tables must exist before screens - CRITICAL: All tables must be created (Phase 2) before any screens can be built (Phase 3). You can't design a screen without its backing data table.
Data and tables come first - Ensure real or sample data is imported into each table before building screens for it
Use all 6 browsers - Don't leave idle browsers when you could be building
Integrations - Call API, Claude, OpenAI, Google Maps
The dropdown is searchable - type to filter.
Layout Editor
Adding Screens/Tabs
Click "+" in Navigation or Menu section
Choose: Screen from data, Custom screen, or Form screen
Configure in right panel
Set a short label - 1-2 words maximum (e.g., "Tasks", "My Team")
Pick an appropriate icon - click the icon and choose one that matches the content
Tab labels: Keep them short! 1-2 words max.
Good: "Tasks", "Team", "Settings", "Orders"
Bad: "My Task List", "Team Member Directory"
Tab icons: Don't leave random icons. Choose icons that represent the screen's purpose:
Tasks/Todos: checkmark, clipboard, list
People/Users: person, people, user
Settings: gear, cog, sliders
Home/Dashboard: home, grid, chart
Messages: chat, envelope, bell
Calendar/Events: calendar, clock
Files/Documents: folder, document, file
Search: magnifying glass
Add/Create: plus, add
Adding Components
Select a screen
Click "+" in Components section
Search or browse categories
Click to add, configure in right panel
Collection Styles
Card, List, Table, Data Grid, Checklist, Calendar, Kanban, Custom
Settings
Name & Icon - App name (keep short, 2 words max, no company name), icon, logo
Appearance - Accent color, layout (Left/Top), style (Light/Deep/Accent)
Access - Who can access the app
Integrations - External connections
Changing App Icon (Emoji Picker)
To change the app icon using the emoji picker:
Go to Settings tab → Name & Icon section
Click the icon image (not the Upload button) → Opens "Emoji Mart™" picker
Type the emoji name in the search box (e.g., "rocket", "checkmark", "clipboard")
Click the emoji button from the search results
Important: Always use the search box! Browsing categories is slow and error-prone. The search instantly filters to matching emojis.
Common emoji searches for app icons:
Tasks: "checkmark", "clipboard", "list"
People: "person", "people", "user"
Business: "briefcase", "chart", "money"
Home: "home", "house"
Settings: "gear", "wrench"
Calendar: "calendar", "clock"
Messages: "chat", "envelope", "bell"
Food: "pizza", "coffee", "burger"
Travel: "car", "plane", "rocket"
Browser Automation Tips
Column names may not save: Always select the column type explicitly.
Avoid info icons (ⓘ): They trigger tooltips that can block the UI.
Hide Tooltips
Rich tooltips with class rich-tooltip-* can block clicks and interfere with automation. Run this via browser_evaluate to hide them:
Run this periodically if tooltips keep appearing, or after hovering over info icons accidentally.
Keyboard shortcuts:
Cmd+K - Open search
Escape - Close dialogs and panels
CMD+SHIFT+ENTER - Add new column (when in Data Editor with table selected)
CMD+Z (macOS) / CTRL+Z (Windows) - Undo last action
Undo mistakes:
Glide Builder supports standard undo functionality. If you accidentally delete a component, action, or make an unwanted change, immediately use CMD+Z (macOS) or CTRL+Z (Windows) to revert it.
Common scenarios:
Deleted the wrong action → CMD+Z to restore it
Removed a component by mistake → CMD+Z to bring it back
Changed a setting incorrectly → CMD+Z to revert
Important: Undo only works for recent actions in the current session. If you navigate away or refresh, you may not be able to undo.
