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-documentation
Write or update dygo instructions, reference documentation, task descriptions, CLI help, metadata examples, or architecture notes. Use when documentation quality and contract accuracy are central to the task.
含まれるファイル（1）
- SKILL.md1.6 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
dygo Documentation
Write accurate technical information in ASD-STE100 style.
Rules
- Use short sentences and active voice.
- Give one instruction per sentence when practical.
- Use the exact terms from
docs/nomenclature.md. - Call the main UI Studio. Use Entity, Record, Field, App, Hook, Fixture, Patch, Job, and Schedule with their defined meanings.
- Separate current behavior from proposed behavior and coming-soon behavior.
- For SDK or runtime changes, check adjacent guides for stale claims about access modes, transaction scope, and available services. Verify examples against the actual service wiring, not only the public interface.
- When code and documentation disagree during a review, report the conflict. Do not silently select the more permissive contract.
- Verify commands, flags, paths, metadata keys, and examples against current code.
- Put source-of-truth details in the canonical document and link to them from related documents.
- Do not copy the same contract into many files.
- Use realistic examples that match the current schema and CLI.
- State safety requirements before destructive or privileged instructions.
- Do not describe framework internals as supported Business App APIs.
Check
Read the completed text as a new framework user. Confirm that each procedure has a clear outcome, prerequisites, safe command order, and no unsupported promise.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
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日 更新