npm - @polderlabs/bizar - Versions diffs - 9.0.0 → 10.0.7 - Mend

@polderlabs/bizar 9.0.0 → 10.0.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1306) hide show

package/.claude/worktrees/kanban-overhaul/.claude/agents/_shared/CLAUDE_TOOLS.md DELETED Viewed

@@ -1,412 +0,0 @@
-# Claude Code Tools Reference
-> **Read this before calling any Claude Code tool.** Calling tools
-> with the wrong argument shape is one of the top causes of
-> "max consecutive mistakes reached" session aborts. When in doubt,
-> read this file.
-Every Bizar agent runs inside a Claude Code session and has access
-to Claude Code's built-in tools. This file is the single source of
-truth for **how to call every Claude Code tool correctly**.
-For a list of what each tool does, see
-https://code.claude.com/docs/en/agent-sdk/overview. This file focuses
-on **argument shapes** — the part that, when wrong, silently fails
-or gets flagged as a "mistake".
----
-## Quick reference (cheat sheet)
-| Tool | Required fields | Common mistake |
-|---|---|---|
-| `Read` | `file_path` | passing a dir instead of a file |
-| `Glob` | `pattern` (or `path` + `pattern`) | forgetting `pattern` glob for nested lookups |
-| `Grep` | `pattern` | passing non-regex without `glob` filter |
-| `Edit` | `file_path`, `new_string` (and `old_string`) | `old_string` not matching whitespace exactly |
-| `Write` | `file_path`, `content` | writing a directory path |
-| `Bash` | `command` | shell redirects (`>`, `>>`) sometimes blocked; default 2-min timeout, max 10 min |
-| `WebFetch` | `url`, `prompt` | passing a non-HTTP URL |
-| `WebSearch` | `query` | none common |
-| `AskUserQuestion` | `question`, `options` (array of 2–4) | **`options: null` or empty → silent failure** |
-| `Skill` | `skill` | passing a skill that isn't installed |
-| `Agent` | `subagent_type`, `prompt` (and `description`) | passing a name not declared in `.claude/agents/` |
----
-## `Read`
-Read a file (or a slice of one).
-```json
-{
-  "file_path": "/abs/path/to/file.ts",
-  "offset": 10,
-  "limit": 50
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `file_path` | string | **yes** | Absolute path. Reading a directory errors. |
-| `offset` | number | no | 1-based line number to start at. Defaults to 1. |
-| `limit` | number | no | Lines to read from offset. If omitted, reads to EOF. |
-**Failure modes:** `file_path` to a directory errors. `file_path` to a non-existent file errors. Don't pass `offset` > file line count.
----
-## `Glob`
-List files matching a glob pattern.
-```json
-{
-  "pattern": "**/*.ts",
-  "path": "/abs/path/to/project"
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `pattern` | string | **yes** | Glob, e.g. `*.ts`, `src/**/*.tsx`. |
-| `path` | string | no | Absolute root. Defaults to the working directory. |
-**Failure modes:** Invalid glob syntax errors. The output excludes common build dirs (node_modules, .git, dist, build, .next, coverage, __pycache__, .venv, target, out, bin, obj) by default.
----
-## `Grep`
-Regex search across files (ripgrep under the hood).
-```json
-{
-  "pattern": "class \\w+ extends Plugin",
-  "path": "/abs/path/to/project",
-  "glob": "*.ts",
-  "output_mode": "files_with_matches",
-  "-n": true
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `pattern` | string | **yes** | Treated as a regex. Use `rg` syntax. |
-| `path` | string | no | Defaults to cwd. Absolute path recommended. |
-| `glob` | string | no | Include filter, e.g. `*.ts`, `*.{ts,tsx}`. |
-| `output_mode` | string | no | `content` (with `-n` for line numbers), `files_with_matches`, or `count`. |
-| `-n` | bool | no | Show line numbers (with `output_mode: content`). |
-**Failure modes:** An invalid regex errors. Path to a file errors when used without a glob filter — must be a directory.
----
-## `Edit`
-The workhorse edit tool.
-### Mode 1 — `old_string` / `new_string` (replace a block)
-```json
-{
-  "file_path": "/abs/path/to/file.ts",
-  "old_string": "export const foo = 1;\n",
-  "new_string": "export const foo = 2;\n"
-}
-```
-- `old_string` must match EXACTLY including whitespace and trailing newline.
-- If `old_string` is not found → tool returns an error like `String to replace not found in file`.
-- If `old_string` matches more than once → tool returns `Found multiple matches` or similar; refine.
-**This is the #1 cause of agent mistakes.** When in doubt:
-1. First call `Read` on the file
-2. Copy the exact bytes (including indentation and trailing newline)
-3. Make the smallest possible edit
-### Mode 2 — `replace_all` (replace every occurrence)
-```json
-{
-  "file_path": "/abs/path/to/file.ts",
-  "old_string": "foo",
-  "new_string": "bar",
-  "replace_all": true
-}
-```
-Use when the same exact string appears multiple times and you genuinely want every occurrence replaced.
-### File does not exist (use `Write` instead)
-If the file does not exist, use the `Write` tool — `Edit` requires the file to exist.
-**Common failures:**
-- "String to replace not found" — whitespace mismatch. Re-read the file and copy the bytes exactly.
-- "multiple matches" — your `old_string` is too generic. Make it more specific (include more surrounding context) or use `replace_all` deliberately.
-- Missing trailing `\n` — `new_string` and `old_string` must end with `\n` if the surrounding context does.
----
-## `Write`
-Create or fully overwrite a file.
-```json
-{
-  "file_path": "/abs/path/to/new-file.ts",
-  "content": "// brand new file content\n"
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `file_path` | string | **yes** | Absolute path. Parent dirs are NOT created automatically. |
-| `content` | string | **yes** | Full file body. |
-**Common failures:**
-- Path to a directory errors.
-- Parent directory missing → creates the file in cwd with the basename, or errors. Use `Bash` to `mkdir -p` first.
----
-## `Bash`
-Run a shell command.
-```json
-{
-  "command": "ls -la /tmp",
-  "timeout": 30000,
-  "description": "List /tmp contents"
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `command` | string | **yes** | Passed to `/bin/bash -c` (Linux/macOS) or `cmd /c` (Windows). |
-| `timeout` | number | no | **Max 600,000 ms (10 min).** Default ~120,000 (2 min). |
-| `description` | string | no | Short human-readable summary shown in the TUI (recommended). |
-**Critical constraints:**
-- **No shell redirects** (`>`, `>>`, `<`) in some runtimes / sandboxes. Use `Edit` or `Write` to author files.
-- Long-running processes hit the timeout. For >10 min tasks, use the `Agent` tool in background mode (`run_in_background: true`) to spawn a sub-agent.
-- The `command` string IS a shell command. Quote carefully. Use `&&` to chain, `;` to sequence, `|` to pipe.
-**Common failures:**
-- `command not found` — the binary isn't on PATH. Use absolute path or `which <name>` first.
-- `Permission denied` — file isn't executable, or you're writing to a protected dir.
-- `timeout` — increase `timeout` (max 600,000) or move to a background agent.
----
-## `WebFetch`
-Fetch a URL and answer a prompt against it.
-```json
-{
-  "url": "https://example.com/docs",
-  "prompt": "Summarize the authentication section"
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `url` | string | **yes** | Must be HTTP/HTTPS. No `file://`. |
-| `prompt` | string | **yes** | The question you want the page answered against. |
-**Failure modes:** Non-HTTP URLs error. The fetch goes through Claude Code's content extractor; PDFs, JS-rendered pages, and login-walled sites may return partial content.
----
-## `WebSearch`
-Run a web search and return ranked results.
-```json
-{
-  "query": "Claude Code Agent SDK sub-agent routing"
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `query` | string | **yes** | Natural-language search. |
----
-## `AskUserQuestion`
-Ask the user ONE clarifying question with 2–4 options. **This is the most-misused tool.**
-```json
-{
-  "question": "Which database do you want to use?",
-  "options": [
-    { "label": "PostgreSQL", "description": "Recommended for relational + JSON" },
-    { "label": "MySQL", "description": "Traditional RDBMS" },
-    { "label": "SQLite", "description": "Embedded, no server" },
-    { "label": "MongoDB", "description": "Document store" }
-  ],
-  "header": "Database",
-  "multi_select": false
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `question` | string | **yes** | One question. Multi-question calls fail. |
-| `options` | array of 2–4 objects | **yes** | **MUST be 2–4 items, each with `label` + `description`.** |
-| `header` | string | no | Short (≤12 chars) shown in the picker chip. |
-| `multi_select` | bool | no | Allow multiple selections. Default false. |
-### ⚠️ CRITICAL — `options` is REQUIRED, not optional
-If you pass `options: []`, omit `options`, or pass strings instead of
-objects, Claude Code **silently rejects the call** and counts it as a
-mistake. After several such silent failures the session aborts.
-### When to use `AskUserQuestion`
-- A key implementation decision has multiple valid paths
-- The user said something ambiguous and you need to clarify before doing real work
-- You're about to make a destructive change (rm, drop table, force-push)
-### When NOT to use `AskUserQuestion`
-- You can decide safely using sensible defaults
-- The user's intent is clear from context
-- You're just confirming something you should have done already
-- The answer is in the codebase (use `Read` / `Grep` first)
-### Alternatives to `AskUserQuestion`
-- **Use multiple `Agent` calls in one message** to parallelize the investigation
-- **Use the `Agent` tool (background)** for long-running research
-- **Just pick a sensible default** and document it in your final response
-### Recovery from `AskUserQuestion` mistakes
-If you accidentally pass the wrong shape and the tool errors, **DO NOT
-retry the same broken call**. Instead:
-1. Switch to a sensible default
-2. Document the decision in your final response
-3. Let the user override later if they disagree
----
-## `Skill`
-Activate a skill.
-```json
-{
-  "skill": "commit",
-  "args": "Add auth bug fix"
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `skill` | string | **yes** | Exact skill name. Run `skills list` (or check `~/.claude/skills/`) to see available. |
-| `args` | string | no | Passed to the skill's runner. |
-**Failure modes:** Unknown skill name errors. Skills are case-sensitive.
----
-## `Agent`
-Dispatch a sub-agent. Claude Code's equivalent of Bizar's `task`
-and `bizar_spawn_background` tools.
-```json
-{
-  "subagent_type": "thor",
-  "prompt": "Implement the rate-limiter middleware in src/middleware/ratelimit.ts",
-  "description": "Implement rate limiter"
-}
-```
-Synchronous (default):
-```json
-{
-  "subagent_type": "thor",
-  "prompt": "Implement the rate-limiter middleware in src/middleware/ratelimit.ts",
-  "description": "Implement rate limiter",
-  "run_in_background": false
-}
-```
-Background (async, returns immediately):
-```json
-{
-  "subagent_type": "mimir",
-  "prompt": "Research the auth flow across the codebase. Cite file paths.",
-  "description": "Research auth flow",
-  "run_in_background": true
-}
-```
-| Field | Type | Required | Notes |
-|---|---|---|---|
-| `subagent_type` | string | **yes** | A Bizar agent name declared in `.claude/agents/<name>.md`: `odin`, `thor`, `tyr`, `heimdall`, `mimir`, `frigg`, `hermod`, `baldr`, `vor`, `vidarr`, `forseti`, `quick`, `agent-browser`, `semble-search`. |
-| `prompt` | string | **yes** | What to do. Be specific. |
-| `description` | string | no | Short summary shown in the TUI. |
-| `run_in_background` | bool | no | Default `false`. Set true for async dispatch. |
-**Failure modes:** Unknown `subagent_type` errors. Sync runs block until the sub-agent returns. Background runs return immediately; check status via the TUI or stop with `TaskStop`.
-### Sync vs async dispatch
-- **`Agent` (sync)** — blocks until the sub-agent returns. Use when the parent needs the result before continuing.
-- **`Agent` with `run_in_background: true`** — async, returns immediately. Use for long-running work that doesn't block the parent. Replaces Cline's `bizar_spawn_background`.
-### Coordinating multiple background agents
-When fanning out several research or exploration tasks, issue multiple `Agent` calls in the **same message** with `run_in_background: true`. Each runs in parallel. Collect results by either:
-- Waiting for the user to ask, then re-dispatching sync `Agent` calls that summarize the background work.
-- Reading the background agent's final summary when it completes.
----
-## Claude Code's other useful tools
-These are available in many Claude Code sessions but not declared
-in Bizar agents' `tools` frontmatter by default. Add them when the
-agent needs them:
-- **`TaskStop`** — stop a background `Agent` that's looping, stalling, or no longer relevant.
-- **`TodoWrite`** — track a multi-step plan in the agent's scratchpad. Use 3-7 items max; refine as you go.
-- **`NotebookEdit`** — edit Jupyter notebook cells. Rarely needed outside data work.
-- **`EnterWorktree` / `ExitWorktree`** — git worktree isolation. Only when explicitly requested.
-- **`WebSearch`** — covered above.
-These are documented at https://code.claude.com/docs/en/agent-sdk/overview.
----
-## Recovery: when you hit the mistake limit
-If Claude Code surfaces "max consecutive mistakes reached" and aborts the session:
-1. **Stop retrying the same broken call.** Each retry wastes a mistake.
-2. **Read this file** — most mistakes come from wrong argument shapes, not bad logic.
-3. **Use simpler tools** — `Read` instead of `Edit` for inspection; rewrite the whole file with `Write` for multi-line changes.
-4. **Spawn a fresh session** if the runtime is in a bad state.
----
-## Per-tool I/O contract
-All Claude Code tools return text via stdout-like output. Failed tools return either:
-- A structured error message (e.g. `String to replace not found in /path`)
-- An exception thrown back to the agent (which Claude Code wraps as a mistake)
-There is no `success: true|false` field. You must read the response text
-to know what happened.

package/.claude/worktrees/kanban-overhaul/.claude/agents/_shared/SKILLS.md DELETED Viewed

@@ -1,109 +0,0 @@
-# Bizar Skills - Reference
-Skills are specialized instruction sets that agents load before working on specific domains. They live as `SKILL.md` files in well-known directories and are injected into agent context when relevant.
-## What Skills Are
-A skill is a Markdown file with YAML frontmatter. The frontmatter declares a `description` that the agent matcher uses to decide when to load the skill. The body contains domain-specific knowledge, patterns, gotchas, and code examples.
-Example `SKILL.md`:
-```yaml
----
-name: my-skill
-description: Use when working with X. Covers Y and Z.
----
-# My Skill
-## When to use
-...
-## Key concepts
-...
-## Code examples
-...
-## Common gotchas
-...
-```
-## Where Skills Live
-| Path | Source | Priority | Notes |
-|---|---|---|---|
-| `~/.claude/skills/<name>/SKILL.md` | User / System | Highest | User-overridable builtins |
-| `~/.agents/skills/<name>/SKILL.md` | User-added | High | Installed via `skills add` |
-| `bizar-dash/skills/<name>/SKILL.md` | Shipped | Medium | Ships with BizarHarness package |
-| `.agents/skills/<name>/SKILL.md` | Project | Low | Project-local skills |
-| `.claude/skills/<name>/SKILL.md` | Project | Lowest | Project-local skills |
-When the same skill name appears in multiple places, the highest-priority source wins.
-## Discovering Skills
-Use the `skills` CLI:
-```bash
-# List installed skills
-skills list --json
-# Search for a skill
-skills search "react"
-# Install from a repository
-skills add owner/repo -s "skill-name" -y
-```
-Known repositories:
-- `vercel-labs/skills` - find-skills, skill-creator, general tools
-- `vercel-labs/agent-skills` - React, Next.js, frontend performance
-- `shadcn/ui` - shadcn/ui components
-- `supabase/agent-skills` - Postgres, Auth, Edge Functions
-- `mattpocork/skills` - TypeScript, TDD
-- `anthropics/skills` - Claude patterns, agents
-- `leonxlnx/taste-skill` - design, UI/UX
-## Shipped Bizar Skills
-These skills ship with BizarHarness and are available immediately:
-| Skill | Description |
-|---|---|
-| `bizar` | Norse-pantheon multi-agent system, Odin routing, agent tiers |
-| `agent-baseline` | Always-on rules: Semble, Skills CLI, loop guard, copyright |
-| `self-improvement` | .bizar/AGENTS_SELF_IMPROVEMENT.md protocol |
-| `obsidian` | Bizar Memory Service (Obsidian + Git + LightRAG) |
-| `minimax` | MiniMax provider, multi-key rotation, usage tracking |
-| `providers` | Provider subsystem, backup keys, auto-add wizard |
-| `chat` | Chat + claude session integration |
-| `usage` | Token usage monitoring, cost estimation, MiniMax usage dashboard |
-| `skills-cli` | skills CLI reference, skill repos, discovery protocol |
-| `lightrag` | LightRAG integration, claude-code-native defaults, indexing |
-| `sdk` | @polderlabs/bizar-sdk on Cloudflare Workers |
-## Skill Loading
-Agents check skill relevance at dispatch time. You can also load a skill explicitly in conversation using the `Skill` tool:
-```
-Load the `minimax` skill before we discuss multi-key rotation.
-```
-## Adding a Project Skill
-Create a skill directory in your project:
-```bash
-mkdir -p .agents/skills/my-project-skill
-cat > .agents/skills/my-project-skill/SKILL.md << 'EOF'
----
-name: my-project-skill
-description: Use when working on my project's specific domain X.
----
-# My Project Skill
-...
-EOF
-```
-Project skills are picked up automatically on next session start.

package/.claude/worktrees/kanban-overhaul/.claude/agents/agent-browser.md DELETED Viewed

@@ -1,80 +0,0 @@
----
-name: agent-browser
-description: agent-browser — Browser-driven E2E verification. Drives Chrome for Testing via the agent-browser CLI. No-edit permissions. Use for end-to-end verification of web apps, taking screenshots, clicking/filling forms, snapshotting accessibility trees.
-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch
-model: bork/MiniMax-M2.7
----
-You are agent-browser — the silent observer. You drive a real browser via the agent-browser CLI to verify that web apps actually work. You never edit code. Your only output is verification.
-## When You Are Used
-- Odin dispatches you after a UI change to verify the dashboard works end-to-end
-- "Take a screenshot of the running app at /chat"
-- "Click button X, fill input Y, verify the result"
-- Any task that needs a real browser interaction to confirm
-## Tools Available
-- **Primary: `agent-browser` (native Rust CLI)** — installed at `~/.local/bin/agent-browser` from https://github.com/vercel-labs/agent-browser. Use it via Bash:
-  ```bash
-  agent-browser open example.com
-  agent-browser snapshot --json               # accessibility tree with refs
-  agent-browser click @e2                    # click by ref
-  agent-browser fill @e3 "test@example.com" # fill by ref
-  agent-browser get text @e1
-  agent-browser screenshot page.png
-  agent-browser close
-  ```
-  100+ typed CLI commands are available; run `agent-browser --help` for the full list.
-- **MCP stdio server:** the agent-browser binary also ships an MCP stdio server. Claude Code can register it as an MCP tool server so any tool call flows through it natively. See `.claude/mcp.json`.
-- **Natural-language `chat`:** `agent-browser chat "open google.com and search for cats"` translates instructions into agent-browser commands and streams results. Requires `AI_GATEWAY_API_KEY`.
-- **Setup:** if the daemon is not running, `cli/agent-browser-up.sh start` (or `bizar browser-agent-up start`).
-- The agent-browser SKILL.md lives at `~/.claude/skills/agent-browser/SKILL.md` — read it on first use.
-- Read, Glob, Grep
-- Bash for `npx bizar dev`, `curl`, and `agent-browser …` calls
-- WebFetch, WebSearch
-- Edit/Write denied — you cannot modify the project
-## Workflow
-1. **Start the app if needed.** `npx bizar dev` or the project's dev command. Wait for the port to be ready.
-2. **Open the URL.** `agent-browser open <url>` (or `goto`, `navigate`). The daemon attaches and Chrome becomes ready in seconds.
-3. **Take a snapshot.** `agent-browser snapshot --json` returns the accessibility tree with refs like `@e1`, `@e2`. Every subsequent interaction targets a ref.
-4. **Interact.** `agent-browser click @e2`, `agent-browser fill @e3 "hello"`, `agent-browser type @e4 "foo"`.
-5. **Verify.** `agent-browser get text @e1` or `agent-browser screenshot page.png`.
-6. **Close.** `agent-browser close` when done.
-## Refs vs. Selectors
-Prefer **refs** (`@e2`) — they're stable across page snapshots and don't depend on DOM structure or class names. Use selectors (`"#submit"`, `role=button[name=Submit]`) only as a fallback when the ref hasn't been captured yet.
-## Plugin system
-agent-browser supports plugins — e.g. `agent-browser-plugin-vault` for
-credential storage. Configure in `agent-browser.json`:
-```json
-{
-  "plugins": [
-    { "name": "vault", "command": "agent-browser-plugin-vault",
-      "capabilities": ["credential.read"] }
-  ]
-}
-```
-## Lessons from v5.x browser-harness (deprecated)
-The previous browser-harness (Python + uv-installed + daemon via shell) was
-retired in v6.0.0 because:
-- agent-browser is **10× faster** to start (Rust vs Python)
-- agent-browser ships **MCP stdio server** natively (browser-harness didn't)
-- agent-browser has **self-healing snapshot**s (browser-harness required
-  manual element coordinates)
-- agent-browser has a **plugin ecosystem** (browser-harness had none)
-- vercel-labs integration with skills.sh + Vercel AI SDK + AI Gateway
-All v5.x browser-harness functionality is preserved as the agent-browser
-`open / snapshot / click / fill / screenshot / close` command set.

package/.claude/worktrees/kanban-overhaul/.claude/agents/baldr.md DELETED Viewed

@@ -1,49 +0,0 @@
----
-name: baldr
-description: Baldr — UI/UX design system specialist. Creates DESIGN.md files following Google's design.md standard. Aesthetic direction, typography, design tokens, anti-slop audits. Does not implement code.
-tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: bork/MiniMax-M2.7
----
-You are Baldr — the beautiful. You create design plans. You do NOT implement code — your output is a `DESIGN.md` file that Thor or Tyr will then execute.
-## When You Are Used
-- "Design a landing page for X"
-- "Audit the visual consistency of this codebase"
-- "Propose a color palette and typography for the app"
-- "Create a DESIGN.md"
-- Any task where the primary output is a design plan, not implementation
-## Process
-1. **Read the brief.** What is the product? Who is the audience? What is the desired feeling (cinematic / editorial / playful / brutalist / minimal)?
-2. **Audit existing assets.** If redesigning, run the 10-dimension visual audit (typography hierarchy, color discipline, spacing rhythm, motion language, etc.) before proposing changes.
-3. **Pick a direction.** Commit to one aesthetic. Anti-slop means avoiding: gratuitous gradients, glassmorphism, generic card grids, and the "tailwind default" look.
-4. **Write DESIGN.md** using Google's `design.md` standard:
-   - YAML tokens (colors, typography, spacing, radii, shadows, motion)
-   - Prose sections (aesthetic direction, anti-patterns banned, motion language, component composition rules)
-5. **List concrete deliverables.** What will Thor/Tyr build? List the files, components, and verification steps.
-## Output Style
-- The DESIGN.md is the deliverable. Write it to `DESIGN.md` in the project root.
-- Lead with the aesthetic direction in 2-3 sentences.
-- Show 1-2 reference images or mood-board descriptions inline.
-- Use code-fenced YAML for tokens.
-- End with a "What Thor/Tyr will build" checklist.
-## Tools Available
-- Semble search for existing UI patterns and component inventory
-- Read, Edit, Write, Glob, Grep
-- Bash for `npx skills add anthropics/skills --all -y` (frontend-design, taste-skill)
-- WebFetch, WebSearch for design inspiration and competitor research
-## Always-On Rules
-**Follow `.claude/agents/_shared/AGENT_BASELINE.md`** — it covers Semble, Skills CLI, Obsidian vault, loop guard, parallel execution, and the full general agent baseline.
-Your unique rule: you plan, Thor and Tyr implement. If asked to write code, refuse and tell the user to route the implementation to @odin.
-Claude Code tool shapes are documented in `.claude/agents/_shared/CLAUDE_TOOLS.md`. Read it before calling any tool.