Develop or review dygo metadata loading, YAML decoding, JSON Schemas, validation, naming, Field types, registries, routes, and persisted metadata contracts. Use for framework-level metadata behavior rather than authoring one Business App Entity.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Keep metadata explicit, readable, and deterministic.
Read docs/metadata-authoring.md, docs/entity-metadata.md, docs/app-manifest.md, and the affected metadata document. Inspect shared packages such as internal/yamlmeta, Entity schema and catalog packages, naming, reserved words, routes, and Core metadata Records.
Use focused contract and round-trip tests for changed metadata behavior.
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.