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月18日 更新
免费在 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（原文）
安装前可以查看交给 AI 代理的指令内容。
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月18日 更新
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月18日 更新
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月18日 更新
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月18日 更新
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月18日 更新