mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-26 10:26:26 +01:00
The review gate asks for a test that verifies the fix. Add one. The original defect was a hardcoded color. The block used #1e1e2e and #cdd6f4 in the normal AND the prose-invert variables, so the theme could not change it. The regression to guard against is therefore simple: a literal color returns to one of these surfaces. Assert on the stylesheet, which follows the pattern already used by MarkdownAccentStyles.test.ts: - the rendered block rides --muted, --foreground, --border, --radius-lg - the editor content block rides the same four tokens - the normal and the inverted prose variables point at the same tokens - none of the three surfaces contains a hex, rgb() or hsl() literal - the copy and wrap controls do not use --muted, which is now the fill of the block they sit on Verified that the tests fail on the original defect. Restoring #1e1e2e and #cdd6f4 fails 2 of the 5. Export codeBlockActionStyle so the control test can read it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@paperclipai/ui
Published static assets for the Paperclip board UI.
What gets published
The npm package contains the production build under dist/. It does not ship the UI source tree or workspace-only dependencies.
Storybook
Storybook config, stories, and fixtures live under ui/storybook/.
pnpm --filter @paperclipai/ui storybook
pnpm --filter @paperclipai/ui build-storybook
Typical use
Install the package, then serve or copy the built files from node_modules/@paperclipai/ui/dist.