# kira - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for kira. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0002` supported 0.86

## What It Can Do

- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md` Claim: `clm_0001` supported 0.86

## How to Start

- `curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_linux_amd64.tar.gz" \` Evidence: `scripts/registry-publish.md` Claim: `clm_0003` supported 0.86
- `curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=kira" | jq .` Evidence: `scripts/registry-publish.md` Claim: `clm_0004` supported 0.86
- `npx kira-mcp   # Ctrl-C once it starts waiting for input` Evidence: `TROUBLESHOOTING.md` Claim: `clm_0005` supported 0.86
- `npm install -g kira-mcp` Evidence: `TROUBLESHOOTING.md` Claim: `clm_0006` supported 0.86
- `git clone https://github.com/aibenyclaude-coder/Kira.git` Evidence: `USAGE.md` Claim: `clm_0007` supported 0.86
- `npx wrangler d1 create kira-events-prod` Evidence: `worker/README.md` Claim: `clm_0008` supported 0.86
- `npx wrangler d1 execute kira-events-prod --remote --file=migrations/0001_init.sql` Evidence: `worker/README.md` Claim: `clm_0009` supported 0.86
- `npx wrangler deploy` Evidence: `worker/README.md` Claim: `clm_0010` supported 0.86
- `npx wrangler d1 create kira-events-dev` Evidence: `worker/README.md` Claim: `clm_0011` supported 0.86
- `npx wrangler d1 execute kira-events-dev --local \` Evidence: `worker/README.md` Claim: `clm_0012` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Trial role matching first
- **Why**: This project is more of a role library; the core risk is picking the wrong role or treating role copy as execution capability. Trial role matching with Prompt Preview first, then decide whether to sandbox-import it.

### 30-Second Read

- **What to do now**: Trial role matching first
- **Minimum safe next step**: Trial role matching with Prompt Preview first; import in isolation only once satisfied
- **Do not trust yet**: Role quality and task fit cannot be trusted directly.
- **Continuing will touch**: Role selection bias, Command execution, Host AI configuration

### What You Can Trust Now

- **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0002` supported 0.86
- **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md` Claim: `clm_0001` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `scripts/registry-publish.md` Claim: `clm_0003` supported 0.86

### What You Cannot Trust Yet

- **Role quality and task fit cannot be trusted directly.** (unverified): A role library proves there are many roles; it does not prove each one fits your specific task or that a role produces high-quality results.
- **Do not treat role copy as real execution capability.** (unverified): Before install you can only judge whether the role description and task profile match; you cannot prove it can complete the task inside the host AI.
- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `CLAUDE.md`
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment.
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.

### What Continuing Will Touch

- **Role selection bias**: The user's judgment about which expert role should handle the task. Why: Picking the wrong role makes the AI answer from the wrong expert perspective, wasting time or misleading decisions.
- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md`
- **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `CLAUDE.md`
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md`
- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Use an interactive trial to verify the task profile and role match first; do not import the whole role library up front. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state.
- **Keep a record of the original role selection**: If output goes off-topic, you can return to the task-profiling stage and reselect a role instead of pushing on with the wrong one.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0013` inferred 0.45
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md` Claim: `clm_0014` supported 0.86
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md` Claim: `clm_0001` supported 0.86

### Context Scale

- Total files: 178
- Important-file coverage: 40/178
- Evidence index entries: 80
- Role / Skill entries: 34

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for kira, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat kira as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for kira, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 34 role / Skill / project-doc entries.

