zedkit

Open-source building blocks for modern apps: small, dependency-light TypeScript packages. MIT licensed; see LICENSE.

Use npm packages (pnpm add @zedtech/…) or copy UI source via the shadcn registry where published — install or copy on the docs site.

pnpm add @zedtech/zedkit-ui          # React UI components (Tailwind v4)
pnpm add -D @zedtech/zedkit-ai       # one agent setup for Cursor, Claude, Codex…

Docs with live examples: zedkit.app. Full catalog by need below; five-minute start in 5-minute quickstart.

Packages

All packages are public on npm. Maturity is the least mature catalog need per package (criteria: docs/catalog/README.md).

Package	Version	Maturity
@zedtech/zedkit-ai (npm)	0.8.1	beta
@zedtech/zedkit-core (npm)	0.2.1	beta
@zedtech/zedkit-devtools (npm)	0.2.2	alpha
@zedtech/zedkit-flags (npm)	0.2.1	alpha
@zedtech/zedkit-i18n (npm)	0.2.0	alpha
@zedtech/zedkit-nest (npm)	0.1.5	beta
@zedtech/zedkit-observability (npm)

A package exists only when real, used code backs it — no placeholders. Each package README records its origin ("original work by the same author") and what it deliberately leaves out.

Looking for something?

"I want X, what do you have to do it?" — search the catalog index by need (machine-readable: docs/catalog/catalog.json). Golden rule (advice): reach every third-party library through a thin wrapper that re-exports it, instead of importing it directly all over the code — see docs/golden-rule.md.

Consumer projects: paste this into your agent instructions (canonical text: .agents/skills/use-zedkit/SKILL.md — keep in sync):

Before writing any helper, check zedkit first, then npm, and wrap what
you adopt: search the zedkit catalog by need and import from zedkit if it
exists; otherwise adopt a mature npm package behind a thin wrapper;
otherwise propose adding it to zedkit with its domain.

5-minute quickstart

Prerequisites: Node ≥ 22 and pnpm 9. In your own repo:

pnpm add -D @zedtech/zedkit-ai
npx zedkit-ai init . --provider cursor   # cursor, claude, codex, muse, all
# then ask your agent: "run the setup-ai skill"
npx zedkit-ai validate                   # must print: ok

Details: packages/ai/README.md. Every package installs the same way (pnpm add @zedtech/zedkit-<name>).

Tooling

• pnpm workspaces with a pinned packageManager and a shared catalog
• Turbo pipelines: typecheck, lint, build, test
• TypeScript strict, ESM + types, vitest, ESLint (raw try/catch is banned; use tryCatch from @zedtech/zedkit-core)
• Changesets for versioning; the release workflow publishes public packages to npm on every Version PR merge
• Docs site: pnpm dev rebuilds the catalog, then serves apps/docs with hot reload at http://localhost:3100 (docs at /docs)

pnpm install
pnpm dev                                     # docs site, http://localhost:3100
pnpm typecheck && pnpm lint && pnpm build && pnpm test

Public repo rules

• No secrets, no customer data, no internal URLs.
• No private names, endpoints, or domain terms from other projects.
• Third-party material (e.g. vendored skills) requires its licence file and a row in packages/ai/kit/THIRD_PARTY_NOTICES.md.