# loadout - Doramagic AI Context Pack

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

## 充分原则

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

## 给宿主 AI 的使用方式

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

## Claim 消费规则

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

## 它最适合谁

- **AI 研究者或研究型 Agent 构建者**：README 明确围绕研究、实验或论文工作流展开。 证据：`README.md` Claim：`clm_0004` supported 0.86
- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0005` supported 0.86
- **希望把专业流程带进宿主 AI 的用户**：仓库包含 Skill 文档。 证据：`plugins/loadout/skills/browse/SKILL.md`, `plugins/loadout/skills/recommend/SKILL.md` Claim：`clm_0006` supported 0.86

## 它能做什么

- **AI Skill / Agent 指令资产库**（可做安装前预览）：项目包含可被宿主 AI 读取的 Skill 或 Agent 指令文件，可用于把专业流程带入 Claude、Codex、Cursor 等宿主。 证据：`plugins/loadout/skills/browse/SKILL.md`, `plugins/loadout/skills/recommend/SKILL.md` Claim：`clm_0001` supported 0.86
- **多宿主安装与分发**（需要安装后验证）：项目包含插件或 marketplace 配置，说明它面向一个或多个 AI 宿主的安装和分发。 证据：`.claude-plugin/marketplace.json`, `plugins/loadout/.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86
- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`README.md` Claim：`clm_0003` supported 0.86

## 怎么开始

- `/plugin marketplace add sukoji/loadout` 证据：`README.md` Claim：`clm_0007` supported 0.86
- `/plugin install loadout@loadout` 证据：`README.md` Claim：`clm_0008` supported 0.86
- `npx claude-loadout            # interactive` 证据：`README.md` Claim：`clm_0009` supported 0.86
- `npx claude-loadout --dry-run  # just show the recommendation` 证据：`README.md` Claim：`clm_0010` supported 0.86
- `npx claude-loadout --all      # apply the whole recommended loadout` 证据：`README.md` Claim：`clm_0011` supported 0.86
- `npx claude-loadout doctor     # audit tokens, hook deps, security gaps (read-only)` 证据：`README.md` Claim：`clm_0012` supported 0.86
- `npx claude-loadout export     # team loadout → .loadout.json` 证据：`README.md` Claim：`clm_0013` supported 0.86
- `npx claude-loadout apply -f .loadout.json   # apply shared manifest` 证据：`README.md` Claim：`clm_0014` supported 0.86
- `npx claude-loadout --help     # full flag list` 证据：`README.md` Claim：`clm_0015` supported 0.86
- `npx claude-loadout --target codex        # writes ~/.codex-style .codex/config.toml` 证据：`README.md` Claim：`clm_0016` supported 0.86

## 继续前判断卡

- **当前建议**：先做权限沙盒试用
- **为什么**：项目存在安装命令、宿主配置或本地写入线索，不建议直接进入主力环境，应先在隔离环境试装。

### 30 秒判断

- **现在怎么做**：先做权限沙盒试用
- **最小安全下一步**：先跑 Prompt Preview；若仍要安装，只在隔离环境试装
- **先别相信**：工具权限边界不能在安装前相信。
- **继续会触碰**：命令执行、宿主 AI 配置、本地环境或项目文件

### 现在可以相信