- **Kira** (project_doc): ! CI https://github.com/aibenyclaude-coder/Kira/actions/workflows/ci.yml/badge.svg https://github.com/aibenyclaude-coder/Kira/actions/workflows/ci.yml ! npm https://img.shields.io/npm/v/kira-mcp.svg https://www.npmjs.com/package/kira-mcp ! npm downloads https://img.shields.io/npm/dw/kira-mcp.svg https://www.npmjs.com/package/kira-mcp ! scars absorbed https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fraw.gi… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **Kira micro-benchmark** (project_doc): A dependency-free micro-benchmark for the two hot paths an agent hits on every call: lookup keyword → skills + scars and resolveRoute goal → ordered steps . It exists to catch performance regressions , not to produce a leaderboard. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `bench/README.md`
- **Kira — Client Examples** (project_doc): Copy-paste MCP config for the three most common clients. Each snippet is a complete, valid config — paste it, restart the client, done. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/README.md`
- **Kira maintainer scripts** (project_doc): Operational scripts run by the project maintainer. Not shipped in the npm package. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `scripts/README.md`
- **Kira Telemetry Worker** (project_doc): Cloudflare Worker that receives outcome reports from Kira MCP clients and exposes 30-day aggregate stats per skill. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `worker/README.md`
- **Kira — Project Rules** (project_doc): MCP server that auto-manages Skills how to do it and Scars what to avoid for AI agents. One install, zero maintenance. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CLAUDE.md`
- **Contributing to Kira** (project_doc): The first 1,000 contributors get permanent free access to all Kira features, including future Pro tier. Your contribution is tracked by GitHub username. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CONTRIBUTING.md`
- **Kira — Design Document** (project_doc): 人間の知見をエージェントに渡す仕組み。 エージェントが同じ壁に二度ぶつからない世界を作る。 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `DESIGN.md`
- **Kira Flywheel — 改善ループの憲法** (project_doc): 0→1 は創業者が出した。1→N はこのループが回す。 2026-07-06 制定 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `FLYWHEEL.md`
- **Kira 事業計画書** (project_doc): Where agents shine. MCP 1個入れるだけで、どのAIエージェントも天才になる。 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `PLAN.md`
- **Kira Telemetry Privacy** (project_doc): Kira reports the outcome of skill applications back to a central service so the community can improve Skills and surface new Scars. This document describes exactly what is sent, how it is sanitized, how to opt out, and how long it is kept . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `PRIVACY.md`
- **Kira Pro -- Monetization Architecture Design** (project_doc): Kira Pro -- Monetization Architecture Design Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `PRO-DESIGN.md`
- **Reciprocity — share a scar, or subscribe, or wait** (project_doc): Reciprocity — share a scar, or subscribe, or wait Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `RECIPROCITY.md`
- **Security Policy** (project_doc): Kira's threat model is unusual and worth stating plainly: the corpus is text that AI agents read and act on. A malicious or sloppy corpus entry is an injection vector into every agent that installs Kira. We treat corpus content with supply-chain rules, and we want to hear about anything that weakens them. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `SECURITY.md`
- **Using Kira** (project_doc): Add to your MCP config and you're done: Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `USAGE.md`
- **GitHub Sponsors tier copy paste when enrolling** (project_doc): GitHub Sponsors tier copy paste when enrolling Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/sponsors-tiers.md`
- **Launch-day objections & honest answers internal prep — not a post** (project_doc): Launch-day objections & honest answers internal prep — not a post Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/launch/objections.md`
- **Reddit draft — r/ClaudeAI adapt for r/mcp, r/LocalLLaMA — post manually** (project_doc): Reddit draft — r/ClaudeAI adapt for r/mcp, r/LocalLLaMA — post manually Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/launch/reddit-r-claudeai.md`
- **Show HN draft post manually — do not automate** (project_doc): Show HN draft post manually — do not automate Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/launch/show-hn.md`
- **X スレッド草案 日本語 — 投稿は手動で** (project_doc): 1/ AI エージェントは失敗を毎セッション忘れる。retry で溶けた時間、踏んだ地雷、全部捨てられる。 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/launch/x-thread-ja.md`
- **Changelog** (project_doc): All notable changes to this project will be documented in this file. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CHANGELOG.md`
- **Troubleshooting** (project_doc): Kira is a stdio MCP server launched by your client with npx kira-mcp . Almost every install problem is one of the issues below. Each entry has a Symptom , a Cause , and a Fix . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `TROUBLESHOOTING.md`
- **Kira in Claude Code** (project_doc): Scope File When --- --- --- Project .mcp.json at the repo root Share Kira with everyone on the repo commit it . Global ~/.claude/settings.json Every project on your machine. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/claude-code.md`
- **Kira in Continue** (project_doc): Continue accepts either YAML ~/.continue/config.yaml , the current default or JSON ~/.continue/config.json . Both are shown below — use whichever your install already has. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/continue.md`
- **Kira in Cursor** (project_doc): Scope File When --- --- --- Project .cursor/mcp.json in the repo Share Kira with the repo commit it . Global ~/.cursor/mcp.json Every project on your machine. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/cursor.md`
- **Discord Launch Posts** (project_doc): Claude Code Community Official Discord Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `launch/discord.md`
- **Reddit r/ChatGPTCoding** (project_doc): Title Built an MCP server with 22 dev skills + failure warnings — agents stop making the same mistakes Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `launch/reddit-chatgpt.md`
- **Reddit r/ClaudeAI** (project_doc): Title I built an MCP that auto-manages skills for Claude Code — no more copying CLAUDE.md between projects Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `launch/reddit-claude.md`
- **Show HN Post** (project_doc): Title Show HN: Kira – One MCP that auto-manages skills and scars for AI agents Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `launch/show-hn.md`
- **X/Twitter — English** (project_doc): Tweet 1 Main announcement I built an MCP that makes AI agents automatically look up proven instructions before acting. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `launch/x-english.md`
- **X/Twitter — 日本語** (project_doc): MCP 1個入れるだけで、エージェントが自動で正しい手順を調べてから動く。 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `launch/x-japanese.md`
- **TL;DR** (project_doc): AIエージェント用のMCPサーバー「Kira」を作った。インストール1回で： - エージェントが自動で正しい手順を調べてから動く - 過去の失敗パターン（Scar）を読んで同じミスを避ける - 「Webアプリ作りたい」→ 8ステップの計画が降ってくる Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `launch/zenn-article.md`
- **Publishing Kira to the MCP Server Registry** (project_doc): Publishing Kira to the MCP Server Registry Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `scripts/registry-publish.md`
- **Third-party registry submissions** (project_doc): The canonical MCP Server Registry publish flow lives in registry-publish.md ./registry-publish.md . Several aggregators mirror that registry automatically see Downstream listings ./registry-publish.md downstream-listings-auto . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `scripts/registry-submissions.md`

