Repository navigation
feat: documented Storybooks for app + site with CI-enforced coverage - #48
Conversation
pnpm typecheck previously never checked .storybook/main.ts or .storybook/preview.tsx (only constants.ts was pulled in transitively via the Toggle story import). Add .storybook/**/* to tsconfig.web.json's include so a future type error in either file fails typecheck.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Adds a test that requires every visual component folder to have a *.stories.tsx file, with exemptions only for non-visual/behavioral components (JsonLd, SetHtmlLang, SvgSprite, RevealClient) and server-only page compositions (BlogArticle, BlogIndex, HomePage, LegalPage, PrivacyPage). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Documents the required .stories.tsx per component folder and the stories-coverage.test.ts EXEMPT-list convention in CLAUDE.md, adds a Storybook section covering both books and the docs/storybook MDX convention, updates STATUS.html with the completed roadmap item and session log, and fixes a pre-existing Biome formatting error in stories-coverage.test.ts that was failing `biome ci`. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
site/tsconfig.json's include globs never matched the dot-directory site/.storybook/, so main.ts and preview.ts were silently excluded from tsc --noEmit. Add .storybook/**/*.ts to include. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sweep the last em dashes out of story-file comments for consistency with 07a28a5, which already did this for CookieConsent. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 28 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (77)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…rerun green Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Union resolutions in package.json/.gitignore/CLAUDE.md/STATUS.html; pnpm-lock regenerated (vitest unified on 3). stories-coverage.test.ts pinned to the node environment — under the renderer project's jsdom, import.meta.url is not a file: URL in vitest 3. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Implements docs/superpowers/specs/2026-07-29-storybook-design-system-design.md
Run locally:
pnpm storybook(app, port 6006) andpnpm storybookinsidesite/(port 6007).🤖 Generated with Claude Code