claudeos-core 1.3.0 → 1.4.0

package/README.zh-CN.md

@@ -1,6 +1,6 @@
 # ClaudeOS-Core
 
-**一条命令，从源代码自动生成 Claude Code 的完整项目文档。**
+**唯一一个先读取源代码、用确定性分析确认技术栈和模式、然后生成精确匹配项目的 Claude Code 规则的工具。**
 
 ```bash
 npx claudeos-core init
@@ -12,20 +12,50 @@ ClaudeOS-Core 读取你的代码库，提取所有模式，生成一套完全适
 
 ---
 
-## 问题
+## 为什么选择 ClaudeOS-Core？
 
-Claude Code 很强大，但它不了解 _你的_ 项目规范。手动编写 `CLAUDE.md`、数十条规则和脚手架技能需要数小时——而且代码一变，这些文档就过时了。
+> 人类描述项目 → LLM 生成文档
 
-## 解决方案
+ClaudeOS-Core:
 
-ClaudeOS-Core 将整个过程自动化：
+> 代码分析源码 → 代码构建定制提示 → LLM 生成文档 → 代码验证输出
 
-1. **扫描** 你的项目——自动检测技术栈、领域、ORM、数据库、包管理器
-2. **深度分析** 源代码——控制器模式、服务层、命名规范、异常处理、安全、测试等 50+ 个类别
-3. **生成** 完整的文档体系——`CLAUDE.md`、Standards（15–19 个文件）、Rules、Skills、Guides（9 个文件）、Master Plans、DB 文档和 MCP 指南
-4. **验证** 一切——5 个内置验证工具确保一致性
+### 核心问题：LLM 猜测，代码确定。
 
-总耗时：**5–18 分钟**，取决于项目规模。零手动配置。
+当你要求 Claude "分析这个项目"时，它会**猜测**你的技术栈、ORM、领域结构。
+
+**ClaudeOS-Core 不猜测。** Claude Node.js:
+
+- `build.gradle` / `package.json` / `pyproject.toml` → **confirmed**
+- directory scan → **confirmed**
+- Java 5 patterns, Kotlin CQRS/BFF, Next.js App Router/FSD → **classified**
+- domain groups → **split**
+- stack-specific prompt → **assembled**
+
+### 结果
+
+其他工具生成"一般性好的"文档。
+ClaudeOS-Core 生成的文档知道你的项目使用 `ApiResponse.ok()`（而不是 `ResponseEntity.success()`），MyBatis XML 映射器位于 `src/main/resources/mapper/{domain}/`，包结构为 `com.company.module.{domain}.controller` — 因为它读了你的实际代码。
+
+### Before & After
+
+**没有 ClaudeOS-Core**:
+```
+❌ JPA repository (MyBatis)
+❌ ResponseEntity.success() (ApiResponse.ok())
+❌ order/controller/ (controller/order/)
+→ 20 min fix per file
+```
+
+**使用 ClaudeOS-Core 后**:
+```
+✅ MyBatis mapper + XML (build.gradle)
+✅ ApiResponse.ok() (source code)
+✅ controller/order/ (Pattern A)
+→ immediate match
+```
+
+这种差异会累积。每天10个任务 × 节省20分钟 = **每天3小时以上**。
 
 ---
 
@@ -79,6 +109,7 @@ ClaudeOS-Core 将整个过程自动化：
 - **FSD（功能切片设计）**：`features/*/`、`widgets/*/`、`entities/*/`
 - **RSC/Client 分离**：检测 `client.tsx` 模式，追踪服务端/客户端组件分离
 - **配置文件回退**：从配置文件检测 Next.js/Vite/Nuxt（monorepo 支持）
+- **深层目录回退**：React/CRA/Vite/Vue/RN 项目扫描任意深度的 `**/components/*/`、`**/views/*/`、`**/screens/*/`、`**/containers/*/`、`**/pages/*/`、`**/routes/*/`、`**/modules/*/`、`**/domains/*/`
 
 ---
 
@@ -117,7 +148,7 @@ bash claudeos-core-tools/bootstrap.sh
 
 ### 输出语言（支持 10 种语言）
 
-不带 `--lang` 运行 `init` 时，会显示箭头键交互选择器：
+不带 `--lang` 运行 `init` 时，会显示交互选择器（支持方向键或数字键）：
 
 ```
 ╔══════════════════════════════════════════════════╗
@@ -132,10 +163,10 @@ bash claudeos-core-tools/bootstrap.sh
   ❯  3. zh-CN  — 简体中文 (Chinese Simplified)
      ...
 
-  ↑↓ Move  ↵ Select
+  ↑↓ Move  1-0 Jump  Enter Select  ESC Cancel
 ```
 
-移动箭头时说明会切换为对应语言。跳过选择器直接指定：
+选择移动时说明会切换为对应语言。跳过选择器直接指定：
 
 ```bash
 npx claudeos-core init --lang zh-CN  # 简体中文
@@ -387,16 +418,21 @@ ClaudeOS-Core 生成的文档，Claude Code 实际读取方式如下：
 | 文件 | 时机 | 保证 |
 |---|---|---|
 | `CLAUDE.md` | 每次对话开始 | 始终 |
-| `.claude/rules/*.md` | 编辑文件时（通过 `paths: ["**/*"]`） | 始终 |
-| `.claude/rules/00.core/00.standard-reference.md` | ↑ 包含在上面 | 始终 |
+| `.claude/rules/00.core/*` | 编辑文件时（`paths: ["**/*"]`） | 始终 |
+| `.claude/rules/10.backend/*` | 编辑文件时（`paths: ["**/*"]`） | 始终 |
+| `.claude/rules/30.security-db/*` | 编辑文件时（`paths: ["**/*"]`） | 始终 |
+| `.claude/rules/40.infra/*` | 仅编辑 config/infra 文件时（范围限定 paths） | 有条件 |
+| `.claude/rules/50.sync/*` | 仅编辑 claudeos-core 文件时（范围限定 paths） | 有条件 |
 
