claudeos-core 1.3.0 → 1.3.1

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## [1.3.1] — 2026-04-03
+
+### Changed
+- **Context efficiency: rules paths scoping** — `40.infra/*` and `50.sync/*` rules now use scoped `paths:` frontmatter instead of `["**/*"]`; infra rules load only for config/infra files, sync rules load only for claudeos-core files (5 stacks; python-django infra keeps `["**/*"]` due to .py settings)
+- **Context efficiency: standard reference distribution** — `00.standard-reference.md` changed from "MUST Read ALL" to "Standard Documents Directory — Read ONLY relevant"; each rule file now ends with `## Reference` section linking to its corresponding standard
+- **content-validator** — Removed `50.sync` exemption from frontmatter validation; all rules now checked equally; updated comment and warning message to reflect scoped paths
+- **prompt-generator** — Removed duplicate `pass1-prompt.md` generation (backward-compat fallback no longer needed; `pass1-{type}-prompt.md` is always generated)
+- **Pass 1 templates** (all 6 stacks) — "Do not create files" → "Do not create or modify source files" (clarifies that saving analysis JSON is allowed)
+- **All 10 READMEs** — "How Claude Code Uses Your Documentation" section updated: auto-load table now shows per-category paths, standard reading explained as on-demand via `## Reference` links
+- **Pass 3 CRITICAL directive: Code Example Accuracy** (all 6 stacks) — Rules/standards code examples must use EXACT method names from pass2-merged.json; prevents hallucination of API names (e.g., `ok()` instead of `success()`)
+
 ## [1.3.0] — 2026-04-03
 
 ### Added

package/README.de.md

@@ -386,16 +386,21 @@ So liest Claude Code die von ClaudeOS-Core generierte Dokumentation tatsächlich
 | Datei | Wann | Garantiert |
 |---|---|---|
 | `CLAUDE.md` | Bei jedem Gesprächsstart | Immer |
-| `.claude/rules/*.md` | Beim Bearbeiten von Dateien (via `paths: ["**/*"]`) | Immer |
-| `.claude/rules/00.core/00.standard-reference.md` | ↑ Oben enthalten | Immer |
+| `.claude/rules/00.core/*` | Beim Bearbeiten von Dateien (`paths: ["**/*"]`) | Immer |
+| `.claude/rules/10.backend/*` | Beim Bearbeiten von Dateien (`paths: ["**/*"]`) | Immer |
+| `.claude/rules/30.security-db/*` | Beim Bearbeiten von Dateien (`paths: ["**/*"]`) | Immer |
+| `.claude/rules/40.infra/*` | Nur bei Config/Infra-Dateien (eingeschränkte Paths) | Bedingt |
+| `.claude/rules/50.sync/*` | Nur bei claudeos-core-Dateien (eingeschränkte Paths) | Bedingt |
 
-### Dateien, die über die standard-reference Regel gelesen werden
+### Dateien, die on-demand über Regel-Referenzen gelesen werden
 
-Die Regel `00.standard-reference.md` weist Claude Code an, die Standard-Dokumente vor dem Schreiben von Code zu Read:
+Jede Regel-Datei verlinkt im `## Reference`-Abschnitt auf den entsprechenden Standard. Claude liest nur den für die aktuelle Aufgabe relevanten Standard:
 
 - `claudeos-core/standard/**` — Coding-Patterns, ✅/❌ Beispiele, Namenskonventionen
 - `claudeos-core/database/**` — DB-Schema (für Queries, Mapper, Migrationen)
 
+`00.standard-reference.md` dient als Verzeichnis zum Entdecken von Standards ohne entsprechende Regel.
+
 ### Dateien, die NICHT gelesen werden (Kontexteinsparung)
 
 Explizit durch den `DO NOT Read`-Abschnitt der standard-reference Regel ausgeschlossen:

package/README.es.md

@@ -387,16 +387,21 @@ Así es como Claude Code lee la documentación generada por ClaudeOS-Core:
 | Archivo | Cuándo | Garantizado |
 |---|---|---|
 | `CLAUDE.md` | Al inicio de cada conversación | Siempre |
