Repository navigation
-
Turning a module off or removing it never breaks your studio. A module whose library your code imports keeps that code working while it is off (DialKit's dials keep their values, with no panel or menus), and removing it rewrites that code into plain values first. A module that can do neither is refused, in Studio settings and the CLI, naming the files that use it.
-
DialKit: tune a prototype view with live dials, then press Save to code to write the values into the view as its new defaults. Right-click a view and choose Add DialKit, ask your agent for the dials you want, and Remove DialKit when you're done; the design stays as tuned. Hide the panel from the prototype's menu or with ⌘⇧;. It works with and without a design system, and never shows on published sites or embedded views. The Feedback Inbox overview and the Design Studio Marketing landing v3 show it in use. It's an optional module, on by default; turn it off in Studio settings.
-
Modules can add actions to the menus of file types they don't own (
ModuleApp.artifactActions), and a module library may load a package's own stylesheet. -
Agents can draw Mermaid on a canvas as editable shapes and arrows: the canvas
mermaidtool, live and withpnpm canvas, takes flowchart, sequence, class, state and ER diagrams, Gantt charts, timelines and quadrant charts. It uses Excalidraw's own converter, the one behind pasting Mermaid onto a canvas, and reports each Mermaid node's element id so agents can move or restyle it. -
Canvas runs on current Excalidraw (0.18.0-3c916c5) and diagrams on Pele 1.13. Sticky notes are Excalidraw's native sticky note: press N or pick it from the toolbar, choose from five colors, and the text shrinks to fit before the note grows. Agents make the same notes with the
notekind. Breaking: the Library is gone, along with its example sticky note. Notes already placed from it stay on your canvases as ordinary shapes; ask your agent to convert them to sticky notes if you want the new behavior. -
Search (⌘K) recognizes the prototype you have open, so choosing it keeps you on the artifact you're viewing instead of jumping to its first one. Thanks @robcrock.
-
A system's Resources search finds components by their file names and paths, such as
button.tsxorbutton.examples.tsx. Thanks @robcrock. -
A system's Overview and Icons source action opens its
intro.tsx, including Studio's own, instead of an unavailablesystem.ts. Thanks @robcrock. -
Closing the artifact filter clears its query, so a hidden search no longer leaves the tree empty. Thanks @robcrock.
-
A pull request or branch opens in GitHub Codespaces with editing working: the studio installs, starts, and opens in a browser tab. Reviewers who haven't joined the studio edit as the sample author.
-
pnpm check:linkschecks every relative link, heading anchor, and/documentation/...link in Markdown guidance, and CI runs it. -
Root
AGENTS.mdnow carries the standing working rules in its own Working in Studio section;src/platform/context/working-in-studio.mdis gone, andpnpm studio context --jsonno longer lists it underguidance. Skills keep their routes in a Skills section that module routing follows. -
Maintainer-only platform context (checks, resource identity, editing and saving, community contributions, releasing) moved to
src/platform/context/maintainers/. Links to the old paths or/documentation/context/platform.core/context/<name>addresses needmaintainers/added. -
Task skills no longer repeat the contributor scope line that
AGENTS.mdalready requires; it stays in the contributor skills. -
Component pages credit only the libraries whose
componentslist includes that component. A system'soriginno longer credits every component, so components ported from elsewhere are no longer attributed to shadcn/ui. The starter systems now list their shadcn components. A team system that credits shadcn should list its shadcn components in that library'scomponents. -
A
Linkwhose path doesn't resolve renders in place, inert and outlined in development, and the console names the path. Before, it failed the whole view, so one link in shared chrome took down every page. -
pnpm checkends with one line per system listing every missing token, with Tailwind's default value beside each. -
/systems/<folder-name>redirects to the system's permanent address. -
useColorMode()from#studio/runtimereads the nearest theme boundary's mode, for code that used to watch.darkon<html>. -
A component folder with an
index.tsis one component: its other files are internal parts, so ported components no longer need renaming to stay off the component list. A file inside it with its own docs or examples still gets a page. -
pnpm canvas … createwarns when new elements repeat existing content, so a retried call doesn't silently duplicate a canvas. -
Prototype and system code no longer sees Node types, so
window.setTimeoutreturns a number again. -
Views that import local images or fonts now pass preview verification instead of showing a permanent "could not be verified" warning.
-
rename-systemno longer edits upstream platform files, and platform tests no longer read the starter systems, so renaming or deleting a starter keepspnpm testpassing and updates clean. -
The theme scope check accepts sibling selectors inside the theme, such as
.theme .a + .b;.theme + .bstill fails. -
Studio's Tailwind Typography classes are now
studio-prose, so a system's ownproseclass no longer picks up the plugin's styles. Team code that used Studio'sproseclasses should switch tostudio-prose. -
pnpm studio --help(or--helpafter any command) lists every command and option.configureusage shows that omitted settings are kept. -
Files written directly (by an agent or an editor) no longer need
pnpm studio identify: the running dev server gives new views, documents, and canvases their permanent identity as they appear, in prototypes you can edit, andpnpm canvasdoes the same for its prototype and builds a fresh manifest instead of reading a stale one.pnpm studio identifyremains for work without the dev server, and its preview now lists files instead of example IDs. -
CLI commands no longer tell you to restart the dev server after configuration, module, or system changes; it already restarts itself.
-
When the CLI, an agent, or another tab changes the studio's configuration, open tabs show Applying changes until the restarted studio has loaded, instead of the old studio and then a blank page. Leaving Studio settings while a save applies no longer keeps that screen over every page in the tab. Starting the studio, or turning a module on or off, no longer reloads the page a second time once a view loads its system's packages.
-
Describe how to propose an improvement and what happens next in
CONTRIBUTING.md, with a feature proposal issue form. Maintainers follow a new community contributions guide to assess, adapt, release, and credit outside work. -
Report bugs through a bug report issue form. Maintainers triage each issue as now, later, or close, and reply with the outcome; the community contributions guide gives the decision rules and the brief an agent drafts for the maintainer.
Updating from 0.1.3
Follow the manual upgrade guidance and preserve local content and settings. Run pnpm install --frozen-lockfile afterwards: this release adds dialkit and motion and updates Excalidraw and Pele. Check these breaking changes against your studio:
- Canvas's Library is gone. Notes placed from it stay as ordinary shapes; ask your agent to convert them to sticky notes if you want the new behavior.
- Studio's Typography classes are now
studio-prose. Team code that used Studio'sproseclasses should switch. - A system's
originno longer credits every component. A team system that credits shadcn should list its shadcn components in that library'scomponents. - Maintainer-only context moved to
src/platform/context/maintainers/, andsrc/platform/context/working-in-studio.mdis gone. Update links to the old paths.