# kira - Doramagic AI Context Pack

> 定位：安装前体验与判断资产。它帮助宿主 AI 有一个好的开始，但不代表已经安装、执行或验证目标项目。

## 充分原则

- **充分原则，不是压缩原则**：AI Context Pack 应该充分到让宿主 AI 在开工前理解项目价值、能力边界、使用入口、风险和证据来源；它可以分层组织，但不以最短摘要为目标。
- **压缩策略**：只压缩噪声和重复内容，不压缩会影响判断和开工质量的上下文。

## 给宿主 AI 的使用方式

你正在读取 Doramagic 为 kira 编译的 AI Context Pack。请把它当作开工前上下文：帮助用户理解适合谁、能做什么、如何开始、哪些必须安装后验证、风险在哪里。不要声称你已经安装、运行或执行了目标项目。

## Claim 消费规则

- **事实来源**：Repo Evidence + Claim/Evidence Graph；Human Wiki 只提供显著性、术语和叙事结构。
- **事实最低状态**：`supported`
- `supported`：可以作为项目事实使用，但回答中必须引用 claim_id 和证据路径。
- `weak`：只能作为低置信度线索，必须要求用户继续核实。
- `inferred`：只能用于风险提示或待确认问题，不能包装成项目事实。
- `unverified`：不得作为事实使用，应明确说证据不足。
- `contradicted`：必须展示冲突来源，不得替用户强行选择一个版本。

## 它最适合谁

- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0002` supported 0.86

## 它能做什么

- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md` Claim：`clm_0001` supported 0.86

## 怎么开始

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

## 继续前判断卡

- **当前建议**：先做角色匹配试用
- **为什么**：这个项目更像角色库，核心风险是选错角色或把角色文案当执行能力；先用 Prompt Preview 试角色匹配，再决定是否沙盒导入。

### 30 秒判断

- **现在怎么做**：先做角色匹配试用
- **最小安全下一步**：先用 Prompt Preview 试角色匹配；满意后再隔离导入
- **先别相信**：角色质量和任务匹配不能直接相信。
- **继续会触碰**：角色选择偏差、命令执行、宿主 AI 配置

### 现在可以相信

- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0002` supported 0.86
- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md` Claim：`clm_0001` supported 0.86
- **存在 Quick Start / 安装命令线索**（supported）：可以相信项目文档出现过启动或安装入口；不要因此直接在主力环境运行。 证据：`scripts/registry-publish.md` Claim：`clm_0003` supported 0.86

### 现在还不能相信

- **角色质量和任务匹配不能直接相信。**（unverified）：角色库证明有很多角色，不证明每个角色都适合你的具体任务，也不证明角色能产生高质量结果。
- **不能把角色文案当成真实执行能力。**（unverified）：安装前只能判断角色描述和任务画像是否匹配，不能证明它能在宿主 AI 里完成任务。
- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。
- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。
- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。 证据：`CLAUDE.md`
- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。
- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。
- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。

### 继续会触碰什么

- **角色选择偏差**：用户对任务应该由哪个专家角色处理的判断。 原因：选错角色会让 AI 从错误专业视角回答，浪费时间或误导决策。
- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md`
- **宿主 AI 配置**：Claude/Codex/Cursor/Gemini/OpenCode 等宿主的 plugin、Skill 或规则加载配置。 原因：宿主配置会改变 AI 后续工作方式，可能和用户已有规则冲突。 证据：`CLAUDE.md`
- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md`
- **宿主 AI 上下文**：AI Context Pack、Prompt Preview、Skill 路由、风险规则和项目事实。 原因：导入上下文会影响宿主 AI 后续判断，必须避免把未验证项包装成事实。

### 最小安全下一步

- **先跑 Prompt Preview**：先用交互式试用验证任务画像和角色匹配，不要先导入整套角色库。（适用：任何项目都适用，尤其是输出质量未知时。）
- **只在隔离目录或测试账号试装**：避免安装命令污染主力宿主 AI、真实项目或用户主目录。（适用：存在命令执行、插件配置或本地写入线索时。）
- **先备份宿主 AI 配置**：Skill、plugin、规则文件可能改变 Claude/Cursor/Codex 的默认行为。（适用：存在插件 manifest、Skill 或宿主规则入口时。）
- **安装后只验证一个最小任务**：先验证加载、兼容、输出质量和回滚，再决定是否深用。（适用：准备从试用进入真实工作流时。）

### 退出方式

