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-app-development
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.
含まれるファイル（1）
- SKILL.md1.6 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
dygo App Development
Build business behavior in an App and let dygo provide the platform foundation.
Start
- Find the project root from
dygo.yml. - Read
docs/doctrine.md,docs/app-model.md, anddocs/dir.mdwhen they exist in the checkout. - Inspect the target App and nearby examples before you choose a structure.
- Confirm that the requested behavior is business-specific. Put reusable platform behavior in the framework instead.
Rules
- Use the terms in
docs/nomenclature.md. - Prefer an App manifest, Entity metadata, access metadata, Hooks, Fixtures, Jobs, Schedules, and Patches over one-off infrastructure.
- Use
pkg/dygofrom App-owned Go code. Do not import frameworkinternal/packages. - Start with the smallest valid App shape. Add Pages, reports, or custom behavior only when metadata-driven Studio rendering is insufficient.
- Keep generated files predictable. Do not overwrite developer-owned Hook or Job logic.
- Treat server-side permissions and observable failure behavior as part of the feature.
- Do not implement behavior that current documentation marks as proposed or coming soon unless the task is to develop that framework capability.
Check
Use focused commands such as dygo app validate, dygo entity validate, dygo hook validate, and dygo doctor. Use broader tests only when the change risk justifies them.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
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日 更新
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日 更新
Improve or review ordinary dygo code changes for simplicity, focused scope, canonical ownership, clear boundaries, and verifiable behavior. Use for normal implementation and refactoring quality; use dygo-thermonuclear-review only for an explicitly severe audit.
日本語の概要は準備中です。原文の説明を表示しています。
hapyco/dygo162026年10月2日 更新