-### 通过 standard-reference 规则读取的文件
+### 通过规则引用按需读取的文件
 
-`00.standard-reference.md` 规则指示 Claude Code 在编写代码前 Read 以下文档：
+每个规则文件底部的 `## Reference` 部分链接到对应的 standard。Claude 仅读取与当前任务相关的 standard：
 
 - `claudeos-core/standard/**` — 编码模式、✅/❌ 示例、命名规范
 - `claudeos-core/database/**` — 数据库 schema（查询、mapper、迁移用）
 
+`00.standard-reference.md` 作为目录，用于发现没有对应规则的 standard 文件。
+
 ### 不读取的文件（节省上下文）
 
 通过 standard-reference 规则的 `DO NOT Read` 部分明确排除：
@@ -450,19 +486,31 @@ npx claudeos-core restore
 
 ## 有何不同？
 
-| | ClaudeOS-Core | SuperClaude | 手动 CLAUDE.md | 通用 Skills |
-|---|---|---|---|---|
-| **读取你的代码** | ✅ 深度分析（55–95 类别） | ❌ 行为注入 | ❌ 手动编写 | ❌ 预置模板 |
-| **项目定制输出** | ✅ 每个文件反映你的模式 | ❌ 通用命令 | 部分 | ❌ 一刀切 |
-| **多栈支持** | ✅ 自动检测 + 分别分析 | ❌ 栈无关 | 手动 | 不一定 |
-| **Kotlin + CQRS/BFF** | ✅ 多模块, Command/Query 分离 | ❌ | ❌ | ❌ |
-| **多语言** | ✅ 10 种语言，交互式选择 | ❌ | ❌ | ❌ |
-| **自验证** | ✅ 5 个验证工具 | ❌ | ❌ | ❌ |
-| **备份 / 恢复** | ✅ Master Plan 系统 | ❌ | ❌ | ❌ |
-| **配置时间** | ~5–18分钟（自动） | ~5分钟（手动配置） | 数小时–数天 | ~5分钟 |
+| | ClaudeOS-Core | Everything Claude Code (50K+ ⭐) | Harness | specs-generator | Claude `/init` |
+|---|---|---|---|---|---|
+| **Approach** | Code analyzes first, then LLM generates | Pre-built config presets | LLM designs agent teams | LLM generates spec docs | LLM writes CLAUDE.md |
+| **Reads your source code** | ✅ Deterministic static analysis | ❌ | ❌ | ❌ (LLM reads) | ❌ (LLM reads) |
+| **Stack detection** | Code confirms (ORM, DB, build tool, pkg manager) | N/A (stack-agnostic) | LLM guesses | LLM guesses | LLM guesses |
+| **Domain detection** | Code confirms (Java 5 patterns, Kotlin CQRS, Next.js FSD) | N/A | LLM guesses | N/A | N/A |
+| **Same project → Same result** | ✅ Deterministic analysis | ✅ (static files) | ❌ (LLM varies) | ❌ (LLM varies) | ❌ (LLM varies) |
+| **Large project handling** | Domain group splitting (4 domains / 40 files per group) | N/A | No splitting | No splitting | Context window limit |
+| **Output** | CLAUDE.md + Rules + Standards + Skills + Guides + Plans (40-50+ files) | Agents + Skills + Commands + Hooks | Agents + Skills | 6 spec documents | CLAUDE.md (1 file) |
+| **Output location** | `.claude/rules/` (auto-loaded by Claude Code) | `.claude/` various | `.claude/agents/` + `.claude/skills/` | `.claude/steering/` + `specs/` | `CLAUDE.md` |
+| **Post-generation verification** | ✅ 5 automated validators | ❌ | ❌ | ❌ | ❌ |
+| **Multi-language output** | ✅ 10 languages | ❌ | ❌ | ❌ | ❌ |
+| **Multi-stack** | ✅ Backend + Frontend simultaneous | ❌ Stack-agnostic | ❌ | ❌ | Partial |
+| **Agent orchestration** | ❌ | ✅ 28 agents | ✅ 6 patterns | ❌ | ❌ |
 