- **保留安装前状态**：记录原始宿主配置和项目状态，后续才能判断是否可恢复。
- **准备移除宿主 plugin / Skill / 规则入口**：如果试装后行为异常，可以把宿主 AI 恢复到试装前状态。
- **保留原始角色选择记录**：如果输出偏题，可以回到任务画像阶段重新选择角色，而不是继续沿着错误角色推进。
- **记录安装命令和写入路径**：没有明确卸载说明时，至少要知道哪些目录或配置需要手动清理。
- **如果没有回滚路径，不进入主力环境**：不可回滚是继续前阻断项，不应靠信任或运气继续。

## 哪些只能预览

- 解释项目适合谁和能做什么
- 基于项目文档演示典型对话流程
- 帮助用户判断是否值得安装或继续研究

## 哪些必须安装后验证

- 真实安装 Skill、插件或 CLI
- 执行脚本、修改本地文件或访问外部服务
- 验证真实输出质量、性能和兼容性

## 边界与风险判断卡

- **把安装前预览误认为真实运行**：用户可能高估项目已经完成的配置、权限和兼容性验证。 处理方式：明确区分 prompt_preview_can_do 与 runtime_required。 Claim：`clm_0013` inferred 0.45
- **命令执行会修改本地环境**：安装命令可能写入用户主目录、宿主插件目录或项目配置。 处理方式：先在隔离环境或测试账号中运行。 证据：`TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md` Claim：`clm_0014` supported 0.86
- **待确认**：真实安装后是否与用户当前宿主 AI 版本兼容？。原因：兼容性只能通过实际宿主环境验证。
- **待确认**：项目输出质量是否满足用户具体任务？。原因：安装前预览只能展示流程和边界，不能替代真实评测。
- **待确认**：安装命令是否需要网络、权限或全局写入？。原因：这影响企业环境和个人环境的安装风险。

## 开工前工作上下文

### 加载顺序

- 先读取 how_to_use.host_ai_instruction，建立安装前判断资产的边界。
- 读取 claim_graph_summary，确认事实来自 Claim/Evidence Graph，而不是 Human Wiki 叙事。
- 再读取 intended_users、capabilities 和 quick_start_candidates，判断用户是否匹配。
- 需要执行具体任务时，优先查 role_skill_index，再查 evidence_index。
- 遇到真实安装、文件修改、网络访问、性能或兼容性问题时，转入 risk_card 和 boundaries.runtime_required。

### 任务路由

- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`TROUBLESHOOTING.md`, `USAGE.md`, `scripts/registry-publish.md`, `worker/README.md` Claim：`clm_0001` supported 0.86

### 上下文规模

- 文件总数：178
- 重要文件覆盖：40/178
- 证据索引条目：80
- 角色 / Skill 条目：34

### 证据不足时的处理

- **missing_evidence**：说明证据不足，要求用户提供目标文件、README 段落或安装后验证记录；不要补全事实。
- **out_of_scope_request**：说明该任务超出当前 AI Context Pack 证据范围，并建议用户先查看 Human Manual 或真实安装后验证。
- **runtime_request**：给出安装前检查清单和命令来源，但不要替用户执行命令或声称已执行。
- **source_conflict**：同时展示冲突来源，标记为待核实，不要强行选择一个版本。

## Prompt Recipes

### 适配判断

- 目标：判断这个项目是否适合用户当前任务。
- 预期输出：适配结论、关键理由、证据引用、安装前可预览内容、必须安装后验证内容、下一步建议。

```text
请基于 kira 的 AI Context Pack，先问我 3 个必要问题，然后判断它是否适合我的任务。回答必须包含：适合谁、能做什么、不能做什么、是否值得安装、证据来自哪里。所有项目事实必须引用 evidence_refs、source_paths 或 claim_id。
```

### 安装前体验

- 目标：让用户在安装前感受核心工作流，同时避免把预览包装成真实能力或营销承诺。
- 预期输出：一段带边界标签的体验剧本、安装后验证清单和谨慎建议；不含真实运行承诺或强营销表述。

