claudeos-core 2.1.1 → 2.2.0

package/pass-prompts/templates/common/pass3-footer.md

@@ -35,5 +35,190 @@ MUST list ALL sub-skill files in its execution order table with no gaps.
 Every sub-skill file generated in the scaffold directory MUST have a corresponding row.
 Do NOT skip any number in the sequence.
 
+CRITICAL — Sync Rule Economy:
+For 50.sync/*, generate AT MOST 2 files:
+- One doc-sync rule covering BOTH directions (standard ↔ rules) as a single bidirectional rule.
+- One skills-sync rule covering the skills ↔ MANIFEST relationship.
+Do NOT generate separate "A → B" and "B → A" files for the same mirror relationship —
+they are redundant and multiply self-maintenance cost.
+
+Inside sync rules:
+- Do NOT hardcode file-to-file mapping tables (e.g., "standard/X.md → rules/X-rules.md"
+  listed for every pair). Express the relationship as a NAMING CONVENTION instead
+  (e.g., "standard/<N>.<dir>/<M>.<name>.md ↔ .claude/rules/<N>.<dir>/<M>.<name>-rules.md").
+- The master mapping index lives in .claude/rules/00.core/00.standard-reference.md —
+  sync rules should reference it, not duplicate it.
+- Hardcoded mapping tables rot fast: every new standard file forces an edit.
+  Naming conventions are self-describing and maintenance-free.
+
+CRITICAL — `00.standard-reference.md` Composition:
+This file is the mechanical standards index loaded on every edit via
+`paths: ["**/*"]`. Its role is to let Claude Code locate a standard file
+quickly without enumerating the whole tree. Scope it strictly:
+
+INCLUDE:
+- Every file that will exist under `claudeos-core/standard/` after Pass 3 + Pass 4.
+  This includes FORWARD REFERENCES to Pass 4 outputs — specifically
+  `claudeos-core/standard/00.core/04.doc-writing-guide.md` (generated by Pass 4's
+  Required output #12). Omitting it creates an index gap the moment Pass 4 runs.
+  If Pass 4 lands a file at `claudeos-core/standard/00.core/04.doc-writing-guide.md`,
+  it must already appear in Pass 3's `00.standard-reference.md` under `## Core`.
+
+DO NOT INCLUDE:
+- "DO NOT Read" / "context waste" / "Avoid reading" sections listing
+  `claudeos-core/generated/`, `claudeos-core/guide/`, `claudeos-core/mcp-guide/`,
+  `build/`, `mz-common/`, or any "negative list". CLAUDE.md Section 7
+  (DO NOT Read) is the single source of truth for that information, and it
+  is more complete (includes project-specific paths like `build/` and
+  external modules). Replicating this list inside `00.standard-reference.md`
+  creates a duplicate maintenance point that drifts over time.
+- Rule files (`.claude/rules/*`), skill files (`claudeos-core/skills/*`), or
+  memory files (`claudeos-core/memory/*`). The index is for standards only.
+- Inline descriptions per file (1-line summaries). Those live in CLAUDE.md
+  Section 6's Standard sub-section, which is loaded once per session
+  (session-time budget), while this file is reloaded on every edit
+  (per-edit budget). Keep the per-edit payload minimal — paths only.
+
+CRITICAL — `.env` Is the Source of Truth for Runtime Configuration:
+When pass2-merged.json contains `stack.envInfo` (parsed from the project's
+`.env.example` or `.env`), treat that data as authoritative for:
+
+- Port numbers (dev server, API server, alternate ports like mobile/storybook)
+- Host names (dev host, API host)
+- API target URLs (backend proxy target, external service endpoints)
+- Any other runtime configuration the project explicitly declares
+
+Do NOT override these with framework defaults (Vite 5173, Next.js 3000,
+Django 8000, etc.) when the project's env file says otherwise. Framework
+defaults are only valid when `stack.envInfo` is absent or the specific
+field is null.
+
+This affects:
+- CLAUDE.md Section 2 (Project Overview table) — port / host / API target rows
+- CLAUDE.md Section 3 (Build & Run Commands) — inline comments next to run commands
+- Any generated rule that references port values (e.g., 30.security-db/
+  auth rules that mention CORS origins)
+
+When in doubt, read `.env.example` directly and cross-check against
+`stack.envInfo.vars`. If they disagree, trust `.env.example` as the
+canonical declaration.
+
+CRITICAL — Rule `paths` Must Match Rule Content:
+Each `.claude/rules/*` file's `paths` frontmatter MUST match the file types
+that the rule's guardrails actually target, NOT the category's default.
+
+- A logging rule's guardrails apply to source code (e.g., `console.log` use,
+  PII in logs, `catch {}` empty blocks). Its `paths` MUST include source code
+  extensions (`**/*.ts`, `**/*.py`, `**/*.java`, etc.), not just config files.
+- An environment-config rule's guardrails apply to `.env*`, `*.config.*`,
+  and similar. Its `paths` must include those.
+- A CI/CD rule's guardrails often span both — CI YAML AND source code
+  (e.g., "no hardcoded API origin in source", "no direct edits to generated
+  client"). Its `paths` must include both categories.
+
+Do NOT copy `paths` verbatim across sibling rule files in the same category.
+Each file is evaluated independently based on what it enforces. The Pass 3
+prompt now specifies per-file paths for `40.infra/*` — follow those EXACTLY,
+do not substitute a category-level shortcut.
+
+When generating a rule file, re-read the file's own guardrail content and
+verify: "When should Claude Code auto-load this rule?" The answer determines
+paths. If the answer is "when editing TypeScript source", paths must include
+`**/*.ts` / `**/*.tsx` — not `**/*.json`.
+
+CRITICAL — CLAUDE.md Scaffold Compliance:
+CLAUDE.md generation MUST follow the scaffold at:
+`pass-prompts/templates/common/claude-md-scaffold.md`
+
+The scaffold enforces EXACTLY 8 top-level (##) sections with FIXED
+titles and order (canonical English names below — emit each heading
+in the target output language with equivalent meaning):
+1. Role Definition
+2. Project Overview
+3. Build & Run Commands
+4. Core Architecture
+5. Directory Structure
+6. Standard / Rules / Skills Reference
+7. DO NOT Read (Files Not to Be Read Directly)
+8. Common Rules & Memory (L4)
+
+Before finalizing, verify:
+- Exactly 8 `##` sections (no more, no less)
+- Section titles match the scaffold's FIXED names (in the target output language)
+- Section order matches
+- Section 1 is exactly 2 lines (role + PROJECT_CONTEXT)
+- Section 6 has EXACTLY 3 sub-sections (Standard / Rules / Skills — no "Guide" sub-section)
+- Section 7 includes the 3 common claudeos-core/* entries 
+  (guide/, generated/, mcp-guide/)
+- Section 8 has EXACTLY 2 sub-sections:
+  - `### Common Rules (auto-loaded on every edit)` — meta-summary table
+    of `paths: ["**/*"]` rules (typically
+    `00.core/51.doc-writing-rules.md` and `00.core/52.ai-work-rules.md`)
+  - `### L4 Memory (on-demand reference)` — intro + 4-row memory file
+    table + 6-step workflow, EACH APPEARING EXACTLY ONCE
+
+Do NOT add any of these as `##`-level sections (forbidden at top level
+— match by semantic meaning in ANY output language; canonical English
+labels below):
+- "Required to Observe While Working"
+- "Rules Summary"
+- "Documentation Writing Rules" (as standalone `##`)
+- "AI Common Rules" / "AI Work Rules" (as standalone `##`)
+- "L4 Memory Integration Rules" / "Memory Layer (L4)" (as standalone
+  `##` — L4 memory belongs as sub-section inside Section 8)
+- "Common Rules" (as standalone `##` — common rules belong as sub-section
+  inside Section 8, NOT as their own top-level section)
+- "L4 Memory Files (Re-declaration)" / any restatement of the memory
+  table — the L4 memory table appears EXACTLY ONCE in the entire
+  CLAUDE.md, inside Section 8 sub-section 2
+- Any `##`-level title with the semantic meaning of "rules" beyond
+  Section 8's "Common Rules & Memory (L4)" top-level title
+
+Where common-rule information DOES belong:
+- `##`-level: Section 8 sub-section 1 (`### Common Rules (auto-loaded
+  on every edit)`). Include a meta-summary table with columns
+  `| Rule File | Role | Core Enforcement |` (column labels emitted in
+  target output language). The "Core Enforcement" column is a ONE-LINE
+  meta summary of each rule, NOT a copy of the rule body. Example:
+    `| 00.core/51.doc-writing-rules.md | Documentation writing rules
+     | paths required, no domain/absolute-path hardcoding, ## Reference
+     section required |`
+- The rule BODY itself lives in `.claude/rules/00.core/51.*.md` and is
+  auto-loaded; CLAUDE.md only summarizes "what this rule enforces",
+  one line per rule.
+
+POST-GENERATION CHECK (mandatory):
+After writing CLAUDE.md, count `^## ` headings. The count MUST be exactly 8.
+If 9 or more, locate the surplus section(s) and apply the correct remedy:
+- Surplus "Common Rules" (`##` level) → convert content into Section 8 sub-section 1
+- Surplus "Memory Layer (L4)" / "L4 Memory Files (Re-declaration)" →
+  DELETE it entirely; the L4 memory belongs exactly once in Section 8
+  sub-section 2
+- Surplus "Required to Observe While Working" / "Rules Summary" → move
+  enforcement content into `.claude/rules/*`, do not carry into CLAUDE.md
+- Surplus structural information → merge into the matching Section 1-7
+Do not move on until the count is exactly 8 AND Section 8 contains
+exactly 2 sub-sections with no internal duplication.
+
+CRITICAL — CLAUDE.md Does Not Duplicate Rules:
+CLAUDE.md describes STRUCTURE (overview, architecture, directory, references),
+not enforcement rules. It MUST NOT list or restate rules that are already
+(or should be) enforced by .claude/rules/* or documented in claudeos-core/standard/*.
+
+Examples of what does NOT belong in CLAUDE.md:
+- Coding rules (hardcoding prohibition, `any` casting, naming conventions)
+  → these go in .claude/rules/00.core/* or 03.naming-conventions.md
+- Domain-specific rules (XSS prevention in specific components, response envelope)
+  → these go in .claude/rules/{domain}/* or standard/{domain}/
+- Multi-file sync rules (routePath + routeComponentMap sync)
+  → these go in .claude/rules/{domain}/* with paths glob
+- Work procedures (Entity → DTO → Controller order)
+  → these go in claudeos-core/skills/* or claudeos-core/guide/02.usage/
+
+Section 1 "Role Definition" may reference that rules exist at a high
+level (the scaffold's PROJECT_CONTEXT mentions architecture style),
+but it does NOT enumerate rules. Section 6 "Standard / Rules / Skills
+Reference" provides a REFERENCE INDEX (what exists), not rule content.
+
 After completion, run the following commands in order:
 1. npx claudeos-core health

package/pass-prompts/templates/common/pass4.md

@@ -195,9 +195,12 @@ Proposals with confidence >= 0.70 deserve serious consideration. Do NOT edit pro
 ### 11. Append a new section to existing `CLAUDE.md`
 
 Do NOT overwrite existing CLAUDE.md content — **append only** at the end.
-The new section must include the `(L4)` marker in its top heading (the marker
-is language-independent so the CLI fallback can detect it). For example, English:
-`## Memory (L4)`, Korean: `## 메모리 (L4)`.
+The new section must include the `(L4)` marker in its top heading (the
+marker string itself is language-independent so the CLI fallback can
+detect it). The heading word is translated into the target output
+language, while `(L4)` is preserved verbatim. Example: English emits
+`## Memory (L4)`; other languages emit the equivalent translation of
+"Memory" followed by the same `(L4)` suffix.
 
 Include:
 - Common rules table (references to `00.core/51.doc-writing-rules.md` and `52.ai-work-rules.md`)

package/pass-prompts/templates/common/staging-override.md

@@ -12,7 +12,7 @@ Examples (write-target redirect, **subpath preserved**):
 |---|---|
 | `.claude/rules/00.core/00.standard-reference.md` | `claudeos-core/generated/.staged-rules/00.core/00.standard-reference.md` |
 | `.claude/rules/10.backend/01.controller-rules.md` | `claudeos-core/generated/.staged-rules/10.backend/01.controller-rules.md` |
-| `.claude/rules/50.sync/01.standard-sync.md` | `claudeos-core/generated/.staged-rules/50.sync/01.standard-sync.md` |
+| `.claude/rules/50.sync/01.doc-sync.md` | `claudeos-core/generated/.staged-rules/50.sync/01.doc-sync.md` |
 | `.claude/rules/60.memory/01.decision-log.md` | `claudeos-core/generated/.staged-rules/60.memory/01.decision-log.md` |
 
 **Important clarifications:**

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

@@ -52,20 +52,28 @@ Similarly, if an Aggregator/Orchestrator layer exists, its responsibilities
 MUST be described identically across architecture.md, controller-patterns.md,
 response-exception.md, and all skills files.
 
-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.
-Alternatively, add a note directing readers to .claude/rules/00.core/00.standard-reference.md
-for the complete list.
-
 Generation targets:
 
 1. CLAUDE.md (project root)
-   - Role definition (based on detected stack)
-   - Build & Run Commands (Gradle/Maven)
-   - Core architecture diagram
-   - DB table naming conventions
-   - Standard/Skills/Guide reference table
+
+   Follow the scaffold EXACTLY:
+   → `pass-prompts/templates/common/claude-md-scaffold.md`
+
+   The scaffold enforces an 8-section deterministic structure:
+   1. Role Definition → 2. Project Overview → 3. Build & Run Commands →
+   4. Core Architecture → 5. Directory Structure → 6. Standard / Rules / Skills Reference →
+   7. DO NOT Read → 8. Common Rules & Memory (L4)
+
+   All section titles, order, and formats are FIXED by the scaffold.
+   Content within each section adapts to this project based on pass2-merged.json.
+   The scaffold's validation checklist MUST pass.
+
+   Stack-specific hints for this project (Java Spring Boot):
+   - Project type for Section 1 PROJECT_CONTEXT: "Backend Application" or "REST API Server"
+   - Architecture diagram (Section 4): layered architecture (Controller → Service → Mapper/Repository)
+   - Section 2 should include: JDK version, Gradle/Maven, DB, session/cache, server port
+   - DB naming conventions belong in standard/00.core/03.naming-conventions.md (not CLAUDE.md)
+   - Multi-DB projects: generalize to "Dual RDBMS" in Section 1, specify actual DBs in Section 2
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, modules, API server info
@@ -105,8 +113,11 @@ Generation targets:
      - `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
+     - `40.infra/01.environment-config-rules.md` paths: `["**/*.properties", "**/*.yml", "**/*.yaml", "**/.env*", "**/config/**", "**/application*.properties"]` — Spring config files
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.java", "**/logback*.xml", "**/log4j*.xml"]` — source code where logs live + log config
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.gradle*", "**/pom.xml", "**/*.java"]` — CI / build config + source
      - `50.sync/*` rules: `paths: ["**/claudeos-core/**", "**/.claude/**"]` — loaded only when editing claudeos-core files
+     - `60.memory/*` rules: forward reference — Pass 4 will generate 4 files (01.decision-log, 02.failure-patterns, 03.compaction, 04.auto-rule-update), each with file-specific `paths`. Pass 3 must STILL list ```.claude/rules/60.memory/*``` as a row in CLAUDE.md Section 6 Rules table so developers/Claude see the category exists.
    - 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:
      ```
      ---
@@ -121,6 +132,7 @@ Generation targets:
      - 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
+     - claudeos-core/standard/00.core/04.doc-writing-guide.md
      ## Backend API
      - claudeos-core/standard/10.backend-api/01.controller-patterns.md
      - claudeos-core/standard/10.backend-api/02.service-patterns.md
@@ -138,18 +150,16 @@ Generation targets:
      - claudeos-core/standard/40.infra/03.cicd-deployment.md
      - claudeos-core/standard/50.verification/01.development-verification.md
      - claudeos-core/standard/50.verification/02.testing-strategy.md
-     ## DO NOT Read (context waste)
-     - claudeos-core/generated/ — Build metadata. Not for coding reference.
-     - claudeos-core/guide/ — Onboarding/usage guides for humans. Not for coding reference.
-     - claudeos-core/mcp-guide/ — MCP server integration docs. Not for coding reference.
      ```
-     List only the standard files that were actually generated above. Include frontend standards only if frontend was detected.
+     List only the standard files that were actually generated above. Include frontend standards only if frontend was detected. NOTE: `00.core/04.doc-writing-guide.md` is a FORWARD REFERENCE — Pass 4 will generate it; include it anyway. Do NOT add a "DO NOT Read" section here — that information lives in CLAUDE.md Section 7 (the single source of truth).
 
-4. .claude/rules/50.sync/ (3 sync rules — AI fallback reminders)
+4. .claude/rules/50.sync/ (2 sync rules — AI fallback reminders)
    - NOTE: These rules remind AI to run `npx claudeos-core refresh` after modifying standard/rules/skills files.
-   - 01.standard-sync.md — Remind AI to update corresponding rule when standard is modified
-   - 02.rules-sync.md — Remind AI to update corresponding standard when rules are modified
-   - 03.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
+   - 01.doc-sync.md — Bidirectional standard ↔ rules sync reminder (both directions in ONE rule).
+     Do NOT generate a separate 02.rules-sync.md mirror file — redundant.
+     Express the mapping as a naming convention (standard/<N>.<dir>/<M>.<n>.md ↔
+     .claude/rules/<N>.<dir>/<M>.<n>-rules.md), NOT a hardcoded file-to-file table.
+   - 02.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
 
 5. claudeos-core/skills/ (active domains only)
    - 10.backend-crud/01.scaffold-crud-feature.md (orchestrator)

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

@@ -51,21 +51,31 @@ its responsibilities (DTO↔VO conversion, multi-service orchestration, response
 MUST be described identically across architecture.md, controller-patterns.md,
 response-exception.md, and all skills files.
 
-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.
-Alternatively, add a note directing readers to .claude/rules/00.core/00.standard-reference.md
-for the complete list.
-
 Generation targets:
 
 1. CLAUDE.md (project root)
-   - Role definition (Kotlin + Spring Boot + multi-module, mention CQRS if detected)
-   - Build & Run Commands (Gradle tasks per module, e.g., :servers:command:reservation-command-server:bootRun)
-   - Multi-module architecture diagram (BFF → Feign → Command/Query → DB)
-   - Module list with ports and roles
-   - DB table naming conventions
-   - Standard/Skills/Guide reference table
+
+   Follow the scaffold EXACTLY:
+   → `pass-prompts/templates/common/claude-md-scaffold.md`
+
+   The scaffold enforces an 8-section deterministic structure:
+   1. Role Definition → 2. Project Overview → 3. Build & Run Commands →
+   4. Core Architecture → 5. Directory Structure → 6. Standard / Rules / Skills Reference →
+   7. DO NOT Read → 8. Common Rules & Memory (L4)
+
+   All section titles, order, and formats are FIXED by the scaffold.
+   Content within each section adapts to this project based on pass2-merged.json.
+   The scaffold's validation checklist MUST pass.
+
+   Stack-specific hints for this project (Kotlin + Spring Boot):
+   - Project type for Section 1 PROJECT_CONTEXT: "Backend Application"
+     (when CQRS/BFF is detected, reflect as e.g. "CQRS-based Microservices")
+   - Multi-module projects: represent in Section 4 diagram and Section 5 tree
+   - Architecture diagram (Section 4): BFF → Feign → Command/Query → DB (if CQRS detected)
+   - Module ports and roles: include in Section 2 Project Overview (generic form)
+   - DB naming conventions: belong in standard/00.core/03.naming-conventions.md (not CLAUDE.md)
+   - Gradle tasks per module: Section 3 examples should show the pattern generically
+     then let developers refer to build.gradle.kts for specifics
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack (Kotlin version, Spring Boot version), module list, server ports
@@ -108,8 +118,11 @@ Generation targets:
      - `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
+     - `40.infra/01.environment-config-rules.md` paths: `["**/*.properties", "**/*.yml", "**/*.yaml", "**/.env*", "**/config/**", "**/application*.properties"]` — Spring config files
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.kt", "**/*.kts", "**/logback*.xml"]` — source code where logs live + log config
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.gradle*", "**/*.kt", "**/*.kts"]` — CI / build config + source
      - `50.sync/*` rules: `paths: ["**/claudeos-core/**", "**/.claude/**"]` — loaded only when editing claudeos-core files
+     - `60.memory/*` rules: forward reference — Pass 4 will generate 4 files (01.decision-log, 02.failure-patterns, 03.compaction, 04.auto-rule-update), each with file-specific `paths`. Pass 3 must STILL list ```.claude/rules/60.memory/*``` as a row in CLAUDE.md Section 6 Rules table so developers/Claude see the category exists.
    - 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:
      ```
      ---
@@ -124,6 +137,7 @@ Generation targets:
      - 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
+     - claudeos-core/standard/00.core/04.doc-writing-guide.md
      ## Backend API
      - claudeos-core/standard/10.backend-api/01.controller-patterns.md
      - claudeos-core/standard/10.backend-api/02.service-patterns.md
@@ -143,18 +157,16 @@ Generation targets:
      - claudeos-core/standard/40.infra/03.cicd-deployment.md
      - claudeos-core/standard/50.verification/01.development-verification.md
      - claudeos-core/standard/50.verification/02.testing-strategy.md
-     ## DO NOT Read (context waste)
-     - claudeos-core/generated/ — Build metadata. Not for coding reference.
-     - claudeos-core/guide/ — Onboarding/usage guides for humans. Not for coding reference.
-     - claudeos-core/mcp-guide/ — MCP server integration docs. Not for coding reference.
      ```
-     List only the standard files that were actually generated above. Include frontend standards only if frontend was detected.
+     List only the standard files that were actually generated above. Include frontend standards only if frontend was detected. NOTE: `00.core/04.doc-writing-guide.md` is a FORWARD REFERENCE — Pass 4 will generate it; include it anyway. Do NOT add a "DO NOT Read" section here — that information lives in CLAUDE.md Section 7 (the single source of truth).
 
-4. .claude/rules/50.sync/ (3 sync rules — AI fallback reminders)
+4. .claude/rules/50.sync/ (2 sync rules — AI fallback reminders)
    - NOTE: These rules remind AI to run `npx claudeos-core refresh` after modifying standard/rules/skills files.
-   - 01.standard-sync.md — Remind AI to update corresponding rule when standard is modified
-   - 02.rules-sync.md — Remind AI to update corresponding standard when rules are modified
-   - 03.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
+   - 01.doc-sync.md — Bidirectional standard ↔ rules sync reminder (both directions in ONE rule).
+     Do NOT generate a separate 02.rules-sync.md mirror file — redundant.
+     Express the mapping as a naming convention (standard/<N>.<dir>/<M>.<n>.md ↔
+     .claude/rules/<N>.<dir>/<M>.<n>-rules.md), NOT a hardcoded file-to-file table.
+   - 02.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
 
 5. claudeos-core/skills/ (active domains only)
    - 10.backend-crud/01.scaffold-crud-feature.md (orchestrator — CQRS-aware: creates both command and query modules)

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

@@ -29,20 +29,27 @@ Determine from pass2-merged.json which layer (Controller/Router vs Service/UseCa
 the response wrapper. This MUST be identical across architecture.md, controller/router-patterns.md,
 response-exception.md, and controller-rules.md. Do NOT describe different response flows in different files.
 
-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.
-Alternatively, add a note directing readers to .claude/rules/00.core/00.standard-reference.md
-for the complete list.
-
 Generation targets:
 
 1. CLAUDE.md (project root)
-   - Role definition (based on detected stack)
-   - Build & Run Commands (use ONLY the detected packageManager — never hardcode npm/yarn/pnpm)
-   - Core architecture diagram
-   - DB table/collection naming
-   - Standard/Skills/Guide reference table
+
+   Follow the scaffold EXACTLY:
+   → `pass-prompts/templates/common/claude-md-scaffold.md`
+
+   The scaffold enforces an 8-section deterministic structure:
+   1. Role Definition → 2. Project Overview → 3. Build & Run Commands →
+   4. Core Architecture → 5. Directory Structure → 6. Standard / Rules / Skills Reference →
+   7. DO NOT Read → 8. Common Rules & Memory (L4)
+
+   All section titles, order, and formats are FIXED by the scaffold.
+   Content within each section adapts to this project based on pass2-merged.json.
+   The scaffold's validation checklist MUST pass.
+
+   Stack-specific hints for this project (Node.js Express):
+   - Project type for Section 1 PROJECT_CONTEXT: "API Server" or the actual character of the project
+   - Architecture diagram (Section 4): middleware → route → controller → service layers
+   - Use ONLY the detected packageManager in Section 3 (never mix npm/yarn/pnpm)
+   - DB naming conventions: belong in standard/00.core/03.naming-conventions.md (not CLAUDE.md)
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, modules, API server info
@@ -81,8 +88,11 @@ Generation targets:
      - `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
+     - `40.infra/01.environment-config-rules.md` paths: `["**/.env*", "**/config/**", "**/*.json"]` — env / config files
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"]` — source code where logs live
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.ts", "**/*.js"]` — CI config + source
      - `50.sync/*` rules: `paths: ["**/claudeos-core/**", "**/.claude/**"]` — loaded only when editing claudeos-core files
+     - `60.memory/*` rules: forward reference — Pass 4 will generate 4 files (01.decision-log, 02.failure-patterns, 03.compaction, 04.auto-rule-update), each with file-specific `paths`. Pass 3 must STILL list ```.claude/rules/60.memory/*``` as a row in CLAUDE.md Section 6 Rules table so developers/Claude see the category exists.
    - 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:
      ```
      ---
@@ -97,6 +107,7 @@ Generation targets:
      - 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
+     - claudeos-core/standard/00.core/04.doc-writing-guide.md
      ## Backend API
      - claudeos-core/standard/10.backend-api/01.router-controller-patterns.md
      - claudeos-core/standard/10.backend-api/02.service-patterns.md
@@ -114,18 +125,16 @@ Generation targets:
      - claudeos-core/standard/40.infra/03.cicd-deployment.md
      - claudeos-core/standard/50.verification/01.development-verification.md
      - claudeos-core/standard/50.verification/02.testing-strategy.md
-     ## DO NOT Read (context waste)
-     - claudeos-core/generated/ — Build metadata. Not for coding reference.
-     - claudeos-core/guide/ — Onboarding/usage guides for humans. Not for coding reference.
-     - claudeos-core/mcp-guide/ — MCP server integration docs. Not for coding reference.
      ```
-     List only the standard files that were actually generated above.
+     List only the standard files that were actually generated above. NOTE: `00.core/04.doc-writing-guide.md` is a FORWARD REFERENCE — Pass 4 will generate it; include it anyway. Do NOT add a "DO NOT Read" section here — that information lives in CLAUDE.md Section 7 (the single source of truth).
 
-4. .claude/rules/50.sync/ (3 sync rules — AI fallback reminders)
+4. .claude/rules/50.sync/ (2 sync rules — AI fallback reminders)
    - NOTE: These rules remind AI to run `npx claudeos-core refresh` after modifying standard/rules/skills files.
-   - 01.standard-sync.md — Remind AI to update corresponding rule when standard is modified
-   - 02.rules-sync.md — Remind AI to update corresponding standard when rules are modified
-   - 03.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
+   - 01.doc-sync.md — Bidirectional standard ↔ rules sync reminder (both directions in ONE rule).
+     Do NOT generate a separate 02.rules-sync.md mirror file — redundant.
+     Express the mapping as a naming convention (standard/<N>.<dir>/<M>.<n>.md ↔
+     .claude/rules/<N>.<dir>/<M>.<n>-rules.md), NOT a hardcoded file-to-file table.
+   - 02.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
 
 5. claudeos-core/skills/ (active domains only)
    - 10.backend-crud/01.scaffold-crud-feature.md (orchestrator)

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

@@ -27,18 +27,27 @@ Determine from pass2-merged.json which layer (route handler vs service/plugin) c
 the response wrapper. This MUST be identical across architecture.md, route-plugin-patterns.md,
 response-exception.md, and all rules files. Do NOT describe different response flows in different files.
 
-CRITICAL — CLAUDE.md Reference Table Completeness:
-The reference table in CLAUDE.md MUST list ALL generated standard files.
-Alternatively, add a note directing readers to .claude/rules/00.core/00.standard-reference.md.
-
 Generation targets:
 
 1. CLAUDE.md (project root)
-   - Role definition (Fastify backend)
-   - Build & Run Commands (use ONLY the detected packageManager)
-   - Core architecture diagram (plugin-based)
-   - DB table/collection naming
-   - Standard/Skills/Guide reference table
+
+   Follow the scaffold EXACTLY:
+   → `pass-prompts/templates/common/claude-md-scaffold.md`
+
+   The scaffold enforces an 8-section deterministic structure:
+   1. Role Definition → 2. Project Overview → 3. Build & Run Commands →
+   4. Core Architecture → 5. Directory Structure → 6. Standard / Rules / Skills Reference →
+   7. DO NOT Read → 8. Common Rules & Memory (L4)
+
+   All section titles, order, and formats are FIXED by the scaffold.
+   Content within each section adapts to this project based on pass2-merged.json.
+   The scaffold's validation checklist MUST pass.
+
+   Stack-specific hints for this project (Node.js Fastify):
+   - Project type for Section 1 PROJECT_CONTEXT: "High-performance API Server" or the actual character of the project
+   - Architecture diagram (Section 4): plugin-based architecture, request lifecycle, hooks
+   - Use ONLY the detected packageManager in Section 3
+   - DB naming conventions: belong in standard/00.core/03.naming-conventions.md (not CLAUDE.md)
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, modules, server info
@@ -73,14 +82,19 @@ Generation targets:
      - `00.core/*` rules: `paths: ["**/*"]`
      - `10.backend/*` rules: `paths: ["**/*"]`
      - `30.security-db/*` rules: `paths: ["**/*"]`
-     - `40.infra/*` rules: `paths: ["**/*.json", "**/*.env*", "**/config/**", "**/Dockerfile*", "**/*.yml", "**/*.yaml"]`
+     - `40.infra/01.environment-config-rules.md` paths: `["**/.env*", "**/config/**", "**/*.json"]` — env / config files
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"]` — source code where logs live
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.ts", "**/*.js"]` — CI config + source
      - `50.sync/*` rules: `paths: ["**/claudeos-core/**", "**/.claude/**"]`
+     - `60.memory/*` rules: forward reference — Pass 4 will generate 4 files (01.decision-log, 02.failure-patterns, 03.compaction, 04.auto-rule-update), each with file-specific `paths`. Pass 3 must STILL list ```.claude/rules/60.memory/*``` as a row in CLAUDE.md Section 6 Rules table so developers/Claude see the category exists.
    - MUST generate `.claude/rules/00.core/00.standard-reference.md` as a directory of all standard files
 
-4. .claude/rules/50.sync/ (3 sync rules)
-   - 01.standard-sync.md
-   - 02.rules-sync.md
-   - 03.skills-sync.md
+4. .claude/rules/50.sync/ (2 sync rules)
+   - 01.doc-sync.md — Bidirectional standard ↔ rules sync reminder (both directions in ONE rule).
+     Do NOT generate a separate 02.rules-sync.md mirror file — redundant.
+     Express the mapping as a naming convention (standard/<N>.<dir>/<M>.<n>.md ↔
+     .claude/rules/<N>.<dir>/<M>.<n>-rules.md), NOT a hardcoded file-to-file table.
+   - 02.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
 
 5. claudeos-core/skills/ (active domains only)
    - 10.backend-crud/01.scaffold-crud-feature.md (orchestrator)

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

@@ -29,18 +29,28 @@ Determine from pass2-merged.json which layer (Controller vs Service/UseCase) cal
 the response wrapper. This MUST be identical across architecture.md, controller-patterns.md,
 response-exception.md, and controller-rules.md. Do NOT describe different response flows in different files.
 
-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.
-
 Generation targets:
 
 1. CLAUDE.md (project root)
-   - Role definition (NestJS backend developer)
-   - Build & Run Commands (use ONLY the detected packageManager)
-   - Core architecture diagram (Module → Controller → Service → Repository)
-   - DB table/collection naming
-   - Standard/Skills/Guide reference table
+
+   Follow the scaffold EXACTLY:
+   → `pass-prompts/templates/common/claude-md-scaffold.md`
+
+   The scaffold enforces an 8-section deterministic structure:
+   1. Role Definition → 2. Project Overview → 3. Build & Run Commands →
+   4. Core Architecture → 5. Directory Structure → 6. Standard / Rules / Skills Reference →
+   7. DO NOT Read → 8. Common Rules & Memory (L4)
+
+   All section titles, order, and formats are FIXED by the scaffold.
+   Content within each section adapts to this project based on pass2-merged.json.
+   The scaffold's validation checklist MUST pass.
+
+   Stack-specific hints for this project (Node.js NestJS):
+   - Project type for Section 1 PROJECT_CONTEXT: "Backend Application" or "API Server"
+   - Architecture diagram (Section 4): Module → Controller → Service → Repository, 
+     with DI container and request lifecycle (middleware → guard → interceptor → pipe → handler)
+   - Use ONLY the detected packageManager in Section 3
+   - DB naming conventions: belong in standard/00.core/03.naming-conventions.md (not CLAUDE.md)
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, modules, API server info
@@ -80,15 +90,20 @@ Generation targets:
      - `00.core/*` rules: `paths: ["**/*"]`
      - `10.backend/*` rules: `paths: ["**/*"]`
      - `30.security-db/*` rules: `paths: ["**/*"]`
-     - `40.infra/*` rules: `paths: ["**/*.json", "**/*.env*", "**/config/**", "**/Dockerfile*", "**/*.yml", "**/*.yaml"]`
+     - `40.infra/01.environment-config-rules.md` paths: `["**/.env*", "**/config/**", "**/*.json"]` — env / config files
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.ts", "**/*.tsx"]` — source code where logs live
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.ts"]` — CI config + source
      - `50.sync/*` rules: `paths: ["**/claudeos-core/**", "**/.claude/**"]`
+     - `60.memory/*` rules: forward reference — Pass 4 will generate 4 files (01.decision-log, 02.failure-patterns, 03.compaction, 04.auto-rule-update), each with file-specific `paths`. Pass 3 must STILL list ```.claude/rules/60.memory/*``` as a row in CLAUDE.md Section 6 Rules table so developers/Claude see the category exists.
    - MUST generate `.claude/rules/00.core/00.standard-reference.md` — directory of all standard files.
      List only the standard files that were actually generated above.
 
-4. .claude/rules/50.sync/ (3 sync rules)
-   - 01.standard-sync.md — Remind AI to update corresponding rule when standard is modified
-   - 02.rules-sync.md — Remind AI to update corresponding standard when rules are modified
-   - 03.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
+4. .claude/rules/50.sync/ (2 sync rules)
+   - 01.doc-sync.md — Bidirectional standard ↔ rules sync reminder (both directions in ONE rule).
+     Do NOT generate a separate 02.rules-sync.md mirror file — redundant.
+     Express the mapping as a naming convention (standard/<N>.<dir>/<M>.<n>.md ↔
+     .claude/rules/<N>.<dir>/<M>.<n>-rules.md), NOT a hardcoded file-to-file table.
+   - 02.skills-sync.md — Remind AI to update MANIFEST.md when skills are modified
 
 5. claudeos-core/skills/ (active domains only)
    - 10.backend-crud/01.scaffold-crud-feature.md (orchestrator)