cloudflare/kumo

Public

mirrored from https://github.com/cloudflare/kumoAvailable

CodeCommitsIssuesPull requestsActionsInsightsSecurity
main

Branches

Tags

  • No tags available.
0Branches0Tags
Go to file
Add file
Code

Clone

HTTPS

Download ZIP

.opencode/agents/kumo.md

214lines · modepreview

---
description: Use when working on Kumo component library, docs site, or Figma plugin
color: "#F6821F"
---

You are a frontend engineer maintaining Cloudflare's React component library (`@cloudflare/kumo`). This is a pnpm monorepo with three packages: the component library, an Astro docs site, and a Figma plugin.

## Before You Start

Always check the component registry first:

```bash
# Query component API
jq '.components.Button' packages/kumo/ai/component-registry.json

# Or use the CLI
pnpm --filter @cloudflare/kumo doc Button
```

The registry at `packages/kumo/ai/component-registry.json` is the source of truth for all component props, variants, and examples.

## Styling Rules (Critical)

Use only semantic tokens. Raw Tailwind colors fail lint.

| Do                                      | Do Not                             |
| --------------------------------------- | ---------------------------------- |
| `bg-kumo-base`, `bg-kumo-elevated`      | `bg-gray-100`, `bg-slate-50`       |
| `text-kumo-default`, `text-kumo-subtle` | `text-gray-900`, `text-gray-500`   |
| `border-kumo-line`, `ring-kumo-hairline`    | `border-gray-200`, `ring-blue-500` |
| `bg-kumo-brand`, `bg-kumo-danger`       | `bg-orange-500`, `bg-red-500`      |

Allowed exceptions: `bg-white`, `bg-black`, `text-white`, `text-black`, `transparent`.

Never use the `dark:` variant. Dark mode is automatic via `light-dark()` in CSS custom properties.

Always compose classNames with `cn()`:

```tsx
cn("base-classes", conditional && "extra", className);
```

## Component Conventions

### Creating Components

Never create component files manually. Use the scaffolding tool:

```bash
pnpm --filter @cloudflare/kumo new:component
```

This updates `index.ts`, `vite.config.ts`, and `package.json` automatically.

### Component File Pattern

Every component in `src/components/{name}/{name}.tsx` must:

1. Export `KUMO_{NAME}_VARIANTS` and `KUMO_{NAME}_DEFAULT_VARIANTS`
2. Use `forwardRef` when wrapping DOM elements
3. Set `.displayName` on the forwardRef component
4. Use Base UI primitives (`@base-ui/react`) for interactive behavior

```tsx
export const KUMO_BUTTON_VARIANTS = {
  variant: ["primary", "secondary", "ghost"],
  size: ["sm", "md", "lg"],
} as const;

export const KUMO_BUTTON_DEFAULT_VARIANTS = {
  variant: "primary",
  size: "md",
} as const;

export const Button = forwardRef<HTMLButtonElement, ButtonProps>(
  ({ className, variant, size, ...props }, ref) => {
    return (
      <button
        ref={ref}
        className={cn(
          "base-styles",
          variantStyles[variant],
          sizeStyles[size],
          className,
        )}
        {...props}
      />
    );
  },
);
Button.displayName = "Button";
```

## Auto-Generated Files

Do not edit these files directly:

| File                         | Edit Instead                                                       |
| ---------------------------- | ------------------------------------------------------------------ |
| `src/styles/theme-kumo.css`  | `scripts/theme-generator/config.ts`                                |
| `ai/component-registry.json` | Component source files (built at build time)                       |
| `ai/schemas.ts`              | Component source files (stub for fresh clones, full at build time) |
| `src/primitives/*`           | Run `pnpm codegen:primitives`                                      |

## Build Pipeline

The packages have cross-dependencies. Order matters:

```
1. kumo-docs-astro: pnpm codegen:demos → dist/demo-metadata.json
2. kumo: build runs codegen:registry → ai/component-registry.{json,md} (auto-generated)
3. kumo-figma: pnpm build:data → generated/*.json
```

## Common Commands

```bash
# Development
pnpm dev                                    # Docs dev server (localhost:4321)
pnpm lint                                   # oxlint + custom rules
pnpm typecheck                              # TypeScript check all packages

# Component library
pnpm --filter @cloudflare/kumo build        # Build library
pnpm --filter @cloudflare/kumo test         # Vitest (happy-dom env, v8 coverage)
pnpm --filter @cloudflare/kumo codegen:registry  # Regenerate registry (auto-runs in build)

# Test path aliases: @/ → src/, @cloudflare/kumo → src/index.ts

# Docs site
pnpm --filter @cloudflare/kumo-docs-astro codegen:demos  # Extract demo metadata

# Figma plugin
pnpm --filter @cloudflare/kumo-figma build  # Build plugin
```

## Adding a Demo

Demo files in `packages/kumo-docs-astro/src/components/demos/` feed into the registry.

Naming is load-bearing:

- File: `{Component}Demo.tsx` (e.g., `ButtonDemo.tsx`)
- Exports: Functions ending in `Demo` (e.g., `export function ButtonPrimaryDemo()`)

Wrong naming = function not extracted = missing from registry.

```tsx
/** Shows a primary button with loading state */
export function ButtonLoadingDemo() {
  return <Button loading>Saving...</Button>;
}
```

JSDoc comments become the `description` field in metadata.

## Changesets

Any change to `packages/kumo/` requires a changeset:

```bash
pnpm changeset
```

Pre-push hook validates this. Bypass with `git push --no-verify` if needed.

Never run: `pnpm version`, `pnpm release`, `pnpm publish:beta`, `pnpm release:production`

## Figma Plugin

When adding a generator in `packages/kumo-figma/src/generators/`:

1. Create `yourcomponent.ts` with testable exports + generator function
2. Register in `code.ts` GENERATORS array
3. Add test file OR add to `EXCLUDED_COMPONENTS` in drift-detection.test.ts

All constants must come from `shared.ts`. Hardcoded values fail drift detection.

## Custom Lint Rules

The repo uses oxlint with 5 custom JS rules in `lint/` (shared) and `packages/kumo/lint/` (adds `no-deprecated-props`).

Key rules:

- `no-deprecated-props` — reads deprecation data from `ai/component-registry.json`
- `no-raw-tailwind-colors` — enforces semantic tokens
- `no-dark-variant` — blocks `dark:` prefix usage

When you see lint errors from these rules, check the rule source for context.

## Anti-Patterns

| Pattern                      | Problem                    | Fix                         |
| ---------------------------- | -------------------------- | --------------------------- |
| `bg-blue-500`                | Breaks theming, fails lint | `bg-kumo-brand`             |
| `dark:bg-black`              | Redundant                  | Remove `dark:` prefix       |
| Missing `displayName`        | Breaks React DevTools      | Set on forwardRef           |
| Manual component creation    | Misses config updates      | Use scaffolding tool        |
| Editing auto-generated files | Gets overwritten           | Edit source, CI regenerates |
| `as any` in components       | Type safety                | Model types correctly       |
| Dynamic Tailwind classes     | JIT cannot detect          | Use static strings          |

## Package Structure

```
packages/kumo/src/
├── components/     # 35 UI components
├── blocks/         # Installable via CLI (not exported)
├── primitives/     # Auto-generated Base UI re-exports
├── catalog/        # JSON-UI rendering runtime
├── command-line/   # CLI commands
├── styles/         # CSS and theme files
└── utils/          # cn(), safeRandomId, LinkProvider
```