Skip to content

internal: migrate Studio UI styling to Tailwind CSS #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
samohovets merged 1 commit into from
Jul 19, 2026
Merged

internal: migrate Studio UI styling to Tailwind CSS #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -251,6 +251,12 @@ pnpm bench:callback # release callback work-budget benchmark
pnpm validate:release # standard validation plus callback benchmark
```

### Studio styling

Studio uses Tailwind CSS v4 through the official Vite plugin. `packages/studio/client/src/studio.css` is configuration-only: it imports Tailwind, registers the React TSX source tree, and defines semantic `studio-*` theme tokens and the existing responsive breakpoints. All UI styling belongs in complete, statically detectable utility strings in `packages/studio/client/src/**/*.tsx`; shared utility-only primitives live in `ui.tsx`.

Do not add authored selectors, `@apply`, `@layer`, `@media`, or `@utility` rules to `studio.css`, and do not assemble utility names with string interpolation. Map dynamic UI states to complete class strings instead. Tailwind Preflight is enabled, so form controls must also carry their intentional utility styling. Validate changes with `pnpm --filter @patchwave/studio build` and `pnpm --filter @patchwave/studio test`.

The callback does not allocate, lock, parse, log, block, invoke JavaScript/N-API, or control the stream. Output is sanitized for non-finite values and bounded by a final safety guard.

## Experimental scope
Expand Down
Loading