跳到主要内容

Lang Graphql

Lint and codegen GraphQL schemas and operations.

Skill metadata​

SourceBundled (installed by default)
Pathskills/software-development/lang-graphql
Version1.0.0
AuthorVibeOS
LicenseMIT
Platformslinux, macos, windows

Reference: full SKILL.md​

信息

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

GraphQL Language Pack Skill

Drive GraphQL work with the project index and standard CLI recipes. LSP hint: none (toolchain CLI) (editor-side when applicable). Zero new core tools.

What this language is (beginner)​

Способ описать API одним графом типов: клиент просит ровно те поля, которые нужны. Часто вместо/рядом с REST.

Лучше всего для:

  • единый API для web+mobile
  • schema-first разработка
  • Federation / Apollo / Yoga
  • codegen клиентов

When to Use​

Выбирай этот pack, если:

  • есть schema.graphql / .graphqlrc
  • нужен гибкий API для SPA/мобилки
  • пользователь просит GraphQL

Manifests (автодетект репозитория): .graphqlrc, .graphqlrc.yml, .graphqlrc.yaml, .graphqlrc.json, schema.graphql, graphql.config.yml, graphql.config.js

Обычно рядом: TypeScript клиент; часто Postgres; codegen в CI.

См. также skill choose-language-pack и vibeos language recommend "…".

When NOT to use​

  • простой CRUD REST → TypeScript/Go/Python HTTP API
  • только SQL без API-слоя → sql pack
  • tRPC в одном TS-монорепо → TypeScript

Prerequisites​

vibeos pack apply lang-graphql --apply
vibeos pack apply project-intelligence --apply

How to Run​

vibeos project index build
npx graphql-schema-linter || true
npx graphql-codegen || true

Quick Reference​

GoalCommand
Apply packvibeos pack apply lang-graphql --apply
Doctorvibeos language doctor graphql
Primary testnpx graphql-schema-linter
Choose guideskill choose-language-pack
Recommendvibeos language recommend "…"

Procedure​

  1. Для нового продукта сначала choose-language-pack / vibeos language recommend.
  2. Work from the project root that matches pack manifests.
  3. Prefer project-local toolchain and committed config (sqlfluff/buf/elm.json).
  4. Explain destructive DB or breaking contract changes; wait for explicit ask.
  5. Do not invent core tools; stay on terminal + read_file + index CLI.

Pitfalls​

  • Keep schema and resolvers in sync.
  • Do not expose internal fields without auth checks.

Verification​

vibeos language doctor graphql
vibeos project index status