----
+### Key difference
 
+**Other tools give Claude "generally good instructions." ClaudeOS-Core gives Claude "instructions extracted from your actual code."**
+
+### Complementary, not competing
+
+ClaudeOS-Core: **project-specific rules**. Other tools: **agent orchestration**.
+Use both together.
+
+---
 ## FAQ
 
 **Q：会修改我的源代码吗？**

package/bin/cli.js

@@ -120,7 +120,7 @@ function selectLangInteractive() {
       }
       output.push("");
       const DIM = "\x1b[2m";
-      output.push(`  \x1b[1m↑↓\x1b[0m${DIM} Move ${RESET} \x1b[1mEnter\x1b[0m${DIM} Select ${RESET} \x1b[1mESC\x1b[0m${DIM} Cancel${RESET}`);
+      output.push(`  \x1b[1m↑↓\x1b[0m${DIM} Move ${RESET} \x1b[1m1-0\x1b[0m${DIM} Jump ${RESET} \x1b[1mEnter\x1b[0m${DIM} Select ${RESET} \x1b[1mESC\x1b[0m${DIM} Cancel${RESET}`);
       return output;
     }
 
@@ -131,13 +131,38 @@ function selectLangInteractive() {
     log("╚══════════════════════════════════════════════════╝");
     log("");
 
-    // Initial render
+    // Try raw mode BEFORE rendering arrow UI — if unsupported, fall back to number input
+    try {
+      process.stdin.setRawMode(true);
+    } catch (e) {
+      // setRawMode not supported (e.g., some Windows terminal emulators)
+      // Show description + language list and fall back to number input (no arrow UI rendered)
+      log("  Generated files (CLAUDE.md, Standards, Rules,");
+      log("  Skills, Guides) will be written in this language.");
+      log("");
+      const readline = require("readline");
+      LANG_CODES.forEach((code, i) => {
+        log(`    ${String(i + 1).padStart(2)}. ${code.padEnd(6)} — ${SUPPORTED_LANGS[code]}`);
+      });
+      log("");
+      const rl = readline.createInterface({ input: process.stdin, output: process.stdout });
+      rl.question(`  Enter number (1-${total}) or language code: `, (answer) => {
+        rl.close();
+        const trimmed = answer.trim();
+        const num = parseInt(trimmed);
+        if (num >= 1 && num <= total) { resolve(LANG_CODES[num - 1]); return; }
+        if (isValidLang(trimmed)) { resolve(trimmed); return; }
+        log(`\n  ❌ Invalid selection: "${trimmed}"`);
+        process.exit(1);
+      });
+      return;
+    }
+
+    // Raw mode succeeded — render interactive arrow UI
     const lines = render();
     const listHeight = lines.length;
     process.stdout.write(lines.join("\n") + "\n");
 
-    // Raw mode for keypress detection
-    process.stdin.setRawMode(true);
     process.stdin.resume();
 
     process.stdin.on("data", (key) => {
@@ -150,19 +175,21 @@ function selectLangInteractive() {
         process.exit(0);
       }
 
-      // ESC (single byte only — arrow keys send \x1b[ which is 3 bytes)
+      // ESC (single byte only — arrow keys send \x1b[ or \x1bO which are 3 bytes)
+      // Note: on very slow connections, arrow key bytes could arrive split across events,
+      // but this is an inherent raw-mode limitation and extremely rare in practice.
       if (k === "\x1b" && key.length === 1) {
         process.stdin.setRawMode(false);
         log("\n  Cancelled.\n");
         process.exit(0);
       }
 
-      // Up arrow
-      if (k === "\x1b[A") {
+      // Up arrow (normal mode \x1b[A and application mode \x1bOA)
+      if (k === "\x1b[A" || k === "\x1bOA") {
         selected = (selected - 1 + total) % total;
       }
-      // Down arrow
-      else if (k === "\x1b[B") {
+      // Down arrow (normal mode \x1b[B and application mode \x1bOB)
+      else if (k === "\x1b[B" || k === "\x1bOB") {
         selected = (selected + 1) % total;
       }
       // Number keys 1-9 (direct jump)
@@ -587,7 +614,8 @@ function countFiles() {
     const visited = new Set();
     const scan = (dir) => {
       if (!fs.existsSync(dir)) return;
-      const realDir = fs.realpathSync(dir);
+      let realDir;
+      try { realDir = fs.realpathSync(dir); } catch { realDir = dir; }
       if (visited.has(realDir)) return;
       visited.add(realDir);
       for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {

package/bootstrap.sh

@@ -5,6 +5,9 @@
 # One-click full system auto-build
 # Automatically splits Pass 1 into N runs based on project size
 #
+# Prerequisites: bash, node (v18+), claude CLI, perl
+# For cross-platform use without perl, use: node bin/cli.js init
+#
 # Usage: bash claudeos-core-tools/bootstrap.sh --lang ko
 #        bash claudeos-core-tools/bootstrap.sh              (interactive)
 
@@ -330,11 +333,19 @@ echo "║                                                    ║"
 printf "║   Files created:     %-29s║\n" "${TOTAL_FILES}"
 printf "║   Domains analyzed:  %-29s║\n" "${TOTAL_GROUPS_DONE} groups"
 printf "║   Analysis passes:   %-29s║\n" "${PASS1_FILES} pass1 files"
+# Find label for selected lang
+LANG_LABEL="$CLAUDEOS_LANG"
+for i in "${!SUPPORTED_LANGS[@]}"; do
+  if [ "${SUPPORTED_LANGS[$i]}" = "$CLAUDEOS_LANG" ]; then
+    LANG_LABEL="${LANG_LABELS[$i]}"; break
+  fi
+done
+printf "║   Output language:   %-29s║\n" "${LANG_LABEL}"
 echo "║                                                    ║"
 echo "║   Verify anytime:                                  ║"
-echo "║   node claudeos-core-tools/health-checker/index.js ║"
+echo "║   npx claudeos-core health                         ║"
 echo "║                                                    ║"
 echo "║   Start using:                                     ║"
-echo "║   \"Create a CRUD for orders\"                     ║"
+echo "║   \"Create a CRUD for orders\"                       ║"
 echo "╚════════════════════════════════════════════════════╝"
 echo ""

package/content-validator/index.js

@@ -105,15 +105,13 @@ async function main() {
         errors.push({ file: r, type: "EMPTY", msg: "Empty file" });
         continue;
       }
-      // All rules (except sync reminders) must have paths: ["**/*"] frontmatter
-      if (!r.includes("50.sync")) {
-        const hasFrontmatter = c.startsWith("---");
-        const hasPathsKey = c.includes("paths:");
-        if (!hasFrontmatter) {
-          warnings.push({ file: r, type: "NO_FRONTMATTER", msg: "Missing YAML frontmatter (---)" });
-        } else if (!hasPathsKey) {
-          warnings.push({ file: r, type: "NO_PATHS", msg: "Frontmatter exists but missing paths: key — use paths: [\"**/*\"] to ensure rule is always loaded" });
-        }
+      // All rules must have paths: frontmatter (value varies by category — e.g. ["**/*"] for core/backend, scoped patterns for infra/sync)
+      const hasFrontmatter = c.startsWith("---");
+      const hasPathsKey = c.includes("paths:");
+      if (!hasFrontmatter) {
+        warnings.push({ file: r, type: "NO_FRONTMATTER", msg: "Missing YAML frontmatter (---)" });
+      } else if (!hasPathsKey) {
+        warnings.push({ file: r, type: "NO_PATHS", msg: "Frontmatter exists but missing paths: key" });
       }
     }
     console.log(`    ${ruleFiles.length} files checked`);
@@ -172,12 +170,19 @@ async function main() {
       if (!hasMarkdownTable) {
         warnings.push({ file: r, type: "NO_TABLE", msg: "Rules summary table appears to be missing" });
       }
-      // Kotlin code block check: core and backend standard files should contain ```kotlin blocks
+      // Kotlin code block check: backend standard files should contain ```kotlin blocks
+      // (core files excluded for multi-stack projects where core may cover frontend too)
       if (detectedLanguage === "kotlin") {
-        const kotlinRelevantPaths = ["backend-api", "00.core/02.", "00.core/03.", "30.security-db"];
-        if (kotlinRelevantPaths.some(p => r.includes(p))) {
+        const kotlinRequiredPaths = ["backend-api", "30.security-db"];
+        const kotlinOptionalPaths = ["00.core/02.", "00.core/03."];
+        const isRequired = kotlinRequiredPaths.some(p => r.includes(p));
+        const isOptional = kotlinOptionalPaths.some(p => r.includes(p));
+        if (isRequired || isOptional) {
           if (!c.includes("```kotlin") && !c.includes("```kt")) {
-            warnings.push({ file: r, type: "NO_KOTLIN_BLOCK", msg: "No ```kotlin code block found (expected for Kotlin project)" });
+            if (isRequired) {
+              warnings.push({ file: r, type: "NO_KOTLIN_BLOCK", msg: "No ```kotlin code block found (expected for Kotlin project)" });
+            }
+            // optional paths: skip warning (core files may legitimately lack kotlin blocks in multi-stack)
           }
         }
       }

package/manifest-generator/index.js

@@ -54,6 +54,7 @@ function frontmatter(f) {
 }
 
 
+// Plans using <file path="..."> block format
 function extractFileBlocks(f) {
   if (!fs.existsSync(f)) return [];
   const content = fs.readFileSync(f, "utf-8");
@@ -66,6 +67,22 @@ function extractFileBlocks(f) {
   return result;
 }
 
+// Plans using ## N. `path` ```markdown code block format (e.g., 21.sync-rules-master.md)
+function extractCodeBlockPaths(f) {
+  if (!fs.existsSync(f)) return [];
+  const content = fs.readFileSync(f, "utf-8");
+  const result = [];
+  const headingRe = /^##\s+\d+\.\s+`?([^`\n]+)`?/gm;
+  let headingMatch;
+  while ((headingMatch = headingRe.exec(content)) !== null) {
+    const filePath = headingMatch[1].trim();
+    if (filePath && filePath.includes("/")) {
+      result.push({ sourcePath: filePath, planFile: rel(f) });
+    }
+  }
+  return result;
+}
+
 async function main() {
   console.log("\n╔═══════════════════════════════════════╗");
   console.log("║  ClaudeOS-Core — Manifest Generator   ║");
@@ -119,10 +136,16 @@ async function main() {
   // import-graph.json removed — @import was never a Claude Code feature
 
   // ─── sync-map.json ─────────────────────────────────────
+  const CODE_BLOCK_PLANS = ["21.sync-rules-master.md"];
   const sm = { generatedAt: new Date().toISOString(), mappings: [] };
   if (fs.existsSync(DIRS.plan)) {
     for (const p of await glob("*.md", { cwd: DIRS.plan, absolute: true })) {
-      sm.mappings.push(...extractFileBlocks(p));
+      const bn = path.basename(p);
+      if (CODE_BLOCK_PLANS.includes(bn)) {
+        sm.mappings.push(...extractCodeBlockPaths(p));
+      } else {
+        sm.mappings.push(...extractFileBlocks(p));
+      }
     }
   }
   sm.summary = { totalMappings: sm.mappings.length };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudeos-core",
-  "version": "1.3.0",
+  "version": "1.4.0",
   "description": "Auto-generate Claude Code documentation from your actual source code — Standards, Rules, Skills, and Guides tailored to your project",
   "main": "bin/cli.js",
   "bin": {

package/pass-prompts/templates/java-spring/pass1.md

@@ -96,7 +96,7 @@ Analysis items (per domain):
     - Performance issues (N+1, unnecessary queries, memory waste)
     - Security issues (SQL Injection potential, missing authorization)
 
-Do not create files. Analysis only.
+Do not create or modify source files. Analysis only.
 Save results to claudeos-core/generated/pass1-{{PASS_NUM}}.json in the following format:
 
 {

package/pass-prompts/templates/java-spring/pass3.md

@@ -15,6 +15,14 @@ If a standard defines a specific pattern (e.g., import path, file naming, API us
 the corresponding rule MUST use the same pattern. Before generating each rule file,
 verify it is consistent with the related standard file.
 
+CRITICAL — Code Example Accuracy:
+ALL code examples in rules and standards MUST use EXACT method names, class names,
+and signatures from pass2-merged.json analysis data.
+Do NOT paraphrase, rename, or infer API names. If pass2-merged.json records
+`MzcpResponseUtils.success()`, use `success()` — NOT `ok()`, NOT `respond()`.
+If a method signature is not captured in the analysis data,
+write "See corresponding standard for exact API" instead of guessing.
+
 CRITICAL — CLAUDE.md Reference Table Completeness:
 The reference table in CLAUDE.md MUST list ALL generated standard files, not just core.
 Include all backend-api, security-db, infra, and verification standards.
@@ -56,19 +64,31 @@ Generation targets:
    - Key rules summary table
 
 3. .claude/rules/ (active domains only)
-   - Every rule file MUST include `paths: ["**/*"]` in YAML frontmatter — this ensures Claude Code always loads the rule regardless of which file is being edited
    - Write the full rule content directly in each file (self-contained, no external references)
    - Include 5-15 lines of key rules with concrete examples
    - Do NOT use @import — it is not a Claude Code feature and does not work
-   - MUST generate `.claude/rules/00.core/00.standard-reference.md` — a mandatory rule file that instructs Claude Code to Read the standard documents before coding. Structure it as:
+   - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
+     ```
+     ## Reference
+     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend-api/01.controller-patterns.md
+     ```
+   - `paths:` frontmatter per rule category:
+     - `00.core/*` rules: `paths: ["**/*"]` — always loaded (architecture, naming are universally needed)
+     - `10.backend/*` rules: `paths: ["**/*"]` — always loaded (backend rules needed for any source editing)
+     - `30.security-db/*` rules: `paths: ["**/*"]` — always loaded (cross-cutting concerns)
+     - `40.infra/*` rules: `paths: ["**/*.yml", "**/*.yaml", "**/*.properties", "**/config/**", "**/*.gradle*", "**/Dockerfile*", "**/.env*"]` — loaded only for config/infra files
+     - `50.sync/*` rules: `paths: ["**/claudeos-core/**", "**/.claude/**"]` — loaded only when editing claudeos-core files
+   - MUST generate `.claude/rules/00.core/00.standard-reference.md` — a directory of all standard files. This is NOT a "read all" instruction. Claude should Read ONLY the standards relevant to the current task. Structure it as:
      ```
      ---
      paths:
        - "**/*"
      ---
-     # Required Standard Documents
-     Before writing or modifying code, you MUST Read the relevant standard files below using the Read tool.
-     ## Core (always read)
+     # Standard Documents Directory
+     Below is the complete list of standard files. Read ONLY the ones relevant to your current task — do NOT read all files.
+     Each rule file in .claude/rules/ links to its corresponding standard in the ## Reference section. Follow those links first.
+     This directory is for discovering standards that have no corresponding rule file.
+     ## Core
      - claudeos-core/standard/00.core/01.project-overview.md
      - claudeos-core/standard/00.core/02.architecture.md
      - claudeos-core/standard/00.core/03.naming-conventions.md

package/pass-prompts/templates/kotlin-spring/pass1.md

@@ -129,7 +129,7 @@ Analysis items (per domain):
     - Aggregate boundary violations (cross-aggregate direct references, oversized aggregates)
     - VO misuse (mutable VOs, VOs with identity, DTO used where VO should be)
 
-Do not create files. Analysis only.
+Do not create or modify source files. Analysis only.
 Save results to claudeos-core/generated/pass1-{{PASS_NUM}}.json in the following format:
 
 {

package/pass-prompts/templates/kotlin-spring/pass3.md

@@ -15,6 +15,14 @@ If a standard defines a specific pattern (e.g., import path, file naming, API us
 the corresponding rule MUST use the same pattern. Before generating each rule file,
 verify it is consistent with the related standard file.
 
+CRITICAL — Code Example Accuracy:
+ALL code examples in rules and standards MUST use EXACT method names, class names,
+and signatures from pass2-merged.json analysis data.
+Do NOT paraphrase, rename, or infer API names. If pass2-merged.json records
+`MzcpResponseUtils.success()`, use `success()` — NOT `ok()`, NOT `respond()`.
+If a method signature is not captured in the analysis data,
+write "See corresponding standard for exact API" instead of guessing.
+
 CRITICAL — CLAUDE.md Reference Table Completeness:
 The reference table in CLAUDE.md MUST list ALL generated standard files, not just core.
 Include all backend-api, security-db, infra, and verification standards.
@@ -59,20 +67,32 @@ Generation targets:
    - Key rules summary table
 
 3. .claude/rules/ (active domains only)
-   - Every rule file MUST include `paths: ["**/*"]` in YAML frontmatter — this ensures Claude Code always loads the rule regardless of which file is being edited
    - Write the full rule content directly in each file (self-contained, no external references)
    - Include 5-15 lines of key rules with concrete examples
    - Do NOT use @import — it is not a Claude Code feature and does not work
    - CQRS-specific rules: include command/query separation rules directly in the rule file content
-   - MUST generate `.claude/rules/00.core/00.standard-reference.md` — a mandatory rule file that instructs Claude Code to Read the standard documents before coding. Structure it as:
+   - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
+     ```
+     ## Reference
+     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend-api/01.controller-patterns.md
+     ```
+   - `paths:` frontmatter per rule category:
+     - `00.core/*` rules: `paths: ["**/*"]` — always loaded (architecture, naming are universally needed)
+     - `10.backend/*` rules: `paths: ["**/*"]` — always loaded (backend rules needed for any source editing)
+     - `30.security-db/*` rules: `paths: ["**/*"]` — always loaded (cross-cutting concerns)
+     - `40.infra/*` rules: `paths: ["**/*.yml", "**/*.yaml", "**/*.properties", "**/config/**", "**/*.gradle*", "**/Dockerfile*", "**/.env*"]` — loaded only for config/infra files
+     - `50.sync/*` rules: `paths: ["**/claudeos-core/**", "**/.claude/**"]` — loaded only when editing claudeos-core files
+   - MUST generate `.claude/rules/00.core/00.standard-reference.md` — a directory of all standard files. This is NOT a "read all" instruction. Claude should Read ONLY the standards relevant to the current task. Structure it as:
      ```
      ---
      paths:
        - "**/*"
      ---
-     # Required Standard Documents
-     Before writing or modifying code, you MUST Read the relevant standard files below using the Read tool.
-     ## Core (always read)
+     # Standard Documents Directory
+     Below is the complete list of standard files. Read ONLY the ones relevant to your current task — do NOT read all files.
+     Each rule file in .claude/rules/ links to its corresponding standard in the ## Reference section. Follow those links first.
+     This directory is for discovering standards that have no corresponding rule file.
+     ## Core
      - claudeos-core/standard/00.core/01.project-overview.md
      - claudeos-core/standard/00.core/02.architecture.md
      - claudeos-core/standard/00.core/03.naming-conventions.md

package/pass-prompts/templates/node-express/pass1.md

@@ -84,7 +84,7 @@ Analysis items (per domain):
    - Performance issues (memory leaks, blocking I/O)
    - Security issues (injection, missing authorization)
 
-Do not create files. Analysis only.
+Do not create or modify source files. Analysis only.
 Save results to claudeos-core/generated/pass1-{{PASS_NUM}}.json in the following format:
 
 {

package/pass-prompts/templates/node-express/pass3.md

@@ -17,6 +17,13 @@ If a standard defines a specific pattern (e.g., import path, file naming, API us
 the corresponding rule MUST use the same pattern. Before generating each rule file,
 verify it is consistent with the related standard file.
 
+CRITICAL — Code Example Accuracy:
+ALL code examples in rules and standards MUST use EXACT method names, class names,
+and signatures from pass2-merged.json analysis data.
+Do NOT paraphrase, rename, or infer API names.
+If a method signature is not captured in the analysis data,
+write "See corresponding standard for exact API" instead of guessing.
+
 CRITICAL — CLAUDE.md Reference Table Completeness:
 The reference table in CLAUDE.md MUST list ALL generated standard files, not just core.
 Include all frontend-ui, backend-api, security-db, infra, and verification standards.
@@ -57,19 +64,31 @@ Generation targets:
    - Key rules summary table
 
 3. .claude/rules/ (active domains only)
-   - Every rule file MUST include `paths: ["**/*"]` in YAML frontmatter — this ensures Claude Code always loads the rule regardless of which file is being edited
    - Write the full rule content directly in each file (self-contained, no external references)
    - Include 5-15 lines of key rules with concrete examples
    - Do NOT use @import — it is not a Claude Code feature and does not work
-   - MUST generate `.claude/rules/00.core/00.standard-reference.md` — a mandatory rule file that instructs Claude Code to Read the standard documents before coding. Structure it as:
+   - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
+     ```
+     ## Reference
+     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend-api/01.router-controller-patterns.md
+     ```
+   - `paths:` frontmatter per rule category:
+     - `00.core/*` rules: `paths: ["**/*"]` — always loaded (architecture, naming are universally needed)
+     - `10.backend/*` rules: `paths: ["**/*"]` — always loaded (backend rules needed for any source editing)
+     - `30.security-db/*` rules: `paths: ["**/*"]` — always loaded (cross-cutting concerns)
+     - `40.infra/*` rules: `paths: ["**/*.json", "**/*.env*", "**/config/**", "**/Dockerfile*", "**/*.yml", "**/*.yaml"]` — loaded only for config/infra files
+     - `50.sync/*` rules: `paths: ["**/claudeos-core/**", "**/.claude/**"]` — loaded only when editing claudeos-core files
+   - MUST generate `.claude/rules/00.core/00.standard-reference.md` — a directory of all standard files. This is NOT a "read all" instruction. Claude should Read ONLY the standards relevant to the current task. Structure it as:
      ```
      ---
      paths:
        - "**/*"
      ---
-     # Required Standard Documents
-     Before writing or modifying code, you MUST Read the relevant standard files below using the Read tool.
-     ## Core (always read)
+     # Standard Documents Directory
+     Below is the complete list of standard files. Read ONLY the ones relevant to your current task — do NOT read all files.
+     Each rule file in .claude/rules/ links to its corresponding standard in the ## Reference section. Follow those links first.
+     This directory is for discovering standards that have no corresponding rule file.
+     ## Core
      - claudeos-core/standard/00.core/01.project-overview.md
      - claudeos-core/standard/00.core/02.architecture.md
      - claudeos-core/standard/00.core/03.naming-conventions.md

package/pass-prompts/templates/node-nextjs/pass1.md

@@ -83,7 +83,7 @@ Analysis items (per domain):
    - Accessibility issues
    - Security issues (XSS, CSRF)
 
-Do not create files. Analysis only.
+Do not create or modify source files. Analysis only.
 Save results to claudeos-core/generated/pass1-{{PASS_NUM}}.json in the following format:
 
 {