---
name: use-studio
description: Create or refine prototypes, canvases, diagrams, documents, and design systems in an existing local Design Studio. Use create-studio for installation and open-studio to reopen the environment.
---

Use the studio identified by the person or the current primary workspace. If the location is unresolved, ask which studio they mean. A preview URL alone does not establish the repository. Read its `AGENTS.md` and required working context before edits.

If the studio needs reopening or workspace handoff, follow [open-studio](../open-studio/SKILL.md). Preserve the repository and use its current procedures rather than importing instructions from another studio or the plugin cache.

For a request to publish through ChatGPT Sites, follow [publish-studio](../publish-studio/SKILL.md). Reuse the studio's Site identity for updates. Editing locally does not publish automatically.

In studios with native project skills, inspect the relevant platform, enabled module, and assigned system skill descriptions. Use the canonical procedure selected for the request. In older studios, follow their repository entry point and linked workflows; do not relocate their files or upgrade them without a request.

Run commands through `node <installed-plugin>/scripts/bootstrap.mjs exec --destination <folder> -- <command> [args...]` for plugin-created studios, especially when the host selects an unusable system Git. This preserves the studio’s pinned Node and working Git; avoid manual PATH replacement.

For prototype work, resolve contributor identity and metadata assignment. Explicit `system: null` means no system; only an omitted assignment follows the configured default. For a pending rebuild, include the target system's guidance and preserve the original. The browser's selected system does not change assignment.

When introducing a fresh starter, clearly identify any remaining Product and Marketing systems and Feedback Inbox and Design Studio Marketing prototypes as learning examples. Explain that the person can customize, replace, or remove them to fit their needs. Do not assume these examples remain unchanged in an existing studio, and do not remove work without a request.

Check module availability before offering its features. Load only the relevant product context, complete the task using the studio's tools, and perform its required checks and rendered review. Explain the result in ordinary design language and leave the person a working preview. Sharing and publishing require their own request.