## Evidence Index

- Indexed 80 evidence entries.

- **Kira** (documentation): ! CI https://github.com/aibenyclaude-coder/Kira/actions/workflows/ci.yml/badge.svg https://github.com/aibenyclaude-coder/Kira/actions/workflows/ci.yml ! npm https://img.shields.io/npm/v/kira-mcp.svg https://www.npmjs.com/package/kira-mcp ! npm downloads https://img.shields.io/npm/dw/kira-mcp.svg https://www.npmjs.com/package/kira-mcp ! scars absorbed https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fraw.githubusercontent.com%2Faibenyclaude-coder%2FKira%2Fmain%2Fdocs%2Fstats.json&query=%24.community scars&label=scars%20absorbed&color=orange ./skills/scars/ ! License: MIT https://img.shields.io/badge/License-MIT-yellow.svg ./LICENSE Evidence: `README.md`
- **Kira micro-benchmark** (documentation): A dependency-free micro-benchmark for the two hot paths an agent hits on every call: lookup keyword → skills + scars and resolveRoute goal → ordered steps . It exists to catch performance regressions , not to produce a leaderboard. Evidence: `bench/README.md`
- **Kira — Client Examples** (documentation): Copy-paste MCP config for the three most common clients. Each snippet is a complete, valid config — paste it, restart the client, done. Evidence: `examples/README.md`
- **Kira maintainer scripts** (documentation): Operational scripts run by the project maintainer. Not shipped in the npm package. Evidence: `scripts/README.md`
- **Kira Telemetry Worker** (documentation): Cloudflare Worker that receives outcome reports from Kira MCP clients and exposes 30-day aggregate stats per skill. Evidence: `worker/README.md`
- **Kira — Project Rules** (documentation): MCP server that auto-manages Skills how to do it and Scars what to avoid for AI agents. One install, zero maintenance. Evidence: `CLAUDE.md`
- **Package** (package_manifest): { "name": "kira-mcp", "version": "0.8.2", "description": "Where agents shine — auto-manages Skills and Scars for AI agents via MCP.", "mcpName": "io.github.aibenyclaude-coder/kira", "license": "MIT", "type": "module", "bin": { "kira-mcp": "./dist/index.js" }, "exports": { "./types": { "types": "./dist/types-public.d.ts", "import": "./dist/types-public.js" } }, "files": "dist/", "skills/", "routes/", "src/keys/", "README.md", "DESIGN.md" , "keywords": "mcp", "mcp-server", "ai", "agent", "agent-memory", "memory", "skills", "scars", "failure-learning", "claude", "claude-code", "cursor", "cline", "windsurf", "model-context-protocol" , "repository": { "type": "git", "url": "https://github.com/ai… Evidence: `package.json`
- **Package** (package_manifest): { "name": "kira-telemetry-worker", "version": "0.1.0", "private": true, "type": "module", "scripts": { "dev": "wrangler dev --port 8787", "deploy": "wrangler deploy", "test": "vitest run", "test:watch": "vitest", "migrate:local": "wrangler d1 execute kira-events-dev --local --file=migrations/0001 init.sql", "migrate:prod": "wrangler d1 execute kira-events-prod --remote --file=migrations/0001 init.sql" }, "devDependencies": { "@cloudflare/vitest-pool-workers": "^0.5.0", "@cloudflare/workers-types": "^4.20240924.0", "typescript": "^5.4.0", "vitest": "2.0.5", "wrangler": "^3.78.0" }, "dependencies": { "zod": "^3.23.0" } } Evidence: `worker/package.json`
- **Contributing to Kira** (documentation): The first 1,000 contributors get permanent free access to all Kira features, including future Pro tier. Your contribution is tracked by GitHub username. Evidence: `CONTRIBUTING.md`
- **License** (source_file): Copyright c 2026 B Button Corporation Yosuke Beniya Evidence: `LICENSE`
- **Kira — Design Document** (documentation): 人間の知見をエージェントに渡す仕組み。 エージェントが同じ壁に二度ぶつからない世界を作る。 Evidence: `DESIGN.md`
- **Kira Flywheel — 改善ループの憲法** (documentation): 0→1 は創業者が出した。1→N はこのループが回す。 2026-07-06 制定 Evidence: `FLYWHEEL.md`
- **Kira 事業計画書** (documentation): Where agents shine. MCP 1個入れるだけで、どのAIエージェントも天才になる。 Evidence: `PLAN.md`
- **Kira Telemetry Privacy** (documentation): Kira reports the outcome of skill applications back to a central service so the community can improve Skills and surface new Scars. This document describes exactly what is sent, how it is sanitized, how to opt out, and how long it is kept . Evidence: `PRIVACY.md`
- **Kira Pro -- Monetization Architecture Design** (documentation): Kira Pro -- Monetization Architecture Design Evidence: `PRO-DESIGN.md`
- **Reciprocity — share a scar, or subscribe, or wait** (documentation): Reciprocity — share a scar, or subscribe, or wait Evidence: `RECIPROCITY.md`
- **Security Policy** (documentation): Kira's threat model is unusual and worth stating plainly: the corpus is text that AI agents read and act on. A malicious or sloppy corpus entry is an injection vector into every agent that installs Kira. We treat corpus content with supply-chain rules, and we want to hear about anything that weakens them. Evidence: `SECURITY.md`
- **Using Kira** (documentation): Add to your MCP config and you're done: Evidence: `USAGE.md`
- **GitHub Sponsors tier copy paste when enrolling** (documentation): GitHub Sponsors tier copy paste when enrolling Evidence: `docs/sponsors-tiers.md`
- **Launch-day objections & honest answers internal prep — not a post** (documentation): Launch-day objections & honest answers internal prep — not a post Evidence: `docs/launch/objections.md`
- **Reddit draft — r/ClaudeAI adapt for r/mcp, r/LocalLLaMA — post manually** (documentation): Reddit draft — r/ClaudeAI adapt for r/mcp, r/LocalLLaMA — post manually Evidence: `docs/launch/reddit-r-claudeai.md`
- **Show HN draft post manually — do not automate** (documentation): Show HN draft post manually — do not automate Evidence: `docs/launch/show-hn.md`
- **X スレッド草案 日本語 — 投稿は手動で** (documentation): 1/ AI エージェントは失敗を毎セッション忘れる。retry で溶けた時間、踏んだ地雷、全部捨てられる。 Evidence: `docs/launch/x-thread-ja.md`
- **Setup Supabase Nextjs** (structured_config): { "id": "community.setup-supabase-nextjs.v1", "keywords": "supabase", "setup supabase", "add supabase", "supabase nextjs", "supabase auth", "supabase database", "add database", "setup database" , "contexts": "nextjs", "react", "typescript", "javascript", "app-router" , "title": "Set up Supabase in a Next.js App Router project", "summary": "Full Supabase integration for Next.js App Router — client setup for server/client/middleware, auth, RLS, TypeScript types, and env config.", "source": "community", "declaration": "I will set up Supabase for this Next.js App Router project using @supabase/ssr the official SSR package . This includes creating typed clients for server components, client comp… Evidence: `skills/community/setup-supabase-nextjs.json`
- **Authjs V5 Signin Wrong Import** (structured_config): { "id": "scar.authjs-v5-signin-wrong-import.v1", "keywords": "auth.js", "authjs", "nextauth", "next-auth", "signIn", "signOut", "server component", "client component" , "contexts": "nextjs", "typescript" , "title": "Auth.js v5 signIn/signOut fails because server and client imports are swapped", "summary": "Importing signIn from next-auth/react in a server component or from @/auth in a client component causes runtime errors.", "severity": "critical", "mistake": "Importing signIn or signOut from next-auth/react in a Server Component or Server Action. Auth.js v5 has TWO separate signIn/signOut exports: server-side from @/auth the project's auth config file and client-side from next-auth/react… Evidence: `skills/scars/authjs-v5-signin-wrong-import.json`
- **Prisma Generate Forgotten** (structured_config): { "id": "scar.prisma-generate-forgotten.v1", "keywords": "prisma", "setup prisma", "add prisma", "prisma orm", "add database", "setup database" , "contexts": "nextjs", "nodejs", "typescript", "javascript" , "title": "Prisma schema changed but prisma generate not run — types are stale", "summary": "Agent modifies schema.prisma but forgets to run npx prisma generate , causing TypeScript errors or runtime crashes from stale client types.", "severity": "critical", "mistake": "After editing schema.prisma adding a model, changing a field , the agent runs npx prisma db push or npx prisma migrate dev to sync the DB, but forgets to run npx prisma generate to regenerate the TypeScript client. The cod… Evidence: `skills/scars/prisma-generate-forgotten.json`
- **Stripe Webhook Body Parsed** (structured_config): { "id": "scar.stripe-webhook-body-parsed.v1", "keywords": "stripe", "add stripe", "stripe checkout", "stripe payments", "add payments" , "contexts": "nextjs", "react", "typescript", "javascript", "nodejs" , "title": "Stripe webhook signature verification fails — body already parsed as JSON", "summary": "Agent reads the webhook body with request.json before verifying the signature, causing stripe.webhooks.constructEvent to fail with 'No signatures found matching the expected signature for payload'.", "severity": "critical", "mistake": "In the webhook handler, the agent calls await request.json to read the body, then passes the parsed object to stripe.webhooks.constructEvent . But constructEv… Evidence: `skills/scars/stripe-webhook-body-parsed.json`
- **Supabase Rls Not Enabled** (structured_config): { "id": "scar.supabase-rls-not-enabled.v1", "keywords": "supabase", "rls", "row level security", "supabase security", "database security", "create table supabase", "supabase table" , "contexts": "nextjs", "supabase" , "title": "Supabase table created without Row Level Security — all data publicly accessible", "summary": "Agent creates a Supabase table without enabling RLS, leaving every row readable and writable by any anonymous user through the public API.", "severity": "critical", "mistake": "Agent runs CREATE TABLE in Supabase without following up with ALTER TABLE ... ENABLE ROW LEVEL SECURITY and adding policies. Supabase exposes tables via the public REST API by default. Without RLS, t… Evidence: `skills/scars/supabase-rls-not-enabled.json`
- **Consent** (source_file): import { readFile, writeFile, mkdir } from "node:fs/promises"; import { homedir } from "node:os"; import { join } from "node:path"; import { randomUUID } from "node:crypto"; import type { ConsentLevel, ConsentState } from "./types.js"; ⋮---- function parseEnvLevel v: string undefined : ConsentLevel null ⋮---- function newId : string ⋮---- async function readConsentFile : Promise ⋮---- async function writeConsentFile state: ConsentState : Promise ⋮---- export async function loadConsent : Promise ⋮---- export async function setConsent level: ConsentLevel, source: ConsentState "source" = "tool" : Promise ⋮---- export async function hasSeenPrompt : Promise ⋮---- export async function markPrompt… Evidence: `src/consent.ts`
- **Lookup** (source_file): import type { Skill, Scar, SkillSummary, ScarSummary, LookupRequest, LookupResponse, NearMatch, } from "./types.js"; import { tokenize, nearMatches, stem, hasCJK, type SimIndexed } from "./similarity.js"; ⋮---- function toSkillSummary skill: Skill & Indexed : SkillSummary ⋮---- function toScarSummary scar: Scar & Indexed : ScarSummary ⋮---- function stripIndex item: T : Omit ⋮---- export interface Indexed extends SimIndexed { keywordsLower: string ; contextsLower: string ; kwPhrases: string ; } ⋮---- function phraseWords text: string : string ⋮---- function phraseIn needle: string , hay: string : boolean ⋮---- export function indexItems items: T : T & Indexed ⋮---- function containsAtWordBo… Evidence: `src/lookup.ts`
- **Report** (source_file): import { appendFile, mkdir, rename, stat } from "node:fs/promises"; import { join } from "node:path"; import type { ReportRequest, ReportResponse } from "./types.js"; import { enqueue } from "./telemetry.js"; import { hasSeenPrompt, markPromptSeen, loadConsent, KIRA HOME } from "./consent.js"; import { sanitize } from "./sanitize.js"; import type { KiraTier } from "./license.js"; ⋮---- export async function record request: ReportRequest, tier: KiraTier = "free" : Promise ⋮---- export interface MissNear { id: string; score: number; } ⋮---- export type MissKind = "lookup" "route"; ⋮---- export async function logMiss keyword: string, context: string , near: MissNear , kind: MissKind = "lookup"… Evidence: `src/report.ts`
- **Route** (source_file): import { readFile, readdir } from "node:fs/promises"; import { join, dirname } from "node:path"; import { fileURLToPath } from "node:url"; import type { Skill, Scar, RouteStep, RouteRequest, RouteResponse, } from "./types.js"; import { lookup, type Indexed } from "./lookup.js"; ⋮---- export interface RouteDefinition { id: string; goals: string ; contexts: string ; title: string; description: string; steps: Array ; } ⋮---- export async function loadRoutes : Promise ⋮---- interface GoalMatch { route: RouteDefinition; exact: boolean; phraseLength: number; } ⋮---- function contextAllows route: RouteDefinition, normalizedContexts: string : boolean ⋮---- function outranks a: GoalMatch, b: GoalMat… Evidence: `src/route.ts`
- **Server** (source_file): import { Server } from "@modelcontextprotocol/sdk/server/index.js"; import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"; import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js"; import { loadAllSkills, loadAllScars } from "./index-loader.js"; import { loadRoutes, resolveRoute } from "./route.js"; import { lookup, indexItems } from "./lookup.js"; import { record, logMiss } from "./report.js"; import { verifyProKey, resolveKiraKey } from "./license.js"; import { startFlusher, shutdownFlush } from "./telemetry.js"; import { KIRA CONSENT TOOL, handleKiraConsent } from "./tools/kira consent.js"; import { KIRA STATUS TOOL, b… Evidence: `src/server.ts`
- **Telemetry** (source_file): import { appendFile, readFile, writeFile, mkdir } from "node:fs/promises"; import { existsSync, readFileSync } from "node:fs"; import { join, dirname } from "node:path"; import { fileURLToPath } from "node:url"; import { gzipSync } from "node:zlib"; import { loadConsent } from "./consent.js"; import { sanitizePayload } from "./sanitize.js"; import { KIRA HOME } from "./consent.js"; import type { KiraTier } from "./license.js"; import type { ConsentLevel, OsFamily, ReportLogEntry, ReportPayloadV1, ReportRequest, } from "./types.js"; ⋮---- function readVersion : string ⋮---- function osFamily : OsFamily ⋮---- function nodeMajor : number ⋮---- interface BuildArgs { request: ReportRequest; leve… Evidence: `src/telemetry.ts`
- **Kira Consent** (source_file): import { setConsent, loadConsent } from "../consent.js"; import type { ConsentLevel, ConsentState } from "../types.js"; ⋮---- interface KiraConsentArgs { level?: ConsentLevel; } ⋮---- export async function handleKiraConsent args: KiraConsentArgs undefined : Promise Evidence: `src/tools/kira_consent.ts`
- **Kira Status** (source_file): import { readFileSync } from "node:fs"; import { existsSync } from "node:fs"; import { readdir } from "node:fs/promises"; import { join, dirname } from "node:path"; import { fileURLToPath } from "node:url"; import { loadConsent } from "../consent.js"; import { PERSONAL SCARS DIR } from "../personal-scars.js"; import { REPORTS LOG, TELEMETRY URL } from "../telemetry.js"; import type { Skill, Scar, ConsentState } from "../types.js"; import type { KiraTier } from "../license.js"; ⋮---- export function readVersion : string ⋮---- export interface KiraStatusResult { kira version: string; tier: KiraTier; consent: ConsentState; counts: { skills: number; scars: number; personal scars: number; routes… Evidence: `src/tools/kira_status.ts`
- **Personal Brief** (source_file): import { loadPersonalScars, PERSONAL SCARS DIR, type PersonalScar, } from "../personal-scars.js"; ⋮---- export interface PersonalBriefInput { limit?: number; contexts?: string ; } ⋮---- export interface PersonalBrief { scars: PersonalScar ; count: number; total: number; source dir: string; read: "local-only"; headline: string; } ⋮---- function recencyMs iso: string : number ⋮---- function byRecencyDesc a: PersonalScar, b: PersonalScar : number ⋮---- function normalizeContexts contexts: string undefined : string ⋮---- function matchesContext scar: PersonalScar, wanted: string : boolean ⋮---- function clampLimit limit: number undefined : number ⋮---- function pluralScars n: number : string ⋮-… Evidence: `src/tools/personal-brief.ts`
- **Premortem** (source_file): import { lookup, type Indexed } from "../lookup.js"; import type { NearMatch, Scar, ScarSeverity } from "../types.js"; ⋮---- export interface PremortemRequest { goal: string; context?: string ; top k?: number; } ⋮---- export interface PremortemHotspot { id: string; title: string; severity: ScarSeverity; hit count: number; contexts: string ; mistake: string; instead: string; heat: number; estimated minutes saved: number; } ⋮---- export interface PremortemResponse { goal: string; context: string ; matched count: number; returned count: number; hotspots: PremortemHotspot ; prevention value: { estimated minutes saved: number; total recorded failures: number; recorded minutes saved: number; crit… Evidence: `src/tools/premortem.ts`
- **Record Failure** (source_file): import { recordPersonalScar, personalScarPath, type PersonalScar, type RecordFailureInput, } from "../personal-scars.js"; import type { ScarSeverity } from "../types.js"; ⋮---- export interface RecordFailureResult { ack: true; scar: PersonalScar; path: string; stored: "local-only"; } ⋮---- export async function handleRecordFailure args: unknown : Promise Evidence: `src/tools/record-failure.ts`
- **Share Scar** (source_file): import { loadPersonalScars, type PersonalScar } from "../personal-scars.js"; import { sanitize } from "../sanitize.js"; ⋮---- export interface ShareScarResult { candidate: Record ; issue title: string; issue body: string; submit url: string null; gh command: string; shared: "nothing yet — this tool only PREPARES the submission"; } ⋮---- function slugify s: string : string ⋮---- function clean text: string undefined, cap: number : string ⋮---- / Generalize a personal scar into the community submission shape. / export function buildCandidate scar: PersonalScar : Record ⋮---- // Honest count: how often it actually recurred on the submitter's machine. ⋮---- function buildIssueBody candidate: Re… Evidence: `src/tools/share-scar.ts`
- **Changelog** (documentation): All notable changes to this project will be documented in this file. Evidence: `CHANGELOG.md`
- **Troubleshooting** (documentation): Kira is a stdio MCP server launched by your client with npx kira-mcp . Almost every install problem is one of the issues below. Each entry has a Symptom , a Cause , and a Fix . Evidence: `TROUBLESHOOTING.md`
- **Kira in Claude Code** (documentation): Scope File When --- --- --- Project .mcp.json at the repo root Share Kira with everyone on the repo commit it . Global ~/.claude/settings.json Every project on your machine. Evidence: `examples/claude-code.md`
- **Kira in Continue** (documentation): Continue accepts either YAML ~/.continue/config.yaml , the current default or JSON ~/.continue/config.json . Both are shown below — use whichever your install already has. Evidence: `examples/continue.md`
- **Kira in Cursor** (documentation): Scope File When --- --- --- Project .cursor/mcp.json in the repo Share Kira with the repo commit it . Global ~/.cursor/mcp.json Every project on your machine. Evidence: `examples/cursor.md`
- **Discord Launch Posts** (documentation): Claude Code Community Official Discord Evidence: `launch/discord.md`
- **Reddit r/ChatGPTCoding** (documentation): Title Built an MCP server with 22 dev skills + failure warnings — agents stop making the same mistakes Evidence: `launch/reddit-chatgpt.md`
- **Reddit r/ClaudeAI** (documentation): Title I built an MCP that auto-manages skills for Claude Code — no more copying CLAUDE.md between projects Evidence: `launch/reddit-claude.md`
- **Show HN Post** (documentation): Title Show HN: Kira – One MCP that auto-manages skills and scars for AI agents Evidence: `launch/show-hn.md`
- **X/Twitter — English** (documentation): Tweet 1 Main announcement I built an MCP that makes AI agents automatically look up proven instructions before acting. Evidence: `launch/x-english.md`
- **X/Twitter — 日本語** (documentation): MCP 1個入れるだけで、エージェントが自動で正しい手順を調べてから動く。 Evidence: `launch/x-japanese.md`
- **TL;DR** (documentation): AIエージェント用のMCPサーバー「Kira」を作った。インストール1回で： - エージェントが自動で正しい手順を調べてから動く - 過去の失敗パターン（Scar）を読んで同じミスを避ける - 「Webアプリ作りたい」→ 8ステップの計画が降ってくる Evidence: `launch/zenn-article.md`
- **Publishing Kira to the MCP Server Registry** (documentation): Publishing Kira to the MCP Server Registry Evidence: `scripts/registry-publish.md`
- **Third-party registry submissions** (documentation): The canonical MCP Server Registry publish flow lives in registry-publish.md ./registry-publish.md . Several aggregators mirror that registry automatically see Downstream listings ./registry-publish.md downstream-listings-auto . Evidence: `scripts/registry-submissions.md`
- **Stats** (structured_config): { "community scars": 41, "community skills": 38, "vendor skills": 0, "total scar hits": 44, "critical scars": 17 } Evidence: `docs/stats.json`
- **Glama** (structured_config): { "$schema": "https://glama.ai/mcp/schemas/server.json", "maintainers": "aibenyclaude-coder" } Evidence: `glama.json`
- **Add Auth Nextjs** (structured_config): { "id": "route.add-auth-nextjs.v1", "goals": "add authentication", "add login", "add user auth", "setup auth for my app", "add sign in", "add sign up", "protect my routes" , "contexts": "nextjs", "react", "typescript" , "title": "Add Authentication to Next.js App", "description": "Complete route for adding authentication with protected routes and user management.", "steps": { "order": 1, "keyword": "add auth", "description": "Set up authentication provider Clerk or Auth.js " }, { "order": 2, "keyword": "prisma", "description": "Set up database for user data if using Auth.js with database adapter " }, { "order": 3, "keyword": "deploy vercel", "description": "Deploy to get callback URLs for O… Evidence: `routes/add-auth-nextjs.json`
- **Add File Uploads** (structured_config): { "id": "route.add-file-uploads.v1", "goals": "add file uploads", "upload files", "add image upload", "file upload feature", "user uploads" , "contexts": "nextjs", "react", "typescript" , "title": "File Upload Pipeline", "description": "Add file upload capability: client-side upload UI, server-side handling, and cloud storage.", "steps": { "order": 1, "keyword": "uploadthing", "description": "Set up UploadThing for file upload handling" }, { "order": 2, "keyword": "zod validation", "description": "Add file validation schemas with Zod" }, { "order": 3, "keyword": "s3 upload", "description": "Configure S3/R2 storage if needed beyond UploadThing" } , "version": "1.0.0", "updated at": "2026-04-… Evidence: `routes/add-file-uploads.json`
- **Api Stripe** (structured_config): { "id": "route.api-stripe.v1", "goals": "add payments", "monetize my app", "add stripe", "accept payments", "add subscription", "add checkout" , "contexts": "nextjs", "react", "typescript", "nodejs" , "title": "Stripe Payment Integration", "description": "Complete route for adding payment functionality to a web application.", "steps": { "order": 1, "keyword": "stripe", "description": "Set up Stripe SDK, API routes, and Checkout flow" }, { "order": 2, "keyword": "deploy vercel", "description": "Deploy to get a public URL for webhooks" } , "version": "1.0.0", "updated at": "2026-04-11T00:00:00Z" } Evidence: `routes/api-stripe.json`
- **Build Saas** (structured_config): { "id": "route.build-saas.v1", "goals": "build a saas", "create a saas app", "build saas application", "saas boilerplate", "saas starter", "build a subscription app" , "contexts": "nextjs", "react", "typescript" , "title": "Full-stack SaaS Application", "description": "Complete route from zero to production SaaS: UI, auth, database, payments, email, analytics, and deployment.", "steps": { "order": 1, "keyword": "setup tailwind", "description": "Set up styling with Tailwind CSS v4" }, { "order": 2, "keyword": "shadcn", "description": "Install UI component library" }, { "order": 3, "keyword": "prisma", "description": "Set up database with Prisma ORM" }, { "order": 4, "keyword": "add auth cler… Evidence: `routes/build-saas.json`
- The remaining 20 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`.

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `bench/README.md`, `examples/README.md`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `bench/README.md`, `examples/README.md`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Introduction to Kira & The Scar Loop**: importance `high`
  - source_paths: README.md, FLYWHEEL.md, DESIGN.md, PRO-DESIGN.md, PLAN.md
- **The 10 MCP Tools**: importance `high`
  - source_paths: src/tools/record-failure.ts, src/tools/personal-brief.ts, src/tools/premortem.ts, src/tools/share-scar.ts, src/tools/kira_consent.ts
- **Corpus: Skills, Community Scars & Personal Scar Storage**: importance `high`
  - source_paths: skills/community/setup-vercel-nextjs.json, skills/community/setup-supabase-nextjs.json, skills/scars/prisma-generate-forgotten.json, skills/scars/stripe-webhook-body-parsed.json, skills/scars/supabase-rls-not-enabled.json
- **Privacy, Telemetry & the Improvement Flywheel**: importance `high`
  - source_paths: PRIVACY.md, RECIPROCITY.md, SECURITY.md, FLYWHEEL.md, src/telemetry.ts

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `7c6d90cffb6b27b10dc8fa3daf43368b466387a4`
- inspected_files: `Dockerfile`, `README.md`, `package.json`, `docs/corpus.json`, `docs/launch/objections.md`, `docs/launch/reddit-r-claudeai.md`, `docs/launch/show-hn.md`, `docs/launch/x-thread-ja.md`, `docs/sponsors-tiers.md`, `docs/stats.json`, `examples/README.md`, `examples/claude-code.md`, `examples/continue.md`, `examples/cursor.md`, `src/aggregate.ts`, `src/consent.ts`, `src/demo-redaction.ts`, `src/demo.ts`, `src/errors.ts`, `src/flywheel.ts`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/aibenyclaude-coder/Kira
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/aibenyclaude-coder/Kira
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/aibenyclaude-coder/Kira
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Maintenance risk requires verification

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/aibenyclaude-coder/Kira
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Maintenance risk requires verification

- Trigger: release_recency=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/aibenyclaude-coder/Kira
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.