Design, implement, or review dygo roles, Entity access metadata, Permissions, and permission-aware Business App behavior. Use when access to Records or business actions is central to the task.
日本語の概要は準備中です。原文の説明を表示しています。
hapyco/dygo162026年10月2日 更新
無料GitHub で公開
dygo-metadata-engineering
Develop or review dygo metadata loading, YAML decoding, JSON Schemas, validation, naming, Field types, registries, routes, and persisted metadata contracts. Use for framework-level metadata behavior rather than authoring one Business App Entity.
含まれるファイル（1）
- SKILL.md1.6 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
dygo Metadata Engineering
Keep metadata explicit, readable, and deterministic.
Start
Read docs/metadata-authoring.md, docs/entity-metadata.md, docs/app-manifest.md, and the affected metadata document. Inspect shared packages such as internal/yamlmeta, Entity schema and catalog packages, naming, reserved words, routes, and Core metadata Records.
Rules
- Keep YAML files as source of truth and persisted Core metadata as the runtime registry.
- Use one decoding and validation contract for equivalent metadata.
- Reject unknown, conflicting, reserved, or ambiguous identities early.
- Keep App-qualified internal identity separate from user-facing routes and storage names.
- Centralize Field-type behavior, naming, reserved names, and route rules in shared registries.
- Keep JSON Schemas aligned with current accepted metadata, but treat runtime Go validation as authoritative.
- Preserve deterministic ordering in validation, plans, and persisted metadata.
- Return diagnostics with the source file and exact metadata path when possible.
- Do not add required metadata only to serve display or storage derivations that dygo can compute.
- Update documentation, schema files, generators, runtime readers, and validation together when a public metadata contract changes.
Use focused contract and round-trip tests for changed metadata behavior.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Design, implement, or review dygo HTTP APIs and public App SDK contracts. Use for Record APIs, metadata and boot endpoints, query behavior, response envelopes, compatibility, and public Go interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
hapyco/dygo162026年10月2日 更新
Diagnose a dygo Business App that does not validate, boot, route, render, authorize, migrate, or execute background work correctly. Use for evidence-first investigation rather than feature implementation.
日本語の概要は準備中です。原文の説明を表示しています。
hapyco/dygo162026年10月2日 更新
Build or extend a dygo Business App using the supported project layout, generators, metadata, SDK, and validation workflow. Use for general app work that is not primarily Entity modeling, access, hooks, Jobs, fixtures, or patches.
日本語の概要は準備中です。原文の説明を表示しています。
hapyco/dygo162026年10月2日 更新
Review a dygo Business App for framework conventions, model quality, access control, SDK boundaries, observability, and safe lifecycle behavior. Use for App audits and pre-merge reviews, not ordinary implementation.
日本語の概要は準備中です。原文の説明を表示しています。
hapyco/dygo162026年10月2日 更新
Design, implement, or review the dygo framework CLI in Go with Cobra. Use for commands, flags, help, prompts, plans, output contracts, completion, and project-aware CLI behavior. Do not use for operating a deployed business through the reserved dygo-cli operator skill.
日本語の概要は準備中です。原文の説明を表示しています。
hapyco/dygo162026年10月2日 更新