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.
Datos de origen
- Repositorio
- glideapps/mcp
- Última actividad en el origen
- 29 de agosto de 2026 a las 18:54
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 0
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- glideos-development
- description
- 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.
# 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.
Ver en GitHub