- **适合人群线索：AI 研究者或研究型 Agent 构建者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0004` supported 0.86
- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0005` supported 0.86
- **适合人群线索：希望把专业流程带进宿主 AI 的用户**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`plugins/loadout/skills/browse/SKILL.md`, `plugins/loadout/skills/recommend/SKILL.md` Claim：`clm_0006` supported 0.86
- **能力存在：AI Skill / Agent 指令资产库**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`plugins/loadout/skills/browse/SKILL.md`, `plugins/loadout/skills/recommend/SKILL.md` Claim：`clm_0001` supported 0.86
- **能力存在：多宿主安装与分发**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`.claude-plugin/marketplace.json`, `plugins/loadout/.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86
- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`README.md` Claim：`clm_0003` supported 0.86

### 现在还不能相信

- **工具权限边界不能在安装前相信。**（unverified）：MCP/tool 类项目通常会触碰文件、网络、浏览器或外部 API，必须真实检查权限和日志。
- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。
- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。
- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。 证据：`.claude-plugin/marketplace.json`, `CLAUDE.md`, `plugins/loadout/.claude-plugin/plugin.json`, `plugins/loadout/skills/browse/SKILL.md` 等
- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。
- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。 证据：`.claude-plugin/marketplace.json`, `plugins/loadout/.claude-plugin/plugin.json`
- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。
- **安装命令是否需要网络、权限或全局写入？**（unverified）：这影响企业环境和个人环境的安装风险。 证据：`README.md`

### 继续会触碰什么

- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`README.md`
- **宿主 AI 配置**：Claude/Codex/Cursor/Gemini/OpenCode 等宿主的 plugin、Skill 或规则加载配置。 原因：宿主配置会改变 AI 后续工作方式，可能和用户已有规则冲突。 证据：`.claude-plugin/marketplace.json`, `CLAUDE.md`, `plugins/loadout/.claude-plugin/plugin.json`, `plugins/loadout/skills/browse/SKILL.md` 等
- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`.claude-plugin/marketplace.json`, `README.md`, `plugins/loadout/.claude-plugin/plugin.json`
- **宿主 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_0023` inferred 0.45
- **宿主 AI 插件或 Skill 规则冲突**：新规则可能改变用户现有宿主 AI 的工作方式。 处理方式：安装前先检查插件 manifest 和 Skill 文件，必要时隔离测试。 证据：`.claude-plugin/marketplace.json`, `plugins/loadout/.claude-plugin/plugin.json` Claim：`clm_0024` supported 0.86
- **命令执行会修改本地环境**：安装命令可能写入用户主目录、宿主插件目录或项目配置。 处理方式：先在隔离环境或测试账号中运行。 证据：`README.md` Claim：`clm_0025` 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。

### 任务路由

- **AI Skill / Agent 指令资产库**：先基于 role_skill_index / evidence_index 帮用户挑选可用角色、Skill 或工作流。 边界：可做安装前 Prompt 体验。 证据：`plugins/loadout/skills/browse/SKILL.md`, `plugins/loadout/skills/recommend/SKILL.md` Claim：`clm_0001` supported 0.86
- **多宿主安装与分发**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`.claude-plugin/marketplace.json`, `plugins/loadout/.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86
- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`README.md` Claim：`clm_0003` supported 0.86

### 上下文规模

- 文件总数：53
- 重要文件覆盖：40/53
- 证据索引条目：50
- 角色 / Skill 条目：2

### 证据不足时的处理

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

## Prompt Recipes

### 适配判断

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

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

### 安装前体验

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

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

请严格输出四段：
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
请基于 loadout 的 AI Context Pack，生成一段我可以粘贴给宿主 AI 的开工前指令。这段指令必须遵守 not_runtime=true，不能声称项目已经安装、运行或产生真实结果。
```

## 角色 / Skill 索引

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

- **browse**（skill）：Browse the Loadout catalog of curated Claude Code extensions by domain frontend, backend, data/ML, devops, mobile, security, docs without changing anything. Use when the user wants to see what's available for a given kind of project, or asks "what MCP/skills/hooks exist for X" but isn't ready to install. 激活提示：当用户任务与“browse”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`plugins/loadout/skills/browse/SKILL.md`
- **recommend**（skill）：Profile the current project and recommend a domain-matched loadout of Claude Code extensions MCP servers, hooks, settings, skills , then apply the ones the user picks. Use when the user wants to set up, gear up, or optimize Claude Code for this repo, asks "what skills/MCP should I use here", runs /loadout, or opens a fresh project and wants the right tooling configured. 激活提示：当用户任务与“recommend”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`plugins/loadout/skills/recommend/SKILL.md`

## 证据索引

- 共索引 50 条证据。