```text
请把 kira 当作安装前体验资产，而不是已安装工具或真实运行环境。

请严格输出四段：
1. 先问我 3 个必要问题。
2. 给出一段“体验剧本”：用 [安装前可预览]、[必须安装后验证]、[证据不足] 三种标签展示它可能如何引导工作流。
3. 给出安装后验证清单：列出哪些能力只有真实安装、真实宿主加载、真实项目运行后才能确认。
4. 给出谨慎建议：只能说“值得继续研究/试装”“先补充信息后再判断”或“不建议继续”，不得替项目背书。

硬性边界：
- 不要声称已经安装、运行、执行测试、修改文件或产生真实结果。
- 不要写“自动适配”“确保通过”“完美适配”“强烈建议安装”等承诺性表达。
- 如果描述安装后的工作方式，必须使用“如果安装成功且宿主正确加载 Skill，它可能会……”这种条件句。
- 体验剧本只能写成“示例台词/假设流程”：使用“可能会询问/可能会建议/可能会展示”，不要写“已写入、已生成、已通过、正在运行、正在生成”。
- Prompt Preview 不负责给安装命令；如用户准备试装，只能提示先阅读 Quick Start 和 Risk Card，并在隔离环境验证。
- 所有项目事实必须来自 supported claim、evidence_refs 或 source_paths；inferred/unverified 只能作风险或待确认项。

```

### 角色 / Skill 选择

- 目标：从项目里的角色或 Skill 中挑选最匹配的资产。
- 预期输出：候选角色或 Skill 列表，每项包含适用场景、证据路径、风险边界和是否需要安装后验证。

```text
请读取 role_skill_index，根据我的目标任务推荐 3-5 个最相关的角色或 Skill。每个推荐都要说明适用场景、可能输出、风险边界和 evidence_refs。
```

### 风险预检

- 目标：安装或引入前识别环境、权限、规则冲突和质量风险。
- 预期输出：环境、权限、依赖、许可、宿主冲突、质量风险和未知项的检查清单。

```text
请基于 risk_card、boundaries 和 quick_start_candidates，给我一份安装前风险预检清单。不要替我执行命令，只说明我应该检查什么、为什么检查、失败会有什么影响。
```

### 宿主 AI 开工指令

- 目标：把项目上下文转成一次对话开始前的宿主 AI 指令。
- 预期输出：一段边界明确、证据引用明确、适合复制给宿主 AI 的开工前指令。

```text
请基于 kira 的 AI Context Pack，生成一段我可以粘贴给宿主 AI 的开工前指令。这段指令必须遵守 not_runtime=true，不能声称项目已经安装、运行或产生真实结果。
```

## 角色 / Skill 索引

- 共索引 34 个角色 / Skill / 项目文档条目。