-| `.claude/rules/*.md` | Al editar archivos (vía `paths: ["**/*"]`) | Siempre |
-| `.claude/rules/00.core/00.standard-reference.md` | ↑ Incluido arriba | Siempre |
+| `.claude/rules/00.core/*` | Al editar archivos (`paths: ["**/*"]`) | Siempre |
+| `.claude/rules/10.backend/*` | Al editar archivos (`paths: ["**/*"]`) | Siempre |
+| `.claude/rules/30.security-db/*` | Al editar archivos (`paths: ["**/*"]`) | Siempre |
+| `.claude/rules/40.infra/*` | Solo al editar archivos config/infra (paths con alcance) | Condicional |
+| `.claude/rules/50.sync/*` | Solo al editar archivos claudeos-core (paths con alcance) | Condicional |
 
-### Archivos leídos vía regla standard-reference
+### Archivos leídos bajo demanda vía referencias en reglas
 
-La regla `00.standard-reference.md` instruye a Claude Code a Read los documentos estándar antes de escribir código:
+Cada archivo de regla enlaza a su standard correspondiente en la sección `## Reference`. Claude solo lee el standard relevante para la tarea actual:
 
 - `claudeos-core/standard/**` — Patrones de código, ejemplos ✅/❌, convenciones de nombres
 - `claudeos-core/database/**` — Schema DB (para queries, mappers, migraciones)
 
+`00.standard-reference.md` sirve como directorio para descubrir standards sin regla correspondiente.
+
 ### Archivos que NO se leen (ahorro de contexto)
 
 Excluidos explícitamente por la sección `DO NOT Read` de la regla standard-reference:

package/README.fr.md

@@ -387,16 +387,21 @@ Voici comment Claude Code lit effectivement la documentation générée par Clau
 | Fichier | Quand | Garanti |
 |---|---|---|
 | `CLAUDE.md` | Au début de chaque conversation | Toujours |
-| `.claude/rules/*.md` | Lors de l'édition de fichiers (via `paths: ["**/*"]`) | Toujours |
-| `.claude/rules/00.core/00.standard-reference.md` | ↑ Inclus ci-dessus | Toujours |
+| `.claude/rules/00.core/*` | Lors de l'édition de fichiers (`paths: ["**/*"]`) | Toujours |
+| `.claude/rules/10.backend/*` | Lors de l'édition de fichiers (`paths: ["**/*"]`) | Toujours |
+| `.claude/rules/30.security-db/*` | Lors de l'édition de fichiers (`paths: ["**/*"]`) | Toujours |
+| `.claude/rules/40.infra/*` | Uniquement pour les fichiers config/infra (paths scopés) | Conditionnel |
+| `.claude/rules/50.sync/*` | Uniquement pour les fichiers claudeos-core (paths scopés) | Conditionnel |
 
-### Fichiers lus via la règle standard-reference
+### Fichiers lus à la demande via les références des règles
 
-La règle `00.standard-reference.md` indique à Claude Code de Read les documents standards avant d'écrire du code :
+Chaque fichier de règle lie son standard correspondant dans la section `## Reference`. Claude ne lit que le standard pertinent pour la tâche en cours :
 
 - `claudeos-core/standard/**` — Patterns de code, exemples ✅/❌, conventions de nommage
 - `claudeos-core/database/**` — Schéma DB (pour requêtes, mappers, migrations)
 
+`00.standard-reference.md` sert de répertoire pour découvrir les standards sans règle correspondante.
+
 ### Fichiers NON lus (économie de contexte)
 
 Explicitement exclus par la section `DO NOT Read` de la règle standard-reference :

package/README.hi.md

@@ -387,16 +387,21 @@ ClaudeOS-Core द्वारा जेनरेट किए गए डॉक
 | फाइल | कब | गारंटी |
 |---|---|---|
 | `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/**` — DB स्कीमा (क्वेरी, मैपर, माइग्रेशन के लिए)
 
+`00.standard-reference.md` बिना संबंधित रूल वाले standard की खोज के लिए एक डायरेक्टरी के रूप में कार्य करता है।
+
 ### न पढ़ी जाने वाली फाइलें (कॉन्टेक्स्ट बचत)
 
 standard-reference रूल के `DO NOT Read` सेक्शन द्वारा स्पष्ट रूप से बाहर:

package/README.ja.md

