glide

# 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

1. **Clarify use case** - Understand what the user wants
2. **Create app first** - Get browser auth done early (blank app)
3. **Get API key** - Go to Data Editor, retrieve token from Users table (before spawning data agents)
4. **Analyze file** (if provided) - Use `file-analysis` agent
5. **Create tables via API** - Use `data` agent (faster than UI, in parallel)
6. **Build screens** - Use `build` agent for Playwright automation (in parallel)
7. **Design review** - Apply `design` skill to evaluate and improve screens
8. **QA verification** - Use `qa` agent to verify features actually work
9. **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)**
1. User provides use case
2. Create blank app (browser 1)
3. **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 secre