kit

Plugin kit from marketplace kitbash in coop-collective/kitbash. Commands read from the repo's manifest — 5 days ago.

Skills (28)

• api-keys

  Use when a Hono + D1 Worker needs long-lived prefixed API keys that people can create and revoke, stored as HMAC.

• cf-analytics

  Use when a Hono Worker should send first-party analytics (signed server events, exact facts, logs, browser events through a relay) to a Canvalytics ingest instead of a hosted vendor.

• cf-email-sender

  Use when a Worker must send its own transactional mail (codes, invitations) through Cloudflare Email Service, printed in dev and refused in production when unconfigured.

• cli-oauth-login

  Use when a Hono + D1 Worker should let a person's own CLI or MCP client sign in with their account over OAuth 2.1 (browser, PKCE) instead of a pasted token, with revocable per-CLI grants.

• cloudflare-container

  Install an authenticated Cloudflare Container with a Bun, Go or Rust runtime.

• crypto-utils

  Use when Worker code must keyed-hash a secret (codes, tokens, API keys) with a pepper, compare secrets in constant time, or mint unbiased codes, tokens and ids.

• d1-rate-limit

  Use when a Hono + D1 Worker needs shared rate limits (login, code sending, API keys) that fail closed in production.

• email-code-auth

  Use when a Hono + D1 Worker needs passwordless email-code sign-in (sign-up included) and opaque, revocable bearer tokens for apps, CLIs or MCP clients.

• hibernating-websocket

  Install a tenant-scoped hibernating Durable Object room, authorized upgrade handler, browser client and real workerd tests into an existing Worker.

• jwt-session-cookie

  HKDF-derived HS256 browser JWT cookies with uncached D1 version and logout revocation checks for Hono Workers.

• member-profiles

  Private-by-default profiles with unique handles, safe field projection and revision checks.

• orgs-roles-invites

  Use when a Hono + D1 app needs workspaces shared by several people, with owner/admin/member roles, email invitations and every request scoped to one org.

• public-edge-cache

  Explicit Cache API fallback for public GET representations behind an always-executed Worker gateway.

• r2-private-uploads

  Small private R2 attachments with bounded bodies and tenant-derived storage keys.

• session-cookie

  Revocable browser cookie sessions for a Hono Worker and D1.

• tiered-result-cache

  Typed read-through result caching through edge Cache API, optional KV, and loaders for R2, D1, Durable Objects, Analytics Engine or other JSON sources.

• vitest-workerd-harness

  Use when a Hono + D1 Worker needs tests that run in workerd with migrations applied, or a test proving new migrations keep production rows.

• clean-code-rust

  Use when explicitly assigned a post-merge Rust maintenance review or a specific agent-debugging, correctness, or performance improvement. Investigate ownership, task lifecycle and measured costs without enforcing cosmetic Clean Code rules. Not a default instruction for ordinary Rust edits.

• clean-code-typescript

  Use when explicitly assigned a post-merge TypeScript maintenance review or a specific agent-debugging, correctness, or performance improvement. Diagnose concrete obstacles, make justified changes, and verify behavior. Not a default instruction for ordinary feature edits.

• page-delivery

  Use when explicitly assigned a post-merge page-rendering or caching review, including vinext SSG, SSR, shared-data freshness, repeated requests and public leaderboards. Choose and verify a strategy per route. Not a default feature-building or site-wide optimization instruction.

• kitbash-accounts

  Set up company service accounts and OAuth applications using Agent Vault for automation access and Infisical for application credentials. Use when the user requests provider onboarding, account access, or a readiness check for an account-manager bot.

• kitbash-bootstrap

  Bootstrap a new repository from Kitbash's Worker, vinext or local Rust server presets, choosing compatible blocks, Git host and deployment settings. Use when starting a new app or service with Kitbash; use kitbash-use to add a block to an existing project.

• kitbash-harvest

  How to turn a feature that already works in a project into a reusable Kitbash block - choose the boundary, extract params for every app-specific literal, make sure tests travel with the code, redact secrets, keep the summary and guide within budget, and check the draft before publishing. Use when th

• kitbash-performance

  Use when auditing slow pages or adding repeatable browser, React/vinext, or Cloudflare performance regression checks. Choose measured budgets and preserve authorization, freshness, and runtime compatibility.

• kitbash-publish

  Publish a finished block to a separately configured legacy Kitbash registry, including visibility, license, scanner findings, and authentication. Use when the user explicitly requests that remote registry workflow; ordinary open-source toolkit contributions use Git pull requests.

• kitbash-secrets

  Generate application secrets, upload local credential files through MCP, deliver secrets to controllers, and provision GitHub or Worker access through Kitbash. Use when setting up secrets without returning their values in chat or tool results.

• kitbash-ui

  Consult the Kitbash Styrene Storybook (@kitbash/ui) for inspiration and reusable source before designing or building React UI, especially agent and AI product surfaces such as approvals, tool calls, plans, chat, model pickers, inputs, charts and onboarding. Use when building, restyling or reviewing

• kitbash-use

  Add a whole feature to an existing project from the local Kitbash block catalog - search, inspect, dry-run install, apply, adapt and verify, then contribute improvements upstream. Use when adding a feature that a block might cover or installing, adapting, upgrading or verifying a block. For a new re

Slash commands (5)

• /kit:bootstrap

  Create a Worker, vinext or local Rust server project with selected blocks and optional Git hosting.

• /kit:harvest

  Turn a feature already built in this project into a Kitbash block draft.

• /kit:install

  Install a Kitbash block into this project, dry run first, then adapt and verify.

• /kit:search

  Find a feature in Kitbash's local block catalog and explain its compatibility and dependencies.

• /kit:secrets

  Generate registered secrets or provision CI and Worker access through a configured broker, returning metadata only.

MCP servers (1)

• kitbash

  runs: node ${CLAUDE_PLUGIN_ROOT}/scripts/kit-mcp.mjs

Hooks (1)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}/hooks/session-start.mjs"

Similar plugins