@@ -388,16 +388,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` ルールが、コード作成前に以下のドキュメントを Read するよう指示します：
+各ルールファイル末尾の `## Reference` セクションが対応するstandardをリンクします。Claudeは現在のタスクに関連するstandardのみ読み取ります：
 
 - `claudeos-core/standard/**` — コーディングパターン、✅/❌ 例、命名規則
 - `claudeos-core/database/**` — DB スキーマ（クエリ、マッパー、マイグレーション用）
 
+`00.standard-reference.md` は対応ルールのないstandardを発見するためのディレクトリです。
+
 ### 読み取らないファイル（コンテキスト節約）
 
 standard-reference ルールの `DO NOT Read` セクションで明示的に除外されます：

package/README.ko.md

@@ -405,16 +405,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 규칙을 통해 읽는 파일
+### rule 참조를 통해 온디맨드로 읽는 파일
 
-`00.standard-reference.md` 규칙이 Claude Code에게 코드 작성 전 아래 문서를 Read하도록 지시합니다:
+각 rule 파일 하단의 `## Reference` 섹션이 대응하는 standard를 링크합니다. Claude는 현재 작업과 관련된 standard만 읽습니다:
 
 - `claudeos-core/standard/**` — 코딩 패턴, ✅/❌ 예시, 네이밍 규칙
 - `claudeos-core/database/**` — DB 스키마 (쿼리, 매퍼, 마이그레이션용)
 
+`00.standard-reference.md`는 대응 rule이 없는 standard를 발견하기 위한 디렉토리 역할입니다.
+
 ### 읽지 않는 파일 (컨텍스트 절약)
 
 standard-reference 규칙의 `DO NOT Read` 섹션으로 명시적으로 제외됩니다:

package/README.md

@@ -424,16 +424,21 @@ ClaudeOS-Core generates documentation that Claude Code actually reads — here's
 | File | When | Guaranteed |
 |---|---|---|
 | `CLAUDE.md` | Every conversation start | Always |
-| `.claude/rules/*.md` | When any file is edited (via `paths: ["**/*"]`) | Always |
-| `.claude/rules/00.core/00.standard-reference.md` | ↑ Included above | Always |
+| `.claude/rules/00.core/*` | When any file is edited (`paths: ["**/*"]`) | Always |
+| `.claude/rules/10.backend/*` | When any file is edited (`paths: ["**/*"]`) | Always |
+| `.claude/rules/30.security-db/*` | When any file is edited (`paths: ["**/*"]`) | Always |
+| `.claude/rules/40.infra/*` | Only when editing config/infra files (scoped paths) | Conditional |
+| `.claude/rules/50.sync/*` | Only when editing claudeos-core files (scoped paths) | Conditional |
 
-### What Claude Code reads via standard-reference rule
+### What Claude Code reads on-demand via rule references
 
-The `00.standard-reference.md` rule instructs Claude Code to Read the standard documents before writing code:
+Each rule file links to its corresponding standard via a `## Reference` section. Claude reads only the relevant standard for the current task:
 
 - `claudeos-core/standard/**` — coding patterns, ✅/❌ examples, naming conventions
 - `claudeos-core/database/**` — DB schema (for queries, mappers, migrations)
 
+The `00.standard-reference.md` serves as a directory of all standard files for discovering standards that have no corresponding rule.
+
 ### What Claude Code does NOT read (saves context)
 
 These folders are explicitly excluded via the `DO NOT Read` section in the standard-reference rule:

package/README.ru.md

@@ -387,16 +387,21 @@ npx claudeos-core restore      # Восстановление Plan → Диск
 | Файл | Когда | Гарантия |
 |---|---|---|
 | `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 стандартные документы перед написанием кода:
+Каждый файл правил ссылается на соответствующий standard в секции `## Reference`. Claude читает только standard, релевантный текущей задаче:
 
 - `claudeos-core/standard/**` — Паттерны кодирования, примеры ✅/❌, соглашения об именах
 - `claudeos-core/database/**` — Схема БД (для запросов, мапперов, миграций)
 
+`00.standard-reference.md` служит каталогом для обнаружения standards без соответствующего правила.
+
 ### Файлы, которые НЕ читаются (экономия контекста)
 
 Явно исключены через секцию `DO NOT Read` правила standard-reference:

