---
id: SPEC
title: "@cleepi/toolkit"
status: shipped
created: 2026-06-02
owner: Honza
related:
  - ../../docs/DRAFT-005-cleepi-toolkit-v0.1.0/spec.md
---

# Spec: `@cleepi/toolkit`

## Purpose

One-install meta-package that delivers the full Cleevio pi experience.
Bundles every general-purpose `@cleepi/*` package, exposes their resources
through a single `pi` manifest, and adds a `/setup` flow to walk users
through the post-install configuration each member needs.

## Scope

**In:** aggregation of universally-useful Cleepi packages, plus onboarding
glue (`/setup` prompt, `cleepi-setup` skill).

**Out:**

- Project-specific packages (e.g. future `@cleepi/packeta-*`). Toolkit is
  the universal set.
- Replacing à la carte installs. Both paths remain valid; toolkit is the
  recommended one.
- Auto-running setup. `/setup` is invoked, never pushed.
- Owning logic that belongs in a member. Toolkit re-exports; it does not
  reimplement.

## Members

**Bundled directly** (in `bundledDependencies`, resources re-exported via
toolkit's pi manifest):

| Member | Resources re-exported |
| --- | --- |
| `@cleepi/sdd` | extensions, skills, prompts |
| `@cleepi/base` | extensions, themes |
| `@cleepi/coding` | extensions, skills, prompts |
| `@cleepi/crew` | extensions, skills, prompts |

**Pulled in via `@cleepi/crew`'s install flow** (DRAFT-003-crew-peer-deps):
`@cleepi/git`, `@cleepi/atlassian`. Crew's extension auto-installs them as
standalone npm packages on first session. Toolkit doesn't bundle these to
avoid duplicating their installs (which causes skill collisions).

Themes are re-exported (so `cleevio-dark` is available) but not auto-activated.

## Release contract

Every release of a *bundled* member (`sdd`, `base`, `coding`, `crew`)
implies a toolkit release at the same or greater SemVer level.
`bundledDependencies` snapshots concrete versions at publish time; bumping
a bundled member without re-releasing toolkit ships stale children.

Releases of `@cleepi/git` and `@cleepi/atlassian` do **not** require a
toolkit release. Crew installs them by name at first run, so users get the
latest published versions automatically.

For v0.1.x the release is manual. Automation is deferred until friction
warrants it.

## See also

- Design rationale: [`docs/DRAFT-005-cleepi-toolkit-v0.1.0/spec.md`](../../docs/DRAFT-005-cleepi-toolkit-v0.1.0/spec.md)
- Release notes: [`CHANGELOG.md`](./CHANGELOG.md)