Admin
078f7ac6f6
Button used Tailwind's bare `transition` utility, whose default property list includes background-color. Since the button's bg is a CSS custom property recomputed every frame by the same 600ms hue animation the main background uses, that extra transition smoothed it on a different (~150ms) timing, so its color change didn't match the page background's. Add a btn-transition utility that mirrors Tailwind's default transition list minus background-color, so the button's background tracks the hue animation frame-for-frame like the rest of the app, while hover/focus feedback (text color, ring, filter) still transitions normally.
web-player
Musify's web client: SvelteKit 2 (adapter-node), Svelte 5 runes, Tailwind 4,
TypeScript. Authentication is server-side OIDC against Zitadel (openid-client
and jose) with an encrypted session cookie; the backend is called from load
functions and form actions through a typed openapi-fetch client.
Development
npm install
npm run dev # :5173
Configuration lives in .env (template in .env.example). Bring the
infrastructure stack up first (see ../deploy/README.md)
and copy the WEB_CLIENT_ID / WEB_CLIENT_SECRET it writes to deploy/.env
into this .env once, then run the dev server.
npm run check # svelte-check — must be clean before closing a change
npm run lint # prettier --check . && eslint .
npm run format # prettier --write .
npm run build # production build into build/
npm run gen:api # regenerate src/lib/api/schema.d.ts from the running API
Production
Built and run as a container by the production stack — see
../deploy/README.md. There the same variables come from
deploy/.env.prod through compose instead of from .env.
Conventions and the design system are documented in CLAUDE.md and
in the musify-web skill.