- **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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CLAUDE.md`
- **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… 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`examples/README.md`
- **Kira maintainer scripts**（project_doc）：Operational scripts run by the project maintainer. Not shipped in the npm package. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`worker/README.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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CONTRIBUTING.md`
- **GitHub Sponsors tier copy paste when enrolling**（project_doc）：GitHub Sponsors tier copy paste when enrolling 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/launch/reddit-r-claudeai.md`
- **Show HN draft post manually — do not automate**（project_doc）：Show HN draft post manually — do not automate 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/launch/show-hn.md`
- **X スレッド草案 日本語 — 投稿は手動で**（project_doc）：1/ AI エージェントは失敗を毎セッション忘れる。retry で溶けた時間、踏んだ地雷、全部捨てられる。 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/launch/x-thread-ja.md`
- **Changelog**（project_doc）：All notable changes to this project will be documented in this file. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CHANGELOG.md`
- **Kira — Design Document**（project_doc）：人間の知見をエージェントに渡す仕組み。 エージェントが同じ壁に二度ぶつからない世界を作る。 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`DESIGN.md`
- **Kira Flywheel — 改善ループの憲法**（project_doc）：0→1 は創業者が出した。1→N はこのループが回す。 2026-07-06 制定 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`FLYWHEEL.md`
- **Kira 事業計画書**（project_doc）：Where agents shine. MCP 1個入れるだけで、どのAIエージェントも天才になる。 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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 . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`PRIVACY.md`
- **Kira Pro -- Monetization Architecture Design**（project_doc）：Kira Pro -- Monetization Architecture Design 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`PRO-DESIGN.md`
- **Reciprocity — share a scar, or subscribe, or wait**（project_doc）：Reciprocity — share a scar, or subscribe, or wait 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`SECURITY.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 . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`TROUBLESHOOTING.md`
- **Using Kira**（project_doc）：Add to your MCP config and you're done: 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`USAGE.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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`examples/cursor.md`
- **Discord Launch Posts**（project_doc）：Claude Code Community Official Discord 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`launch/reddit-claude.md`
- **Show HN Post**（project_doc）：Title Show HN: Kira – One MCP that auto-manages skills and scars for AI agents 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`launch/x-english.md`
- **X/Twitter — 日本語**（project_doc）：MCP 1個入れるだけで、エージェントが自動で正しい手順を調べてから動く。 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`launch/x-japanese.md`
- **TL;DR**（project_doc）：AIエージェント用のMCPサーバー「Kira」を作った。インストール1回で： - エージェントが自動で正しい手順を調べてから動く - 過去の失敗パターン（Scar）を読んで同じミスを避ける - 「Webアプリ作りたい」→ 8ステップの計画が降ってくる 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`launch/zenn-article.md`
- **Publishing Kira to the MCP Server Registry**（project_doc）：Publishing Kira to the MCP Server Registry 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`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 . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`scripts/registry-submissions.md`

## 证据索引

- 共索引 80 条证据。

- **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. 证据：`CLAUDE.md`
- **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 证据：`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. 证据：`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. 证据：`examples/README.md`
- **Kira maintainer scripts**（documentation）：Operational scripts run by the project maintainer. Not shipped in the npm package. 证据：`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. 证据：`worker/README.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… 证据：`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" } } 证据：`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. 证据：`CONTRIBUTING.md`
- **License**（source_file）：Copyright c 2026 B Button Corporation Yosuke Beniya 证据：`LICENSE`
- **GitHub Sponsors tier copy paste when enrolling**（documentation）：GitHub Sponsors tier copy paste when enrolling 证据：`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 证据：`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 证据：`docs/launch/reddit-r-claudeai.md`
- **Show HN draft post manually — do not automate**（documentation）：Show HN draft post manually — do not automate 证据：`docs/launch/show-hn.md`
- **X スレッド草案 日本語 — 投稿は手動で**（documentation）：1/ AI エージェントは失敗を毎セッション忘れる。retry で溶けた時間、踏んだ地雷、全部捨てられる。 证据：`docs/launch/x-thread-ja.md`
- **Changelog**（documentation）：All notable changes to this project will be documented in this file. 证据：`CHANGELOG.md`
- **Kira — Design Document**（documentation）：人間の知見をエージェントに渡す仕組み。 エージェントが同じ壁に二度ぶつからない世界を作る。 证据：`DESIGN.md`
- **Kira Flywheel — 改善ループの憲法**（documentation）：0→1 は創業者が出した。1→N はこのループが回す。 2026-07-06 制定 证据：`FLYWHEEL.md`
- **Kira 事業計画書**（documentation）：Where agents shine. MCP 1個入れるだけで、どのAIエージェントも天才になる。 证据：`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 . 证据：`PRIVACY.md`
- **Kira Pro -- Monetization Architecture Design**（documentation）：Kira Pro -- Monetization Architecture Design 证据：`PRO-DESIGN.md`
- **Reciprocity — share a scar, or subscribe, or wait**（documentation）：Reciprocity — share a scar, or subscribe, or wait 证据：`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. 证据：`SECURITY.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 . 证据：`TROUBLESHOOTING.md`
- **Using Kira**（documentation）：Add to your MCP config and you're done: 证据：`USAGE.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. 证据：`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. 证据：`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. 证据：`examples/cursor.md`
- **Discord Launch Posts**（documentation）：Claude Code Community Official Discord 证据：`launch/discord.md`
- **Reddit r/ChatGPTCoding**（documentation）：Title Built an MCP server with 22 dev skills + failure warnings — agents stop making the same mistakes 证据：`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 证据：`launch/reddit-claude.md`
- **Show HN Post**（documentation）：Title Show HN: Kira – One MCP that auto-manages skills and scars for AI agents 证据：`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. 证据：`launch/x-english.md`
- **X/Twitter — 日本語**（documentation）：MCP 1個入れるだけで、エージェントが自動で正しい手順を調べてから動く。 证据：`launch/x-japanese.md`
- **TL;DR**（documentation）：AIエージェント用のMCPサーバー「Kira」を作った。インストール1回で： - エージェントが自動で正しい手順を調べてから動く - 過去の失敗パターン（Scar）を読んで同じミスを避ける - 「Webアプリ作りたい」→ 8ステップの計画が降ってくる 证据：`launch/zenn-article.md`
- **Publishing Kira to the MCP Server Registry**（documentation）：Publishing Kira to the MCP Server Registry 证据：`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 . 证据：`scripts/registry-submissions.md`
- **Stats**（structured_config）：{ "community scars": 41, "community skills": 38, "vendor skills": 0, "total scar hits": 44, "critical scars": 17 } 证据：`docs/stats.json`
- **Glama**（structured_config）：{ "$schema": "https://glama.ai/mcp/schemas/server.json", "maintainers": "aibenyclaude-coder" } 证据：`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… 证据：`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-… 证据：`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" } 证据：`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… 证据：`routes/build-saas.json`
- **Deploy Production**（structured_config）：{ "id": "route.deploy-production.v1", "goals": "deploy to production", "go live", "launch my app", "ship it", "put it online", "make it live" , "contexts": "nextjs", "react", "typescript", "nodejs" , "title": "Deploy to Production", "description": "Complete production deployment route including CI, monitoring, and deployment.", "steps": { "order": 1, "keyword": "setup vitest", "description": "Ensure tests pass before deploying" }, { "order": 2, "keyword": "github actions", "description": "Set up CI to run tests on every push" }, { "order": 3, "keyword": "docker", "description": "Containerize if needed skip for Vercel/Cloudflare " }, { "order": 4, "keyword": "deploy vercel", "description": "… 证据：`routes/deploy-production.json`
- **React Native Mobile App**（structured_config）：{ "id": "route.react-native-mobile-app.v1", "goals": "build a mobile app", "create a react native app", "build an expo app", "create a mobile application", "react native setup", "start a mobile project", "build ios and android app" , "contexts": "react-native", "expo", "typescript" , "title": "React Native Mobile App Expo ", "description": "Complete route from Expo project init to a production-ready React Native app with state management, auth, error monitoring, and analytics.", "steps": { "order": 1, "keyword": "setup expo", "description": "Initialize a new Expo project with TypeScript and file-based routing Expo Router " }, { "order": 2, "keyword": "setup zustand", "description": "Add lig… 证据：`routes/react-native-mobile-app.json`
- **Setup Dev Environment**（structured_config）：{ "id": "route.setup-dev-environment.v1", "goals": "setup dev environment", "configure development", "setup linting and testing", "setup code quality", "prepare project for development" , "contexts": "nextjs", "react", "typescript", "nodejs" , "title": "Set Up Development Environment", "description": "Configure linting, testing, and CI for a clean development workflow.", "steps": { "order": 1, "keyword": "setup eslint", "description": "Configure ESLint for code quality" }, { "order": 2, "keyword": "setup vitest", "description": "Set up unit testing" }, { "order": 3, "keyword": "docker", "description": "Containerize the application" }, { "order": 4, "keyword": "github actions", "description"… 证据：`routes/setup-dev-environment.json`
- **Web App Nextjs**（structured_config）：{ "id": "route.web-app-nextjs.v1", "goals": "build a web app", "create a web application", "make a website", "build a nextjs app", "create a fullstack app", "new nextjs project" , "contexts": "nextjs", "react", "typescript" , "title": "Full-stack Next.js Web Application", "description": "Complete route from project setup to production deployment for a Next.js web application.", "steps": { "order": 1, "keyword": "create nextjs app", "description": "Initialize a new Next.js project with App Router and TypeScript" }, { "order": 2, "keyword": "setup tailwind", "description": "Set up styling with Tailwind CSS v4" }, { "order": 3, "keyword": "shadcn", "description": "Install UI component library"… 证据：`routes/web-app-nextjs.json`
- **Server**（structured_config）：{ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json", "name": "io.github.aibenyclaude-coder/kira", "description": "Skills and Scars for AI agents - your agent records its failures and never repeats them.", "repository": { "url": "https://github.com/aibenyclaude-coder/Kira.git", "source": "github" }, "version": "0.8.1", "websiteUrl": "https://github.com/aibenyclaude-coder/Kira", "packages": { "registryType": "npm", "registryBaseUrl": "https://registry.npmjs.org", "identifier": "kira-mcp", "version": "0.8.1", "runtimeHint": "npx", "transport": { "type": "stdio" }, "environmentVariables": { "name": "KIRA TELEMETRY", "description": "Override telemetry cons… 证据：`server.json`
- **Tsconfig**（structured_config）：{ "compilerOptions": { "target": "ES2022", "module": "NodeNext", "moduleResolution": "NodeNext", "outDir": "./dist", "rootDir": "./src", "strict": true, "esModuleInterop": true, "skipLibCheck": true, "forceConsistentCasingInFileNames": true, "resolveJsonModule": true, "sourceMap": true, "declaration": false }, "include": "src/ / " , "exclude": "node modules", "dist" } 证据：`tsconfig.json`
- **Tsconfig**（structured_config）：{ "compilerOptions": { "target": "ES2022", "module": "ESNext", "moduleResolution": "Bundler", "strict": true, "esModuleInterop": true, "skipLibCheck": true, "forceConsistentCasingInFileNames": true, "resolveJsonModule": true, "lib": "ES2022" , "types": "@cloudflare/workers-types" }, "include": "src/ / ", "tests/ / " } 证据：`worker/tsconfig.json`
- **Create Nextjs App**（structured_config）：{ "id": "community.create-nextjs-app.v1", "keywords": "create nextjs app", "new nextjs project", "nextjs init", "create next app", "start nextjs", "nextjs setup" , "contexts": "nextjs", "react", "typescript" , "title": "Create a new Next.js application with create-next-app", "summary": "Scaffold a new Next.js project using create-next-app with App Router, TypeScript, Tailwind CSS, and recommended defaults.", "source": "community", "declaration": "I will create a new Next.js project using npx create-next-app@latest with App Router, TypeScript, and Tailwind CSS enabled. The project will use the src/ directory and default import alias @/ . If you want Pages Router, JavaScript, or a different c… 证据：`skills/community/create-nextjs-app.json`
- **Cut A Release**（structured_config）：{ "id": "community.cut-a-release.v1", "keywords": "cut a release", "release version", "tag release", "publish release", "version bump", "ship a release" , "contexts": "git", "github", "npm" , "title": "Cut a release: version consistency, changelog truth, bare gates, tag, publish", "summary": "Checklist-driven release flow that catches the usual silent failures: version strings that disagree across manifests, changelogs written from memory instead of the diff, gates that pass because of a pipe, and races with concurrent writers.", "source": "community", "declaration": "I will follow the release checklist: sync with the remote, make every version string agree, verify the changelog against the… 证据：`skills/community/cut-a-release.json`
- **Delegate To Subagents**（structured_config）：{ "id": "community.delegate-to-subagents.v1", "keywords": "delegate to subagents", "orchestrate agents", "multi agent workflow", "dispatch parallel agents", "subagent prompt", "agent team" , "contexts": , "title": "Delegate work to weaker subagents so the team beats a stronger soloist", "summary": "The delegation discipline that lets a team of cheaper agents match a stronger single model: closed-form prompts, evidence-first verification, anti-correlated lenses, externalized state, and depth concentrated at the narrow waist.", "source": "community", "declaration": "I will delegate with the closed-form template — every subagent gets a role, exact inputs, a definition of done, required evidenc… 证据：`skills/community/delegate-to-subagents.json`
- **Deploy Cloudflare Pages**（structured_config）：{ "id": "community.deploy-cloudflare-pages.v1", "keywords": "cloudflare", "deploy cloudflare", "cloudflare pages", "deploy to cloudflare", "wrangler" , "contexts": "nextjs", "react", "typescript", "javascript", "vite", "static" , "title": "Deploy a project to Cloudflare Pages", "summary": "Complete Cloudflare Pages deployment flow — handles wrangler setup, auth, Next.js via @cloudflare/next-on-pages, static site deploys, env vars, secrets, custom domains, and preview deployments.", "source": "community", "declaration": "Cloudflare Pages provides edge-first hosting with generous free tier. I will use the Wrangler CLI to deploy this project. If you prefer Vercel, Netlify, or a self-hosted alt… 证据：`skills/community/deploy-cloudflare-pages.json`
- **Deploy Vercel Nextjs**（structured_config）：{ "id": "community.deploy-vercel-nextjs.v1", "keywords": "deploy vercel", "deploy to vercel", "vercel deploy" , "contexts": "nextjs", "react", "typescript", "javascript" , "title": "Deploy a Next.js project to Vercel", "summary": "Complete Vercel deployment flow for Next.js apps — handles auth, build verification, env vars, first-time linking, and production confirmation.", "source": "community", "declaration": "Vercel provides a first-class, officially-supported deployment path for Next.js. I will use the Vercel CLI to deploy this project. If you prefer Cloudflare Pages, Netlify, or a self-hosted alternative, say so before I begin.", "instructions": " Deploy Next.js to Vercel\n\n 1. Pre-fl… 证据：`skills/community/deploy-vercel-nextjs.json`
- **Mcp Registry Publish**（structured_config）：{ "id": "community.mcp-registry-publish.v1", "keywords": "mcp registry publish", "list mcp server", "mcp server registry", "mcp-publisher", "submit mcp server" , "contexts": "mcp", "ci", "github-actions" , "title": "List an MCP server in the official MCP Registry OIDC from CI, no device flow ", "summary": "Get an MCP server into registry.modelcontextprotocol.io — which PulseMCP, Smithery and other aggregators auto-ingest — as a repeatable CI job instead of a one-off manual ritual. Verified on a real listing, including the schema traps.", "source": "community", "declaration": "I will publish this MCP server to the official registry via a CI job using GitHub Actions OIDC io.github. namespace… 证据：`skills/community/mcp-registry-publish.json`
- **Npm Trusted Publishing**（structured_config）：{ "id": "community.npm-trusted-publishing.v1", "keywords": "npm trusted publishing", "npm publish github actions", "npm oidc publish", "tokenless npm publish", "npm provenance" , "contexts": "ci", "github-actions", "npm" , "title": "Publish to npm from GitHub Actions with Trusted Publishing OIDC, no tokens ", "summary": "Tag-push releases with zero long-lived credentials: OIDC proves the repo's identity, npm publishes with a provenance attestation. Every step here was verified on a real release, including the traps.", "source": "community", "declaration": "I will set up tokenless npm publishing: a tag-triggered workflow that verifies the tag is on the default branch, publishes with OIDC + p… 证据：`skills/community/npm-trusted-publishing.json`
- **Setup Authjs Nextjs**（structured_config）：{ "id": "community.setup-authjs-nextjs.v1", "keywords": "auth.js", "authjs", "nextauth", "next-auth", "setup auth", "add auth", "authentication", "login", "sign in", "oauth" , "contexts": "nextjs", "typescript", "nodejs" , "title": "Set up Auth.js v5 in a Next.js App Router project", "summary": "Complete Auth.js v5 setup — install, route handler, middleware, providers Google/GitHub/Credentials , session access in server & client components, and database adapter.", "source": "community", "declaration": "I will set up Auth.js v5 the successor to NextAuth.js v4 for authentication. Auth.js v5 is designed for the App Router and supports Edge Runtime. If you prefer Clerk, Lucia, or another auth s… 证据：`skills/community/setup-authjs-nextjs.json`
- **Setup Clerk Nextjs**（structured_config）：{ "id": "community.setup-clerk-nextjs.v1", "keywords": "clerk", "setup clerk", "add clerk", "add auth", "add auth clerk", "setup auth", "authentication", "clerk nextjs", "clerk auth" , "contexts": "nextjs", "react", "typescript", "javascript" , "title": "Set up Clerk authentication with Next.js App Router", "summary": "Complete Clerk auth integration for Next.js App Router — ClerkProvider, middleware, sign-in/sign-up pages, route protection, and server/client auth hooks.", "source": "community", "declaration": "I will set up Clerk authentication using @clerk/nextjs for the Next.js App Router. This covers middleware, provider setup, auth pages, and route protection. If you need a different a… 证据：`skills/community/setup-clerk-nextjs.json`
- **Setup Docker Nodejs**（structured_config）：{ "id": "community.setup-docker-nodejs.v1", "keywords": "docker", "setup docker", "add docker", "dockerfile", "containerize", "docker compose" , "contexts": "nextjs", "nodejs", "typescript", "javascript", "react" , "title": "Set up Docker for Node.js and Next.js projects", "summary": "Production-grade Docker setup — multi-stage Dockerfile, .dockerignore, docker-compose for dev, health checks, and Next.js standalone output.", "source": "community", "declaration": "I will create a production-grade Docker setup with multi-stage builds, proper layer caching, a non-root user, and minimal image size. For Next.js projects, I will use standalone output mode. If you need a different base image or or… 证据：`skills/community/setup-docker-nodejs.json`
- 其余 20 条证据见 `AI_CONTEXT_PACK.json` 或 `EVIDENCE_INDEX.json`。

## 宿主 AI 必须遵守的规则

- **把本资产当作开工前上下文，而不是运行环境。**：AI Context Pack 只包含证据化项目理解，不包含目标项目的可执行状态。 证据：`CLAUDE.md`, `README.md`, `bench/README.md`
- **回答用户时区分可预览内容与必须安装后才能验证的内容。**：安装前体验的消费者价值来自降低误装和误判，而不是伪装成真实运行。 证据：`CLAUDE.md`, `README.md`, `bench/README.md`

## 用户开工前应该回答的问题

- 你准备在哪个宿主 AI 或本地环境中使用它？
- 你只是想先体验工作流，还是准备真实安装？
- 你最在意的是安装成本、输出质量、还是和现有规则的冲突？

## 验收标准

- 所有能力声明都能回指到 evidence_refs 中的文件路径。
- AI_CONTEXT_PACK.md 没有把预览包装成真实运行。
- 用户能在 3 分钟内看懂适合谁、能做什么、如何开始和风险边界。

---

## Doramagic Context Augmentation

下面内容用于强化 Repomix/AI Context Pack 主体。Human Manual 只提供阅读骨架；踩坑日志会被转成宿主 AI 必须遵守的工作约束。

## Human Manual 骨架

使用规则：这里只是项目阅读路线和显著性信号，不是事实权威。具体事实仍必须回到 repo evidence / Claim Graph。

宿主 AI 硬性规则：
- 不得把页标题、章节顺序、摘要或 importance 当作项目事实证据。
- 解释 Human Manual 骨架时，必须明确说它只是阅读路线/显著性信号。
- 能力、安装、兼容性、运行状态和风险判断必须引用 repo evidence、source path 或 Claim Graph。

- **Kira 概览：让 AI 代理不再重复犯错**：importance `high`
  - source_paths: README.md, DESIGN.md, PRO-DESIGN.md, PLAN.md
- **系统架构：本地存储 + MCP 服务器 + Cloudflare Worker**：importance `high`
  - source_paths: src/index.ts, src/server.ts, src/index-loader.ts, src/license.ts, src/errors.ts
- **核心 MCP 工具详解（10 个）**：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
- **隐私设计、遥测与本地状态管理**：importance `high`
  - source_paths: PRIVACY.md, SECURITY.md, src/sanitize.ts, src/consent.ts, src/telemetry.ts
- **技能目录（Skills）与伤痕语料（Scars）**：importance `high`
  - source_paths: docs/corpus.json, scripts/gen-corpus.mjs, scripts/validate-entry.mjs, routes/web-app-nextjs.json, routes/build-saas.json
- **安装、客户端配置与运行环境**：importance `medium`
  - source_paths: USAGE.md, examples/README.md, examples/claude-code.md, examples/cursor.md, examples/continue.md
- **飞轮改进循环：失误 → 反馈 → 目录升级**：importance `high`
  - source_paths: FLYWHEEL.md, src/flywheel.ts, src/report.ts, scripts/scar-intake.mjs, scripts/gen-stats.mjs
- **贡献、发布与版本演进（v0.3.1 → v0.8.2）**：importance `medium`
  - source_paths: CONTRIBUTING.md, RECIPROCITY.md, TROUBLESHOOTING.md, CHANGELOG.md, scripts/registry-publish.md

## 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`

宿主 AI 硬性规则：
- 没有 repo_clone_verified=true 时，不得声称已经读过源码。
- 没有 repo_inspection_verified=true 时，不得把 README/docs/package 文件判断写成事实。
- 没有 quick_start_verified=true 时，不得声称 Quick Start 已跑通。

## Doramagic Pitfall Constraints / 踩坑约束

这些规则来自 Doramagic 发现、验证或编译过程中的项目专属坑点。宿主 AI 必须把它们当作工作约束，而不是普通说明文字。

### Constraint 1: 可能修改宿主 AI 配置

- Trigger: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。
- Host AI rule: 列出会写入的配置文件、目录和卸载/回滚步骤。
- Why it matters: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。
- Evidence: capability.host_targets | https://github.com/aibenyclaude-coder/Kira | host_targets=mcp_host, claude_code, claude, cursor
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 2: 能力判断依赖假设

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: 将假设转成下游验证清单。
- Why it matters: 假设不成立时，用户拿不到承诺的能力。
- Evidence: capability.assumptions | https://github.com/aibenyclaude-coder/Kira | README/documentation is current enough for a first validation pass.
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 3: 维护活跃度未知

- Trigger: 未记录 last_activity_observed。
- Host AI rule: 补 GitHub 最近 commit、release、issue/PR 响应信号。
- Why it matters: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- Evidence: evidence.maintainer_signals | https://github.com/aibenyclaude-coder/Kira | last_activity_observed missing
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

- Trigger: no_demo
- Evidence: downstream_validation.risk_items | https://github.com/aibenyclaude-coder/Kira | no_demo; severity=medium
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 5: 存在评分风险

- Trigger: no_demo
- Why it matters: 风险会影响是否适合普通用户安装。
- Evidence: risks.scoring_risks | https://github.com/aibenyclaude-coder/Kira | no_demo; severity=medium
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 6: issue/PR 响应质量未知

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: 抽样最近 issue/PR，判断是否长期无人处理。
- Why it matters: 用户无法判断遇到问题后是否有人维护。
- Evidence: evidence.maintainer_signals | https://github.com/aibenyclaude-coder/Kira | issue_or_pr_quality=unknown
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 7: 发布节奏不明确

- Trigger: release_recency=unknown。
- Host AI rule: 确认最近 release/tag 和 README 安装命令是否一致。
- Why it matters: 安装命令和文档可能落后于代码，用户踩坑概率升高。
- Evidence: evidence.maintainer_signals | https://github.com/aibenyclaude-coder/Kira | release_recency=unknown
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。