Skip to content

local-install.md

Latest commit

 

History

History
88 lines (64 loc) · 2.57 KB

local-install.md

File metadata and controls

88 lines (64 loc) · 2.57 KB
Raw

Local install — make plain claude auto-load prism

This mirrors the superpowers-dev pattern: the bundled .claude-plugin/marketplace.json declares "name": "prism-dev", so the local checkout doubles as a single-plugin development marketplace. Adding it makes prism a first-class installed plugin — every plain claude session loads it, hooks fire, slash commands appear, settings persist in ~/.claude/settings.json.

One-time setup

In an interactive Claude Code session (any project, any cwd):

/plugin marketplace add /Users/prasad/Prasad/projects/prism
/plugin install prism@prism-dev

That's it. After install, ~/.claude/settings.json gets two updates:

{
  "extraKnownMarketplaces": {
    "prism-dev": { "source": { "source": "filesystem", "path": "/Users/prasad/Prasad/projects/prism" } }
  },
  "enabledPlugins": {
    "prism@prism-dev": true
  }
}

Quit the session. Run plain claude from anywhere — prism's SessionStart hook fires, the AI sees the plugin awareness, slash commands like /prism-status are available immediately. The UserPromptSubmit hook refreshes per-turn so achievement detection stays sharp.

Picking up edits without restarting

After editing skill markdown, hooks, or commands:

/reload-plugins

For changes to lib/cli.ts (the CLI is invoked via bun lib/cli.ts), no reload is needed — each invocation is a fresh subprocess.

Disabling temporarily

/plugin disable prism@prism-dev

Re-enable later with /plugin enable prism@prism-dev.

Uninstalling

/plugin uninstall prism@prism-dev
/plugin marketplace remove prism-dev

This restores plain claude to the pre-install state. Removes the entries from ~/.claude/settings.json and ~/.claude/plugins/known_marketplaces.json, but does not touch your data at ~/.prism/. To wipe that too:

bun /Users/prasad/Prasad/projects/prism/lib/cli.ts reset --yes --all

Why a separate prism-dev marketplace name

Once prism is published at claude.com/plugins, users will install via /plugin install prism@claude-plugins-official. The local-dev install path uses prism-dev as the marketplace name to avoid collision and so both can coexist on the same machine if you want to A/B test.

Per-session override (no install needed)

If you don't want to register prism into your global settings, just pass --plugin-dir per session:

claude --plugin-dir /Users/prasad/Prasad/projects/prism

This loads prism for that session only. Useful for trying new prism versions side-by-side.