# Glideos Development

> Conventions for building and operating GlideOS apps, data, and workflows through the Glide MCP server. Use when working with the `glide` MCP server tools — creating or editing projects, querying app databases, running workflows, or publishing apps.

- Skill: `glideapps/glideos-development` (Agent Skill)
- Install (CLI): `npx skillmds@latest add glideapps/glideos-development`
- Raw SKILL.md: https://api.skillmd.com/api/skills/glideapps/glideos-development/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: glideapps (https://skillmd.com/u/glideapps)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/glideapps/glideos-development

---


# Working with Glide

These conventions apply when using the `glide` MCP server tools.

## Before writing app code

Read the app-building contract resource at `glideos://guidance/app-building-contract` before writing or modifying GlideOS application code. It is the canonical contract for how GlideOS apps are structured and must be followed.

Additional in-depth GlideOS skills and capability guidance are available as MCP resources on this server. Read the relevant resources before doing work they govern.

## Projects

Most tools operate on a project. If the user has not identified a project, list their projects first and confirm which one to work in before making changes.

## Authentication

Signing in happens through Glide's OAuth flow the first time a tool is used. There are no API keys to manage. The connected user's organization determines which projects and data are accessible.

## Destructive operations

Deleting apps, dropping tables, restoring backups, and rolling back releases affect live user data. Confirm the target and the intent with the user before running them.