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-database-engineering
Develop or review dygo PostgreSQL connectivity, schema planning, additive migration, prune, metadata persistence, Records, transactions, and schema snapshots. Use for framework database behavior and high-risk data lifecycle changes.
中文简介正在准备中。当前显示原文说明。
集成工具PostgreSQL
查看安装方法包含的文件（1）
- SKILL.md1.6 KB
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
dygo Database Engineering
Make database changes reviewable, transactional, and safe for business data.
Start
Read docs/database.md, docs/patches.md, and the relevant Record or metadata contract. Inspect the planner, executor, naming policy, and current schema tests before you edit behavior.
Rules
- Keep
dygo db migrateadditive and safe. - Use explicit prune for metadata-orphaned tables, columns, indexes, and constraints.
- Keep destructive targets concrete and visible in the plan.
- Use metadata as source of truth for dygo-managed schema.
- Preserve deterministic plans and schema snapshots.
- Keep related state changes atomic when partial application would violate an invariant.
- Use parameterized SQL. Do not interpolate business values or identifiers without approved quoting rules.
- Respect transaction ownership and PostgreSQL locking behavior.
- Make concurrent claims and uniqueness rules enforceable in the database when correctness depends on them.
- Keep Core metadata persistence on the same framework contracts where practical.
- Return actionable database errors without exposing credentials.
Check
Use focused planner and database tests. Verify both the intended schema result and meaningful data preservation. Development migrations require elevated execution because the database socket is outside the normal sandbox.
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
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日 更新