Installation

Prerequisites

• Claude Code installed and authenticated
• Node.js 18+
• git

No other tooling required. The plugins themselves are markdown files and YAML - no build step, no npm install.

Clone the repo

git clone https://github.com/hjemmesidekongen/ai.git
cd ai

Set up the marketplace registry

Claude Code discovers plugins through a marketplace registry file at ~/.claude/plugins/known_marketplaces.json. You need to add an entry pointing to the plugins/ directory in your clone.

Create or edit ~/.claude/plugins/known_marketplaces.json:

[
  {
    "path": "/absolute/path/to/ai/plugins"
  }
]

Replace /absolute/path/to/ai/plugins with the actual absolute path to the plugins/ directory in your clone (e.g., /Users/you/ai/plugins).

Then restart Claude Code. Plugins are discovered automatically on startup.

How plugin discovery works

Claude Code's plugin system works through the marketplace registry at ~/.claude/plugins/known_marketplaces.json. That file points to the plugins/ directory in this repo.

On startup, Claude Code:

1. Reads the marketplace registry to find the plugins/ directory
2. Scans each subdirectory for a .claude-plugin/plugin.json
3. Reads each plugin's ecosystem.json to discover skills, commands, agents, and hooks
4. Registers everything so it's available in the command palette and hook pipeline

Nothing is compiled or bundled. Each skill is a markdown file loaded on demand.

What gets installed

kronen (v0.3.0) - the foundation layer

• 40 skills: planning, brainstorm, verification, tracing, memory, code review, debugging, and more
• 13 commands: /plan:create, /plan:execute, /brainstorm:start, /brainstorm:decide, and others
• 12 agents: plugin-validator, security-auditor, error-detective, tdd-orchestrator, and others
• 23 hooks: PreToolUse (scope guard, push protection), PostToolUse (tracing, observations, compaction), Stop (verification, wave check, doc check), PreCompact (context snapshot), SessionStart (recovery, memory health), UserPromptSubmit (prompt grade)

smedjen (v0.2.0) - multi-agent development pipeline

• 62 skills across 9 categories: core execution, disciplines, tech knowledge (React, Next.js, NestJS, Prisma, Expo, and more), integration, expo, studio knowledge
• 6 agents: dispatcher, frontend, backend, testing, security, reviewer
• 2 commands: /smedjen:scan, /smedjen:run

herold (v0.1.0) - task management and workplace integration

• 9 skills: Jira ingestion, contradiction detection, QA handover, PR workflows, bulk ingestion, project profiles
• 8 commands: /task:ingest, /task:start, /task:pr, /task:done, and others

Verify the installation

Run /help inside Claude Code. You should see commands listed under kronen, smedjen, and herold.

Try a quick smoke test:

# Should respond with plan status (even if no active plan exists)
/plan:status

# Should open a brainstorm session
/brainstorm:start

Check that hooks are active by attempting a direct push to main - it should be blocked with an explanation. That means the PreToolUse hooks registered correctly.

Updating

Pull the latest changes and clear the plugin cache:

git pull
rm -rf ~/.claude/plugins/cache/hjemmesidekongen-ai/

Then restart Claude Code.

The cache clear is not optional. Claude Code caches plugin contents aggressively, and stale cache causes hooks and skills to silently run old versions even after you pull. This is the most common source of "why isn't my change working" issues.

Troubleshooting

If something is not working after install, check the Troubleshooting page for common issues with plugins, hooks, MCP connections, cache, and session state.

See also

• Configuration - MCP servers, plugin settings, CLAUDE.md, and project profiles
• Initialize in a New Project - scan your codebase and run your first planning session
• Troubleshooting - fixes for common installation and runtime issues