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.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add hapyco/dygo --skill dygo-pages-and-studio --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Dygo Pages And Studio?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hapyco-dygo-pages-and-studio)More formats (shields.io, HTML) on the badges page.
---
name: dygo-pages-and-studio
description: 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.
---
# dygo Pages And Studio
Use metadata to select a framework-owned renderer. 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 a stable Page key and a supported renderer.
- Let Studio own rendering, layout, permissions, loading, errors, and shared interaction patterns.
- Prefer normal Entity and Record surfaces when they solve the task.
- 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.
- Do not implement proposed custom UI contracts as if they are supported.
## Check
Validate Page metadata through the current project validation path. Confirm that boot data, navigation, route resolution, permissions, and renderer registration agree.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.
