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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use metadata to select entity-index or a sibling Vue file. Do not place UI implementation inside Page metadata.
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.
pages/ path.dygo generate page <app>/<page> to create YAML, Vue, and access files.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/.renderer: entity-index when a Page should show the entity list UI without a sibling Vue file.<page>.vue beside the YAML. Do not implement a separate App frontend bundle contract.Validate Page metadata through the current project validation path. Confirm that boot data, navigation, route resolution, permissions, and renderer registration agree.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.