package/README.vi.md

@@ -387,16 +387,21 @@ npx claudeos-core restore      # Khôi phục Plan → Đĩa
 | File | Thời điểm | Đảm bảo |
 |---|---|---|
 | `CLAUDE.md` | Mỗi lần bắt đầu cuộc trò chuyện | Luôn luôn |
-| `.claude/rules/*.md` | Khi chỉnh sửa file (qua `paths: ["**/*"]`) | Luôn luôn |
-| `.claude/rules/00.core/00.standard-reference.md` | ↑ Bao gồm ở trên | Luôn luôn |
+| `.claude/rules/00.core/*` | Khi chỉnh sửa file (`paths: ["**/*"]`) | Luôn luôn |
+| `.claude/rules/10.backend/*` | Khi chỉnh sửa file (`paths: ["**/*"]`) | Luôn luôn |
+| `.claude/rules/30.security-db/*` | Khi chỉnh sửa file (`paths: ["**/*"]`) | Luôn luôn |
+| `.claude/rules/40.infra/*` | Chỉ khi chỉnh sửa file config/infra (paths giới hạn) | Có điều kiện |
+| `.claude/rules/50.sync/*` | Chỉ khi chỉnh sửa file claudeos-core (paths giới hạn) | Có điều kiện |
 
-### File được đọc qua quy tắc standard-reference
+### File được đọc theo yêu cầu qua tham chiếu trong quy tắc
 
-Quy tắc `00.standard-reference.md` hướng dẫn Claude Code Read tài liệu standard trước khi viết code:
+Mỗi file quy tắc liên kết đến standard tương ứng trong phần `## Reference`. Claude chỉ đọc standard liên quan đến tác vụ hiện tại:
 
 - `claudeos-core/standard/**` — Pattern coding, ví dụ ✅/❌, quy tắc đặt tên
 - `claudeos-core/database/**` — DB schema (cho query, mapper, migration)
 
+`00.standard-reference.md` đóng vai trò thư mục để khám phá các standard không có quy tắc tương ứng.
+
 ### File KHÔNG đọc (tiết kiệm context)
 
 Được loại trừ rõ ràng qua phần `DO NOT Read` của quy tắc standard-reference:

package/README.zh-CN.md

@@ -387,16 +387,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` 部分明确排除：

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`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudeos-core",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "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:
 
 {

package/pass-prompts/templates/node-nextjs/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.
@@ -55,19 +62,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
-   - 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/20.frontend-ui/01.component-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)
+     - `20.frontend/*` rules: `paths: ["**/*"]` — always loaded (frontend rules needed for any source editing)
+     - `30.security-db/*` rules: `paths: ["**/*"]` — always loaded (cross-cutting concerns)
+     - `40.infra/*` rules: `paths: ["**/*.json", "**/*.env*", "**/next.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/python-django/pass1.md

@@ -89,7 +89,7 @@ Analysis items (per domain):
     - Security issues (SQL Injection, missing authorization, CSRF)
     - Performance issues (unnecessary queries, memory)
 
-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/python-django/pass3.md

@@ -16,6 +16,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 backend-api, security-db, infra, and verification standards.
@@ -56,19 +63,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.view-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: ["**/*"]` — always loaded (Django settings are .py files, so infra paths cannot be scoped separately)
+     - `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/python-fastapi/pass1.md

@@ -93,7 +93,7 @@ Analysis items (per domain):
     - Security issues (injection, missing authorization)
     - Performance issues (blocking I/O, N+1)
 
-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/python-fastapi/pass3.md

@@ -16,6 +16,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 backend-api, security-db, infra, and verification standards.
@@ -56,19 +63,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-endpoint-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: ["**/*.toml", "**/*.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/plan-installer/prompt-generator.js

@@ -56,11 +56,6 @@ function generatePrompts(templates, lang, templatesDir, generatedDir) {
     }
   }
 
-  if (primaryTemplate) {
-    const body = readTemplate(primaryTemplate, "pass1");
-    if (body) writeFileSafe(path.join(generatedDir, "pass1-prompt.md"), header + body);
-  }
-
   if (primaryTemplate) {
     const body = readTemplate(primaryTemplate, "pass2");
     if (body) {