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.
ソース情報
- リポジトリ
- glideapps/mcp
- ソースの最終更新活動
- 2026年8月29日 18:54
- 検出された SKILL.md の言語
- 英語
- スター
- 0
- フォーク
- 0
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- 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.
GitHubで見る