rapidkit
v0.39.0
Published
Open-source workspace intelligence CLI for software systems: create, adopt, govern, verify, and align polyglot workspaces for humans, CI, IDEs, and AI agents.
Maintainers
Readme
RapidKit
Open-Source Workspace Intelligence for Software Systems
One workspace. One truth. Humans and AI aligned.
RapidKit turns scattered projects into a governed, agent-ready workspace.
It gives developers, CI, IDEs, and AI agents the same evidence-backed source of truth: workspace model, agent context, impact analysis, verification evidence, contracts, and release gates.
Start here
Install
npm install -g rapidkitor run without installing:
npx rapidkit --helpCreate a governed workspace
mkdir -p ~/rapidkit/workspaces
cd ~/rapidkit/workspaces
npx rapidkit create workspace platform --yes --profile polyglot --output .
cd platform
npx rapidkit bootstrap --profile polyglot
npx rapidkit create project
npx rapidkit create frontend nextjs my-web --yes
npx rapidkit workspace model --json
npx rapidkit workspace context --for-agent --json --write
npx rapidkit pipeline --json --strictAdopt an existing project
mkdir -p ~/rapidkit/workspaces
cd ~/rapidkit/workspaces
npx rapidkit create workspace platform --yes --profile polyglot --output .
npx rapidkit adopt /path/to/project --workspace ~/rapidkit/workspaces/platform
cd ~/rapidkit/workspaces/platform
npx rapidkit workspace model --json
npx rapidkit workspace context --for-agent --json --write
npx rapidkit pipeline --json --strictWhat you get
- A governed workspace boundary for projects, policies, reports, and contracts
- Native create for RapidKit-owned backend and frontend kits
- Adopt/import for existing repositories without moving source code
- Agent-ready context packs for Copilot, Cursor, Claude, Codex, and other tools
- Impact analysis and release gates backed by workspace evidence
- One shared truth for developers, CI, IDEs, and AI agents
Create planner
RapidKit does not pretend every technology is a native scaffold. It uses a create planner contract to choose the safest path:
| Lane | Use when | Result |
| ----------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| native-create | RapidKit owns the scaffold contract | Create the project with a first-class kit |
| external-create-adopt | The ecosystem has an official generator, but RapidKit does not own the post-create contract yet | Use the ecosystem generator, then adopt into Workspace Intelligence |
| adopt-only | The project already exists or native create is not supported | Register, model, verify, and govern the project without scaffolding it |
Native create includes FastAPI, NestJS, Go, Spring Boot, .NET, and official frontend generators such as Next.js, Vite, Nuxt, Angular, Astro, Remix, and SvelteKit.
External ecosystems such as WordPress, Laravel, Symfony, Rails, and generic PHP projects can still enter RapidKit through adopt/import and receive workspace model, context, impact, doctor, and release governance.
Details: docs/create-planner-capabilities.md.
Workspace Intelligence
Most AI tools understand:
- Files
- Functions
- Repositories
Production systems require understanding:
- Ownership
- Architecture
- Dependencies
- Operational context
- Verification requirements
- Change impact
RapidKit adds the missing layer:
Workspace Intelligence.
One workspace. One truth. Humans and AI aligned.
A shared, evidence-backed understanding of software systems for developers, CI pipelines, IDEs, and AI agents.
In RapidKit, Workspace Intelligence is not a chat feature. It is the deterministic workspace layer behind the CLI:
- Model — what projects, runtimes, frameworks, commands, policies, contracts, and evidence exist
- Context — what AI agents and IDEs should know before giving advice
- Impact — what changed and which projects, commands, and release gates are affected
- Verify — which evidence proves the workspace is ready, blocked, or needs attention
- Sync — how developers, CI, Workspai, and AI agents stay grounded in the same truth
From Code to Shared Understanding
How RapidKit transforms projects and repositories into workspace intelligence for developers, CI, and AI agents.

