Datex Studio — Shared Reference

This skill is a library, not a workflow. The other datex-studio-* skills cite the files here via relative paths (e.g. ../datex-studio-shared/branch-setup.md). It exists as its own skill so that npx skills / skills.sh can install it alongside its dependents — sibling non-skill directories (the old shared/) are not copied by those tools.

When this skill is relevant

You're following another Datex Studio skill and it points you here. Read only the specific reference file the parent skill named — do not preload the whole tree.

If a user asks a Datex Studio question that isn't already scoped to a more specific skill (e.g. "how do branch IDs work across dxs commands?", "what's the OData pagination pattern?"), use the index below to find the right file.

Reference index

Cross-skill operational context

• configuration-roundtrip.md — Canonical dxs configuration get → extract inner .json → edit → upsert round-trip for every component-creator/editor skill, and the silent-wipe bug the extraction step prevents. The branch is the source of truth; the JSON files are throwaway scratch.
• branch-setup.md — Active organization, repository, feature branch, and API connection selection. The Branch ID Policy (always ask, never assume) lives here.
• studio-management.md — Studio lifecycle: check status, start in background with readiness verification, clean up.
• context-navigation.md — How to retrieve and read dxs -O json … context responses (backend vs. frontend symbol filtering), plus the nomenclature registry for discovering custom types and enum members ($types.<Package>.*).
• flow-code-patterns.md — $utils.isDefined(), date defaulting, $shell.Reports.open{ref}(), and the OData pagination / 5000-record cap pattern.