Start working with Glide - includes interactive login, app selection, and task choice
Guides you through Glide authentication, app selection, and task setup. Use this first to log in, choose an app, and launch the appropriate agent for your work.
/plugin marketplace add glideapps/glide-code/plugin install glide@glideThis command guides you through the initial setup for working with Glide apps, including authentication and app selection.
IMPORTANT: Read the main glide skill first - it contains the workflow, agent coordination, and parallel building strategy needed to understand app building.
Before doing anything else, read the main glide skill.
This skill covers:
This context is essential for understanding how to orchestrate the setup and build process.
Check .glide/config.json to see if the user is already authenticated.
If the file exists with authentication data or an authenticated browser profile exists:
Guide the user through logging in interactively:
Open browser: Use mcp__plugin_glide_browser-1__browser_navigate to go to https://go.glideapps.com
Check login status: Use mcp__plugin_glide_browser-1__browser_snapshot to see current state
If already logged in: (shows "New app" button, dashboard visible)
If not logged in: Guide the user:
"Please log in to Glide in the browser window. Click 'Sign In' and complete the authentication. I'll detect when you're done."
Wait for completion: Poll mcp__plugin_glide_browser-1__browser_snapshot every 3 seconds
Sync authenticated profile to all browsers:
mkdir -p .glide
for i in 2 3 4 5 6; do
rm -rf ".glide/browser-profile-$i"
cp -R ".glide/browser-profile-1" ".glide/browser-profile-$i"
done
Inform user:
"✓ Logged in! All 6 browsers are authenticated and ready for parallel work."
Store authentication:
.glide/config.json to store authenticated statusUse AskUserQuestion:
If the user selected "Edit existing app":
Use AskUserQuestion:
The URL format is typically: go.glideapps.com/app/{appId}/layout
Extract the appId from the URL if provided, or search by app name.
Store the app context:
.glide/config.json to include appUrl and appIdUse AskUserQuestion:
Based on their selection:
build agentfile-analysis agentdesign-review agentqa agentapp-research agentglide skill - this is mandatory before proceeding.glide/config.json first to check existing auth and settingsdata agent when actually creating tables (not at setup time)