Mermaid source for GitHub docs: from-code-to-shared-understanding.md.
RapidKit provides the workspace intelligence engine: model, context, impact, verification, evidence, contracts, and governance.
Workspai provides the VS Code experience on top of that foundation.
For the visual experience, install the Workspai VS Code extension.
Table of contents
- Start here
- Create planner
- Workspace Intelligence
- From Code to Shared Understanding
- Typical workflows
- Mental model
- Workspace Intelligence Commands
- Requirements
- Install
- Project workflows
- CI & evidence
- Workspai ecosystem
- VS Code extension
- Documentation
- Development
- Troubleshooting
- License
Typical workflows
| Question | Command |
| --------------------------------------------- | ---------------------------------------------- |
| What projects exist in this workspace? | workspace model --json |
| What context should AI agents receive? | workspace context --for-agent --json --write |
| What breaks if I change this? | workspace impact --from <snapshot> |
| Can I safely release? | pipeline --json --strict |
| How do I align AI tools and CI? | workspace agent-sync --write |
| How do I onboard an existing project? | adopt |
| How do I bring repositories into a workspace? | import |
Existing project
npx rapidkit adopt /path/to/project --workspace /path/to/workspace
npx rapidkit workspace model --jsonAgent-ready workspace
npx rapidkit workspace context --for-agent --json --write
npx rapidkit workspace agent-sync --write --refresh-contextRelease verification
npx rapidkit pipeline --json --strictAdopt in place
npx rapidkit adopt /path/to/project --workspace /path/to/workspace --json
npx rapidkit adopt --json # from inside the project folderWorkspace layout
~/.rapidkit/workspaces.json
~/rapidkit/workspaces/
workspai/ # managed default (standalone, import, and adopt fallback)
my-workspace/ # user-created workspacesNew workspaces go under ~/rapidkit/workspaces/<name>. Legacy ~/Workspai/rapidkits/* paths remain registered. Use --output <parent-dir> for a custom parent.
Mental model
Two-layer model
First-class engine kits → FastAPI and NestJS (modules + deep generation)
Workspace intelligence → frontend apps, Go, Spring, .NET, adopted/imported reposRapidKit treats the workspace as the operating boundary: policy, registry, evidence, contracts, and release readiness. Projects can live inside the workspace or be adopted from outside.
workspace/
.rapidkit/workspace.json
.rapidkit/reports/
services/api/
external-project/
.rapidkit/project.json
.rapidkit/adopt.jsonEvery tool gets the same answers: what projects exist, what stack they use, which commands are safe, what evidence exists, and what context agents should receive.
Workspace Intelligence Commands
Workspace Intelligence provides a shared understanding of projects, dependencies, operational context, and release readiness for developers, CI pipelines, and AI agents.
| Command | Purpose |
| ------------------------------------------------- | ---------------------------------------------------------------- |
| workspace model [--cache\|--incremental] --json | Canonical workspace model (graph-aware, incremental rebuilds) |
| workspace context --for-agent --json --write | Agent-ready context pack + auto agent grounding sync |
| workspace agent-sync --write | Cross-tool grounding (AGENTS.md, Copilot, Cursor, Claude, INDEX) |
| workspace snapshot --json | Persist model snapshot |
| workspace diff --from <file\|git[:ref]> --json | Diff against snapshot or git |
| workspace impact --from <file> --json | Graph-aware transitive blast-radius evidence |
| workspace verify [--strict] --json | Definitive verification gate (subgraph + freshness + policy) |
| workspace graph <emit\|explain\|dot\|mermaid> | Inspect and visualize the dependency graph |
| workspace watch [--json] [--once] | Daemon mode: keep model + graph in memory, stream change events |
JSON schemas: contracts/workspace-intelligence/. Details: commands-reference.md.
Graph-aware intelligence engine
The workspace model carries a deterministic, first-class dependency graph that
impact, verify, and graph all reason over — so the same evidence drives blast
radius, gating, and visualization:
- Transitive blast radius —
workspace impactreports each affected project'sdistance,path, andviaedge back to the change, plus centrality-weighted critical-path hotspots. - Whole-subgraph gate —
workspace verifygates the changed projects and their transitive dependents, surfaces graph integrity issues (cycles, dangling edges, orphans), and emits a structuredgate(passed/mode/exitCode/reasons). - Transitive freshness — a deterministic
fresh | stale | unknownverdict chained through the graph: a dependency change makes every dependent stale, not just by timestamp. - Policy violations — model/contract violations are surfaced as structured
policyViolations[](not just an exit code) so IDEs and CI can render blockers. - Health history — every verify run appends to a bounded
.rapidkit/reports/workspace-intelligence-history.jsonring buffer for trends. - Fast rebuilds —
workspace model --cache/--incrementalreuse unchanged project models and re-infer only incident edges, keyed by a structuralinputsHash. - Watch / daemon —
workspace watchkeeps the model + graph in memory and streams deterministicworkspace-watch-event.v1change events (changed projects, graph edge deltas, structural hash) via fast incremental rebuilds.
Agent grounding (CLI-only, no extension required)
RapidKit can sync cross-tool instruction files so Copilot, Cursor, Claude Code, Codex, Grok, and other agents read the same evidence before guessing:
# Full sync: refresh context pack + INDEX + AGENTS.md + Copilot/Cursor/Claude hooks
npx rapidkit workspace agent-sync --write --refresh-context
# Context pack write also syncs grounding by default
npx rapidkit workspace context --for-agent --json --write
# CI strict gate (fail if required reports missing/stale)
npx rapidkit workspace agent-sync --write --strict --json| Artifact / file | Purpose |
| -------------------------------------------------------- | ------------------------------------------------------- |
| .rapidkit/reports/INDEX.json | Read order, blockers, report timestamps |
| .rapidkit/reports/workspace-context-agent.json | Canonical agent context pack |
| .rapidkit/AGENT-GROUNDING.md | Tool-agnostic grounding doc |
| AGENTS.md | Open standard for all agents (managed RapidKit section) |
| .github/copilot-instructions.md | GitHub Copilot / VS Code Chat always-on rules |
| .github/instructions/rapidkit-evidence.instructions.md | Copilot scoped rules for .rapidkit/** |
| .github/prompts/rapidkit-diagnose.prompt.md | Copilot reusable diagnose prompt |
| .github/skills/rapidkit-grounding/SKILL.md | Copilot agent skill workflow |
| .cursor/rules/rapidkit-grounding.mdc | Cursor always-on project rule |
| CLAUDE.md | Claude Code entry (@AGENTS.md + managed notes) |
| .claude/rules/rapidkit-evidence.md | Claude Code scoped evidence rules |
Agents cannot be forced probabilistically — but this stack maximizes the chance they read reports first, even when the user talks to Copilot directly without Workspai.
Skip auto-sync after context write: --no-agent-sync. Target specific ecosystems: --target copilot,cursor,claude.
After pipeline, grounding syncs automatically (refresh context + INDEX + hooks). Disable with --no-agent-sync or RAPIDKIT_NO_AGENT_SYNC=1.
CI template: docs/examples/ci-agent-grounding.yml.
Requirements
- Node.js
>= 20.19.6 - Python
>= 3.10(for Python/Core workflows) - Java 21+, Go, .NET SDK 8+ (optional, per stack)
Install
npm install -g rapidkit
# or
npx rapidkit --helpProject workflows
I already have a project
npx rapidkit adopt /path/to/project --workspace /path/to/workspace
npx rapidkit import ../orders-api --workspace ./platform
npx rapidkit workspace model --json
npx rapidkit doctor workspace --jsonI want a new project
mkdir -p ~/rapidkit/workspaces
cd ~/rapidkit/workspaces
npx rapidkit create workspace platform --yes --profile polyglot --output .
cd platform
npx rapidkit bootstrap --profile polyglot
npx rapidkit create project # interactive kit picker
npx rapidkit create frontend nextjs my-web --yes
cd <project-name> && npx rapidkit init && npx rapidkit devBackend kits: fastapi.standard, nestjs.standard, springboot.standard, gofiber.standard, dotnet.webapi.clean, and more.
Frontend: create frontend nextjs|remix|vite-react|angular|astro|… or create project frontend.nextjs <name>.
Shortcut: npx rapidkit platform (interactive workspace wizard).
I want CI or release gates
npx rapidkit pipeline --json --strictStages individually: workspace sync, doctor workspace --ci, analyze --strict, readiness --strict, autopilot release.
CI & evidence
| Stage | Report |
| --------- | --------------------------------------------------- |
| Pipeline | .rapidkit/reports/pipeline-last-run.json |
| Doctor | .rapidkit/reports/doctor-last-run.json |
| Analyze | .rapidkit/reports/analyze-last-run.json |
| Readiness | .rapidkit/reports/release-readiness-last-run.json |
| Autopilot | .rapidkit/reports/autopilot-release-last-run.json |
Common workspace commands:
npx rapidkit doctor workspace
npx rapidkit workspace agent-sync --write --refresh-context
npx rapidkit setup <python|node|go|java|dotnet> [--warm-deps]
npx rapidkit workspace list
npx rapidkit cache <status|clear|prune|repair>
npx rapidkit mirror <status|sync|verify|rotate>Full syntax: docs/commands-reference.md. CI workflows: docs/ci-workflows.md — includes .github/workflows/ci.yml, .github/workflows/workspace-e2e-matrix.yml, .github/workflows/windows-bridge-e2e.yml, .github/workflows/e2e-smoke.yml, .github/workflows/security.yml.
Workspai ecosystem
RapidKit and Workspai form a single workspace intelligence platform.
RapidKit provides the workspace intelligence engine: model, context, impact, verification, evidence, contracts, and governance.
Workspai — Workspace + Intelligence — provides the VS Code surface: dashboard, sidebar, Incident Studio, AI workflows, and developer-facing workspace operations.
| Component | Repository | Role | | --------- | ---------------------------------------------------------------------- | ------------------------------------------- | | CLI | rapidkit-npm | Commands, governance, adoption, CI evidence | | VS Code | rapidkit-vscode | Workspai dashboard, sidebar, AI studio | | Core | rapidkit-core | Python engine, modules, doctor | | Examples | rapidkit-examples | Starter workspaces |
VS Code extension
Workspai is the VS Code experience for RapidKit workspace intelligence.
Search Workspai in the marketplace or install via:
ext install rapidkit.rapidkit-vscode.
| Feature | CLI | Extension |
| ------------------------------- | ---------------------------- | ------------------------------- |
| Create / adopt / import | Yes | Guided wizards |
| Workspace model / context | Yes | Dashboard + AI scope |
| Cross-tool agent grounding | Yes (workspace agent-sync) | Send-to-Copilot / Ask Studio UX |
| Enterprise evidence loop | Partial | Full dashboard |
| Module catalog (FastAPI/NestJS) | Limited | Browser UI |
The extension invokes this npm CLI. For the latest adopt and create frontend features, install matching CLI version: npm install -g rapidkit@latest or npm link from this repo (Development).
Documentation
| Doc | Description | | ------------------------------------------------------------------------ | ------------------------------------------- | | docs/README.md | Documentation index | | docs/commands-reference.md | Full command syntax | | docs/workspace-operations.md | Import, adopt, snapshots, archives, infra | | docs/workspace-run.md | Polyglot fleet orchestration | | docs/doctor-command.md | Doctor scopes, CI exit codes, JSON evidence | | docs/OPEN_SOURCE_USER_SCENARIOS.md | Role-based workflows | | docs/SETUP.md | Maintainer setup | | docs/SECURITY.md | Security policy | | docs/config-file-guide.md | User configuration | | CHANGELOG.md | Version history |
Development
npm ci && npm run build && npm run test
npm run install:local # link CLI globally for manual testingContributors: docs/DEVELOPMENT.md, docs/ci-workflows.md.
npm run prepack validates embeddings and CLI surfaces before npm pack / npm publish.
Troubleshooting
| Problem | Quick check | Fix |
| --------------------------------------- | ---------------------------------- | ------------------------------------------------ |
| python3 not found | python3 --version | Install Python 3.10+ |
| setup --warm-deps skipped | Project markers in cwd | Run from target project directory |
| Strict policy blocks command | .rapidkit/policies.yml | workspace policy set … |
| npm audit fix --force downgrades tsup | package.json | Do not use --force; keep tsup@^8.5.1 |
| Security audit fails on esbuild | npm audit --audit-level=moderate | Keep esbuild override in package.json |
| Doctor output stale | Report timestamps | Re-run doctor workspace or doctor project |
| Copilot ignores workspace evidence | Missing grounding files | workspace agent-sync --write --refresh-context |
| Agent grounding strict CI failed | Stale/missing reports | Run governance chain then re-sync |
| Affected run scope wrong | Git ref | Use --since <ref> explicitly |
License
MIT — see LICENSE.
