跳到正文
cccskills
免费在 GitHub 公开

dygo-pages-and-studio

Define dygo App Pages and metadata-driven Studio experiences for Business Apps. Use when an App needs a Page, navigation entry, renderer choice, or Studio presentation beyond default Entity routes.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md1.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

dygo Pages And Studio

Use metadata to select entity-index or a sibling Vue file. Do not place UI implementation inside Page metadata.

Start

Read docs/pages.md, docs/studio.md, and the Page-related parts of docs/app-model.md and docs/dir.md. Confirm which Page features exist now.

Rules

  • Keep the Page bundle app-owned under the documented pages/ path.
  • Use dygo generate page <app>/<page> to create YAML, Vue, and access files.
  • Use renderer: vue with a sibling <page>.vue file under apps/<app>/pages/<page>/. Studio globs every App's Page Vue files into the host. Studio Home lives at apps/studio/pages/home/.
  • Use renderer: entity-index when a Page should show the entity list UI without a sibling Vue file.
  • Let Studio own rendering, layout, permissions, loading, errors, and shared interaction patterns.
  • Prefer normal Entity and Record surfaces when they solve the task.
  • Studio lists App Pages in the sidebar except Home. Home stays on the Studio home control.
  • Add a Page only when it represents a useful business Space or cross-Entity entry point.
  • Keep navigation labels and actions in dygo vocabulary.
  • Do not encode arbitrary frontend code, SQL, or unvalidated behavior in metadata.
  • Put Vue UI in <page>.vue beside the YAML. Do not implement a separate App frontend bundle contract.

Check

Validate Page metadata through the current project validation path. Confirm that boot data, navigation, route resolution, permissions, and renderer registration agree.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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日 更新

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日 更新

查看 hapyco 的全部技能

报告此技能的问题