- **Loadout catalog — by domain**（documentation）：Curated Claude Code extensions, organized by the kind of project you're working on. Generated from the canonical catalog — do not edit by hand run npm run build:docs . 证据：`docs/domains/README.md`
- **CLAUDE.md — Loadout**（documentation）：If you are resuming work on this project, read HANDOFF.md HANDOFF.md first. It has the current status, the task board, and how to verify the build. This file is the short always-loaded version. 证据：`CLAUDE.md`
- **Loadout looks at your project and sets up Claude Code for it — automatically.**（documentation）：Loadout looks at your project and sets up Claude Code for it — automatically. 证据：`README.md`
- **Package**（package_manifest）：{ "name": "claude-loadout", "version": "0.3.17", "description": "Profile your project and gear up your coding agent with the right MCP servers, skills, and hooks. Claude Code, Codex, Cursor, opencode, Gemini CLI & OpenClaw. A recommender + installer, not a list you read.", "type": "module", "bin": { "loadout": "cli/index.js" }, "files": "cli", "plugins/loadout/catalog", "README.md", "LICENSE" , "scripts": { "start": "node cli/index.js", "validate": "node scripts/validate-catalog.mjs", "test:recommend": "node scripts/test-recommend.mjs", "test:mcps": "node scripts/test-mcps.mjs", "verify:mcp": "node scripts/verify-mcp-packages.mjs", "test": "node scripts/validate-catalog.mjs && node scripts/… 证据：`package.json`
- **Contributing to Loadout**（documentation）：Loadout is only as good as its catalog. Adding a well-tagged entry is the highest-value contribution. 证据：`CONTRIBUTING.md`
- **Loadout — browse the catalog**（skill_instruction）：Read-only. Show what's in the catalog for a chosen domain; do not modify any files. 证据：`plugins/loadout/skills/browse/SKILL.md`
- **Loadout — recommend & apply**（skill_instruction）：Your job: look at THIS project, figure out what it is, and hand the user a short, ranked loadout of Claude Code extensions worth adding — then apply exactly the ones they choose. You are a recommender and installer, not a list-dumper. Never paste the whole catalog. 证据：`plugins/loadout/skills/recommend/SKILL.md`
- **Marketplace**（structured_config）：{ "$schema": "https://json.schemastore.org/claude-code-marketplace.json", "name": "loadout", "description": "Loadout — profile your project and gear up Claude Code with the right skills, MCP servers, and hooks. Not a list you read; a loadout you apply.", "owner": { "name": "sukoji" }, "plugins": { "name": "loadout", "source": "./plugins/loadout", "description": "Analyze your repo, recommend a domain-matched loadout of Claude Code extensions, and apply the ones you pick — MCP servers, hooks, settings, and skills.", "version": "0.3.17", "category": "workflow", "keywords": "setup", "recommender", "mcp", "skills", "hooks", "onboarding", "curated" , "homepage": "https://github.com/sukoji/loadout… 证据：`.claude-plugin/marketplace.json`
- **Plugin**（structured_config）：{ "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json", "name": "loadout", "displayName": "Loadout", "version": "0.3.17", "description": "Profile your project and gear up Claude Code with the right skills, MCP servers, and hooks.", "author": { "name": "sukoji" }, "homepage": "https://github.com/sukoji/loadout", "repository": "https://github.com/sukoji/loadout", "license": "MIT", "keywords": "setup", "recommender", "mcp", "skills", "hooks", "onboarding", "curated" } 证据：`plugins/loadout/.claude-plugin/plugin.json`
- **License**（source_file）：Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 证据：`LICENSE`
- **Changelog**（documentation）：All notable changes to Loadout are documented here. Format loosely follows Keep a Changelog https://keepachangelog.com/ ; versions follow SemVer https://semver.org/ . 证据：`CHANGELOG.md`
- **HANDOFF — resume this project cold**（documentation）：Read this file first. It exists so any session a new Claude Code session, or a human can pick up Loadout development without the original chat context. If a session dies mid-task, start here. 证据：`HANDOFF.md`
- **Backend / API**（documentation）：Servers, APIs, databases — Node, Python, Go, Rust, Java services. 证据：`docs/domains/backend-api.md`
- **Data / ML / Notebooks**（documentation）：Python data work, training pipelines, analysis, and reporting. 证据：`docs/domains/data-ml.md`
- **DevOps / Infra**（documentation）：CI/CD, Docker, Terraform, Kubernetes, cloud automation. 证据：`docs/domains/devops.md`
- **Docs / Writing / Office**（documentation）：Documentation, reports, and real Word/Excel/PDF/PPT deliverables. 证据：`docs/domains/docs-writing.md`
- **Frontend / Web UI**（documentation）：React, Vue, Svelte, Next — anything that ships to a browser. 证据：`docs/domains/frontend.md`
- **Game Development**（documentation）：Godot, Unity, Unreal — gameplay code, editor scripting, and engine tooling. 证据：`docs/domains/game-dev.md`
- **General / Any project**（documentation）：The always-useful baseline every repo benefits from. 证据：`docs/domains/general.md`
- **Mobile**（documentation）：iOS, Android, React Native, Flutter apps. 证据：`docs/domains/mobile.md`
- **Research / Academic**（documentation）：Literature review, notebooks, papers, and experiment repos — when discovery and writing matter as much as code. 证据：`docs/domains/research.md`
- **Security-sensitive**（documentation）：Auth, payments, PII, or anything where a mistake is expensive. 证据：`docs/domains/security.md`
- **Community**（structured_config）：{ "id": "caveman", "tier": "community", "verified": false, "type": "skill", "name": "Caveman token saver ", "description": "Community skill that makes the agent answer in terse 'caveman' style, cutting ~65–75% of output tokens while keeping technical accuracy. Levels: /caveman lite full ultra, plus Caveman Compress for CLAUDE.md.", "domains": "general" , "signals": "always" , "official": false, "homepage": "https://github.com/JuliusBrussee/caveman", "install": { "type": "manual", "note": "Community ~14k★ , UNVERIFIED by Loadout — review the repo before installing. Works with Claude Code and 40+ other agents.", "commands": } }, { "id": "community-marketplace", "tier": "community", "verified"… 证据：`plugins/loadout/catalog/community.json`
- **Domains**（structured_config）：{ "id": "frontend", "title": "Frontend / Web UI", "title ko": "프론트엔드 / 웹 UI", "blurb": "React, Vue, Svelte, Next — anything that ships to a browser.", "signals": "react", "next", "vue", "svelte", "vite", "tailwind", "angular", "package.json" , "loadout": "context7", "playwright", "chrome-devtools", "figma", "format-js-on-edit", "eslint-fix-on-edit", "superpowers", "code-review", "init-claude-md" }, { "id": "backend-api", "title": "Backend / API", "title ko": "백엔드 / API", "blurb": "Servers, APIs, databases — Node, Python, Go, Rust, Java services.", "signals": "express", "fastify", "nestjs", "django", "flask", "fastapi", "go.mod", "Cargo.toml", "pom.xml", "prisma", "drizzle", "postgres" , "lo… 证据：`plugins/loadout/catalog/domains.json`
- **Ecosystem**（structured_config）：{ "id": "42crunch-api-security-testing", "tier": "official", "type": "skill", "name": "42crunch-api-security-testing", "description": "Automate API security directly in Claude Code with 42Crunch - automatically audit OpenAPI specs, detect vulnerabilities aligned with OWASP API Security risks including BOLA/BFLA , and apply AI-powered fixes. Designed for AI-assisted development workflows, it provides continuous guardrails through an audit- scan- remediate- validate loop, ensuring APIs meet enterprise security standards before deployment.", "domains": "security" , "signals": , "official": true, "category": "security", "homepage": "https://42crunch.com", "install": { "type": "plugin", "marketp… 证据：`plugins/loadout/catalog/ecosystem.json`
- **Hooks**（structured_config）：{ "id": "format-js-on-edit", "type": "hook", "name": "Auto-format JS/TS on edit Prettier ", "description": "After Claude writes or edits a file, run Prettier on that exact file so the diff is always clean. Keeps you from reviewing formatting noise.", "domains": "frontend", "backend-api" , "signals": "package.json", "prettier", "react", "next", "vue", "svelte" , "note": "Requires jq and npx prettier available. On Windows, run Claude Code from Git Bash/WSL for this shell form, or adapt the command.", "settings": { "hooks": { "PostToolUse": { "matcher": "Write Edit", "hooks": { "type": "command", "command": "jq -r '.tool input.file path' grep -Eq '\\. js jsx ts tsx css scss json md html vue sv… 证据：`plugins/loadout/catalog/hooks.json`
- **Mcp**（structured_config）：{ "id": "filesystem", "type": "mcp", "name": "Filesystem", "description": "Give Claude scoped read/write access to specific directories outside the project root — useful for cross-repo work, shared asset folders, or a downloads dir.", "domains": "general", "backend-api", "data-ml", "devops" , "signals": "always" , "auth": false, "official": true, "homepage": "https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem", "config": { "command": "npx", "args": "-y", "@modelcontextprotocol/server-filesystem", "." } }, { "id": "git", "type": "mcp", "name": "Git", "description": "Structured git operations status, log, diff, blame, branch as first-class tools instead of shell parsing.… 证据：`plugins/loadout/catalog/mcp.json`
- **Skills**（structured_config）：{ "id": "superpowers", "type": "skill", "name": "Superpowers", "description": "A large, battle-tested framework of skills and subagents for planning, TDD, debugging, and disciplined execution. One of the most popular community skill packs; accepted into the official marketplace.", "domains": "general", "backend-api", "frontend", "data-ml" , "signals": "always" , "homepage": "https://github.com/obra/superpowers", "install": { "type": "plugin", "marketplace": "obra/superpowers", "plugin": "superpowers", "commands": "/plugin marketplace add obra/superpowers", "/plugin install superpowers@superpowers" } }, { "id": "office-docs", "type": "skill", "name": "Office documents pdf / docx / pptx / xls… 证据：`plugins/loadout/catalog/skills.json`
- **Index**（source_file）：const c = color, s = $ ⋮---- async function main ⋮---- function parseTargets args ⋮---- function printTargets ⋮---- function printHelp ⋮---- function parseOutputPath args, flags ⋮---- function parseManifestPath args ⋮---- function runExport args, flags ⋮---- function runApplyManifest args, flags ⋮---- function runDoctor flags = new Set ⋮---- function parseSelection answer, top ⋮---- function authLabel item ⋮---- function describeSignals signals ⋮---- function printReceipt r ⋮---- function printTargetReceipt r 证据：`cli/index.js`
- **Ingest Official**（source_file）：// Tier 2 ingestion: pull Anthropic's official plugin marketplace a trusted, vetted source and // transform its entries into Loadout catalog candidates in plugins/loadout/catalog/ecosystem.json. // These are surfaced by signal match or via --discover and installed with /plugin — never // auto-written to config. Curated entries Tier 1 always win on id collisions. // // Run: node scripts/ingest-official.mjs needs network ⋮---- // tech tokens to look for in name+description → signals that align with what scan.mjs detects ⋮---- function deriveSignals text ⋮---- if curated.has id seen.has id { skipped++; continue; } // Tier 1 wins 证据：`scripts/ingest-official.mjs`
- **Validate Catalog**（source_file）：// Validates the catalog: unique ids, required fields per kind, and that every // domain loadout references an item that actually exists. Exits non-zero on any error. ⋮---- // unique ids ⋮---- // required fields const need = item, field = ⋮---- // domain integrity 证据：`scripts/validate-catalog.mjs`
- **Verify Mcp Packages**（source_file）：// Accuracy gate: confirm every npx-based MCP server in the catalog points at a real, published // npm package a wrong install command is worse than no entry, since Loadout applies it . // stdio-via-uvx and HTTP servers are reported as "manual" — verify those against their homepage. 证据：`scripts/verify-mcp-packages.mjs`
- **Apply**（source_file）：// Apply selected catalog items to the project config. Returns a receipt describing what happened. export function apply selected, root = process.cwd ⋮---- function readJson path ⋮---- function writeJson path, doc ⋮---- // Deep-merge source into target. Arrays are concatenated so hook event arrays append, // not replace . Objects merge recursively. Scalars from source win. function deepMerge target, source 证据：`cli/lib/apply.mjs`
- **Doctor**（source_file）：export function doctor root = process.cwd ⋮---- function auditMcpServers mcpDoc, catalog, findings, file = ".mcp.json", mcpLocations ⋮---- function auditCrossAgentMcp root, catalog, findings, mcpLocations ⋮---- function trackMcp id, file, mcpLocations ⋮---- function auditDuplicateMcp mcpLocations, findings ⋮---- function auditMcpEntry id, cfg, catalog, findings, file, mcpLocations ⋮---- function auditTokens mcpDoc, findings ⋮---- function auditHooks settingsDoc, findings ⋮---- function auditSecurity hasEnv, settingsDoc, findings ⋮---- function auditGaps root, catalog, findings ⋮---- function commandExists name 证据：`cli/lib/doctor.mjs`
- **Manifest**（source_file）：// Build a shareable team loadout manifest from the current project profile. export function buildManifest catalog, root = process.cwd , opts = ⋮---- export function buildRecommendPreview signals, domains, items, community, installed, opts = ⋮---- export function writeManifest manifest, outPath ⋮---- export function readManifestIds path ⋮---- export function resolveManifestItems catalog, ids ⋮---- export function previewManifestApply catalog, manifestPath, opts = ⋮---- export function applyManifest catalog, manifestPath, root = process.cwd , opts = ⋮---- function normalizeTargets targets 证据：`cli/lib/manifest.mjs`
- **Paths**（source_file）：export function openclawHome ⋮---- export function openclawConfigPath 证据：`cli/lib/paths.mjs`
- **Recommend**（source_file）：// Signals too broad to justify a Tier-2 official plugin on their own. ⋮---- // On Windows, prefer native hook variants when catalog provides them. function resolveItemId id, byId ⋮---- // Score domains against project signals and build a ranked, de-duplicated loadout. // Tier 1 curated recs come from domain loadouts; Tier 2 official enter by signal match; // Tier 3 community surface only when opts.discover is set, and are never auto-applied. export function recommend ⋮---- // top 2 signal-matched domains + always keep general ⋮---- // Tier 2: official-marketplace plugins — only when signals are specific enough. ⋮---- function officialSignalMatch matched ⋮---- function rankEntries a, b ⋮---… 证据：`cli/lib/recommend.mjs`
- **Scan**（source_file）：// Walk a shallow slice of the project and collect "signals" — lowercase tokens // framework names, filenames, file extensions that the catalog matches against. export function scanProject root = process.cwd ⋮---- const add = s ⋮---- const has = p const read = p = ⋮---- // package.json + dependency names ⋮---- // normalize a few common scoped/aliased packages to catalog signals ⋮---- / ignore malformed package.json / ⋮---- // Python ⋮---- // Other ecosystems ⋮---- // shallow extension sweep top level + one dir down for .tf / .ipynb / .xcodeproj etc. ⋮---- function isDir root, rel ⋮---- function sweepExtensions root, signals, depth = 2 ⋮---- const walk = dir, d = ⋮---- function addExtensionS… 证据：`cli/lib/scan.mjs`
- **Targets**（source_file）：// Cross-agent target adapters. MCP servers are portable across modern agents; each target // only differs in WHERE its config lives and WHAT shape an MCP entry takes. Verified formats: // Claude Code .mcp.json { mcpServers: { NAME: {command,args,env} {type:"http",url} } } // Cursor .cursor/mcp.json same "mcpServers" shape as Claude // Gemini CLI .gemini/settings.json same "mcpServers" shape as Claude // opencode opencode.json { mcp: { NAME: {type:"local",command: ... ,enabled,environment} } } // Codex .codex/config.toml mcp servers.NAME command=".." args= .. env={..} // OpenClaw ~/.openclaw/openclaw.json { mcp: { servers: { NAME: {command,args,env} } } } http → transport ⋮---- export funct… 证据：`cli/lib/targets.mjs`
- **Test Detect Installed**（source_file）：function assert name, cond 证据：`scripts/test-detect-installed.mjs`
- **Test Doctor**（source_file）：function assert name, cond ⋮---- function hasMsg list, needle 证据：`scripts/test-doctor.mjs`
- **Test Manifest**（source_file）：function assert name, cond 证据：`scripts/test-manifest.mjs`
- **Test Recommend**（source_file）：// Regression checks for recommend ranking — run before release. ⋮---- function assert name, cond, detail = "" ⋮---- function topNames signals ⋮---- // ML research repo should surface research tools, not random python marketplace plugins. ⋮---- // LaTeX + bib repo should match research domain. ⋮---- // Frontend repo should still prioritize browser tooling. ⋮---- // Jupyter + numpy research repo LOOP 5 . ⋮---- // FastAPI backend should get API-appropriate tools, not frontend noise. ⋮---- // Godot game project. 证据：`scripts/test-recommend.mjs`
- **Test Scan**（source_file）：function assert name, cond 证据：`scripts/test-scan.mjs`
- **LOOP — Loadout improvement until claims are earned**（documentation）：LOOP — Loadout improvement until claims are earned 证据：`LOOP.md`
- **Loadout은 당신의 프로젝트를 보고, 거기에 맞게 Claude Code를 자동으로 세팅합니다.**（documentation）：Loadout은 당신의 프로젝트를 보고, 거기에 맞게 Claude Code를 자동으로 세팅합니다. 证据：`README.ko.md`
- **.gitignore**（source_file）：node modules/ .log .DS Store .env .env. dist/ coverage/ .claude/settings.local.json .loadout.json 证据：`.gitignore`
- **Banner**（source_file）：Loadout Gear up Claude Code for your project in one command — profiles your repo, then recommends and applies the right MCP servers, hooks and skills. 证据：`assets/banner.svg`
- **Demo**（source_file）：Loadout demo A terminal running npx claude-loadout : it detects the stack, recommends Playwright, a Prettier hook, and Context7, you pick 1,2,3, and it applies them to .mcp.json and .claude/settings.json. .l1{animation:l1 10s infinite}.l2{animation:l2 10s infinite}.l3{animation:l3 10s infinite} .l4{animation:l4 10s infinite}.l5{animation:l5 10s infinite}.l6{animation:l6 10s infinite} .l7{animation:l7 10s infinite}.l8{animation:l8 10s infinite}.l9{animation:l9 10s infinite} .cur{animation:blink 1s steps 1 infinite} @keyframes blink{0%,49%{opacity:1}50%,100%{opacity:0}} @keyframes l1{0%,2%{opacity:0}5%,95%{opacity:1}100%{opacity:0}} @keyframes l2{0%,13%{opacity:0}16%,95%{opacity:1}100%{opacit… 证据：`assets/demo.svg`
- **Build Docs**（source_file）：// Regenerates the browsable per-domain catalog pages under docs/domains/ from the // canonical catalog JSON, plus a domains index. Keeps the human-readable "list" // side of the repo in sync with the data the recommender actually uses. ⋮---- function itemLine item 证据：`scripts/build-docs.mjs`

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

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

- **项目概述与核心价值**：importance `high`
  - source_paths: README.md, CLAUDE.md, CHANGELOG.md, package.json
- **三层覆盖生态与目录体系**：importance `high`
  - source_paths: plugins/loadout/catalog/community.json, plugins/loadout/catalog/ecosystem.json, scripts/ingest-official.mjs, cli/lib/recommend.mjs
- **CLI 模块架构与数据流**：importance `high`
  - source_paths: cli/index.js, cli/lib/scan.mjs, cli/lib/recommend.mjs, cli/lib/apply.mjs, cli/lib/manifest.mjs
- **插件市场与斜杠命令注册**：importance `medium`
  - source_paths: .claude-plugin/marketplace.json, plugins/loadout/.claude-plugin/plugin.json, plugins/loadout/skills/recommend/SKILL.md, plugins/loadout/skills/browse/SKILL.md
- **扫描、领域匹配与推荐打分**：importance `high`
  - source_paths: cli/lib/scan.mjs, cli/lib/recommend.mjs, plugins/loadout/catalog/domains.json, plugins/loadout/skills/recommend/SKILL.md, scripts/test-scan.mjs
- **应用写入与多代理配置**：importance `high`
  - source_paths: cli/lib/apply.mjs, cli/lib/targets.mjs, cli/lib/paths.mjs, docs/domains/README.md
- **目录 JSON、领域文档与校验流程**：importance `high`
  - source_paths: plugins/loadout/catalog/domains.json, plugins/loadout/catalog/mcp.json, plugins/loadout/catalog/hooks.json, plugins/loadout/catalog/skills.json, scripts/validate-catalog.mjs
- **Doctor 审计、命令行工作流与贡献指南**：importance `medium`
  - source_paths: cli/lib/doctor.mjs, cli/lib/manifest.mjs, scripts/test-doctor.mjs, scripts/test-detect-installed.mjs, CONTRIBUTING.md

## Repo Inspection Evidence / 源码检查证据

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `6144f8aee5fb97ebc734879f81804603ed1b2983`
- inspected_files: `README.md`, `package.json`, `docs/domains/README.md`, `docs/domains/backend-api.md`, `docs/domains/data-ml.md`, `docs/domains/devops.md`, `docs/domains/docs-writing.md`, `docs/domains/frontend.md`, `docs/domains/game-dev.md`, `docs/domains/general.md`, `docs/domains/mobile.md`, `docs/domains/research.md`, `docs/domains/security.md`

宿主 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/sukoji/loadout | host_targets=mcp_host, claude_code, claude, openclaw, cursor, gemini_cli
- 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/sukoji/loadout | 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/sukoji/loadout | last_activity_observed missing
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

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

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

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