Kajabi

Structured code review for the sage-lib design-system monorepo. Reviews React component changes against sage's existing patterns (propTypes + forwardRef, classnames, configs.js, story + spec files) and Jest test coverage. Categorizes issues by severity.

Run parallel reviews of sage-lib changes using specialized reviewer agents (code, design, a11y, existence). Launches reviewers simultaneously, then consolidates feedback by severity. Use before opening a PR against develop.

Accessibility review criteria for sage-lib React components and SCSS. Sage is a leaf-level UI library so a11y bugs propagate to every consuming app — treat keyboard, ARIA, focus, semantic HTML, and contrast as first-class.

Design-token + SCSS review criteria for sage-lib. Covers sage-token discipline (`sage-color`, `sage-spacing`, `sage-border` helpers), Pine-token alignment for dark-mode shims, BEM-style classname conventions, and Storybook story coverage.

Existence / duplication review for sage-lib. Given a diff, flags new React components, SCSS partials, mixins, and design tokens that appear to duplicate something already in the library.

Run parallel reviews of Pine design-system changes using specialized reviewer agents (code, security, design, existence). Launches reviewers simultaneously, then consolidates feedback by severity. Use before creating a PR against main.

Design-token, SCSS, accessibility, and Figma Code Connect review for Pine. Covers component token files (`*.tokens.scss`), `:host` custom-property patterns, `:host-context([data-theme=dark])` dark-mode support, keyboard / ARIA / focus, semantic HTML, and `.figma.ts` alignment.

Existence/duplication review for Pine. Given a diff, flags new pds-* components, sub-components, tokens, and shared utilities that appear to duplicate something already in the library.

Structured code review for Pine design-system components. Reviews Stencil decorators (@Component, @Prop, @Event, @Method), TypeScript types, JSDoc consistency across components, lifecycle methods, spec + e2e test coverage, and auto-generated file hygiene. Categorizes issues by severity.

Security review criteria for Pine components. Pine ships pds-* web components that consume user content via slots and props. Reviewer focuses on XSS via innerHTML, slot sanitization, URL-prop validation, event handler injection, and secret leakage.