tanphuc16797/workspace-wiki

★ 18HTMLAudience · developerComplexity · 2/5ActiveLicenseSetup · easy

Mindmap

mindmap
  root((Workspace Wiki))
    Inputs
      Project folder
      Workspace docs
      Stack packs
    Outputs
      Scoped context
      Slash commands
      Wiki updates
    Use Cases
      Isolate client projects
      Share team prompts
      Add reusable stack packs
    Tech Stack
      Claude Code
      Bash
      PowerShell
      HTML

mindmap root((Workspace Wiki)) Inputs Project folder Workspace docs Stack packs Outputs Scoped context Slash commands Wiki updates Use Cases Isolate client projects Share team prompts Add reusable stack packs Tech Stack Claude Code Bash PowerShell HTML

Things people build with this

USE CASE 1

Stop Claude Code from leaking rules between client A and client B by binding each repo to its own workspace via .claude/wiki.json.

USE CASE 2

Share a consistent set of agent prompts and pipeline rules across a team using the shared engine layer.

USE CASE 3

Layer reusable stack packs (frontend, web APIs, event-driven) on top of a workspace to inject the right patterns.

USE CASE 4

Use /use-wiki and /update-wiki around each task so the wiki stays current after every coding session.

Tech stack

HTMLBashPowerShellClaudeCode

Getting it running

Difficulty · easy Time to first run · 30min

Only Claude Code is officially supported and the install is a one-line script from the latest GitHub release, with an optional SHA256 verified path.

MIT license, so you can use, modify, and redistribute it freely, including in commercial work, as long as you keep the copyright notice.

In plain English

Workspace Wiki is an add-on for Claude Code, the command-line and editor extension version of Claude. It tries to solve a problem that hits teams who use Claude Code across many different projects or client companies at once: the assistant can start blurring context, pulling rules or names from one codebase into another. This repository sets up a structured knowledge layer that is locked to whichever project folder you are working in. The mental model has two parts. The shared engine holds general agent prompts, pipeline rules, and slash commands. Alongside it sit any number of workspaces, each one a separate sandbox of company or project knowledge. The active workspace is stored per project in a small .claude/wiki.json file, so switching codebases switches the context automatically. Between the engine and the workspace, you can also turn on packs, which are bundles of stack-specific patterns for things like web APIs, event-driven systems, frontend work, or product knowledge. The author lays out five non-negotiable rules. Workspace isolation is required, agents are fed runtime context rather than just static documents, packs act as reusable reasoning modules, only Claude Code is officially supported, and knowledge is prioritised in a fixed order with contracts at the top and general domain knowledge at the bottom. The audience the author has in mind is teams running multiple projects, tech leads who want consistent agent output, and solo builders who want repeatable workflows. Installation is by a one-line curl or PowerShell command that pulls a script from the latest GitHub release, with a separate verified-install path that checks SHA256 hashes first. Daily use is through slash commands inside Claude Code, such as /list-workspaces, /switch-workspace, /use-wiki for starting a task, and /update-wiki after coding. Onboarding guides are published in Vietnamese and English through GitHub Pages. The project is MIT licensed and described as best-effort and may move to maintenance mode if the maintainer's capacity changes.

Copy-paste prompts

Prompt 1

Install Workspace Wiki on macOS with the verified curl command, then create a workspace called acme-saas bound to ~/code/acme.

Prompt 2

Write a .claude/wiki.json that activates the acme-saas workspace plus the web-api and frontend packs for the current repo.

Prompt 3

Explain the five non-negotiable rules from the README in plain English and how a tech lead should police them in code review.

Prompt 4

Switch active workspace mid-session with /switch-workspace and show how Claude Code picks up the new context without restart.

Prompt 5

Compare Workspace Wiki to CLAUDE.md files and to Cursor rules for managing multi-project context on the same machine.

Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.