claudeos-core 2.1.1 → 2.3.0

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

@@ -1,26 +1,26 @@
-## CRITICAL — Write path redirect for `.claude/rules/` (tool-access workaround)
-
-Claude Code's sensitive-path policy blocks direct writes under `.claude/` from this subprocess, even with `--dangerously-skip-permissions`. To work around this safely, all rule files must be written to a staging directory and the Node.js orchestrator will move them after you finish.
-
-**Rule (overrides every instruction below):**
-
-> Whenever the instructions below tell you to WRITE a file whose path starts with `.claude/rules/`, write it to `claudeos-core/generated/.staged-rules/` instead, **preserving the subpath exactly**.
-
-Examples (write-target redirect, **subpath preserved**):
-
-| Instruction says to write | You MUST write to |
-|---|---|
-| `.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/60.memory/01.decision-log.md` | `claudeos-core/generated/.staged-rules/60.memory/01.decision-log.md` |
-
-**Important clarifications:**
-
-1. **Prose references stay as-is.** When the instructions or the file content you generate describe `.claude/rules/` as a concept ("Rules (.claude/rules/) and Standards...", "Each rule file in .claude/rules/ links to..."), keep that text literal. Only the **write-target file paths** are redirected. Generated file bodies will eventually live under `.claude/rules/`, so in-body references should point to the final location, not the staging location.
-2. **Frontmatter `paths:` values stay as-is.** These are glob patterns scoped to project files (`"**/*"`, `"**/*.yml"`, etc.), not self-references.
-3. **Do NOT attempt to write to `.claude/rules/` directly** — those writes will be refused by the tool.
-4. **Create missing staging subdirectories as needed.** `claudeos-core/generated/` exists, but subpaths under `.staged-rules/` do not yet.
-5. **This redirect applies to THIS Pass only.** Files written anywhere else (e.g. `claudeos-core/standard/`, `CLAUDE.md`, `claudeos-core/memory/`) are unaffected — write those to their intended paths as stated in the instructions below.
-
----
+## CRITICAL — Write path redirect for `.claude/rules/` (tool-access workaround)
+
+Claude Code's sensitive-path policy blocks direct writes under `.claude/` from this subprocess, even with `--dangerously-skip-permissions`. To work around this safely, all rule files must be written to a staging directory and the Node.js orchestrator will move them after you finish.
+
+**Rule (overrides every instruction below):**
+
+> Whenever the instructions below tell you to WRITE a file whose path starts with `.claude/rules/`, write it to `claudeos-core/generated/.staged-rules/` instead, **preserving the subpath exactly**.
+
+Examples (write-target redirect, **subpath preserved**):
+
+| Instruction says to write | You MUST write to |
+|---|---|
+| `.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.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:**
+
+1. **Prose references stay as-is.** When the instructions or the file content you generate describe `.claude/rules/` as a concept ("Rules (.claude/rules/) and Standards...", "Each rule file in .claude/rules/ links to..."), keep that text literal. Only the **write-target file paths** are redirected. Generated file bodies will eventually live under `.claude/rules/`, so in-body references should point to the final location, not the staging location.
+2. **Frontmatter `paths:` values stay as-is.** These are glob patterns scoped to project files (`"**/*"`, `"**/*.yml"`, etc.), not self-references.
+3. **Do NOT attempt to write to `.claude/rules/` directly** — those writes will be refused by the tool.
+4. **Create missing staging subdirectories as needed.** `claudeos-core/generated/` exists, but subpaths under `.staged-rules/` do not yet.
+5. **This redirect applies to THIS Pass only.** Files written anywhere else (e.g. `claudeos-core/standard/`, `CLAUDE.md`, `claudeos-core/memory/`) are unaffected — write those to their intended paths as stated in the instructions below.
+
+---

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)

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

@@ -29,20 +29,31 @@ Determine from pass2-merged.json which layer handles response formatting (API Ro
 service/utility layer). This MUST be identical across architecture.md, api-routes.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, 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
-   - Directory structure description
-   - 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 (Next.js):
+   - Project type for Section 1 PROJECT_CONTEXT: "Full-stack Web Application"
+     (detect App Router vs Pages Router and reflect, e.g., "Next.js App Router-based")
+   - Architecture diagram (Section 4): server components vs client components,
+     data fetching (server actions / route handlers), middleware flow
+   - Use ONLY the detected packageManager in Section 3
+   - Section 5 tree: distinguish app/ (App Router) vs pages/ (Pages Router) as applicable
+   - Detect codegen tools (orval, graphql-codegen, prisma generate) 
+     and reflect in Section 5 emphasis ("Do Not Modify Manually")
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, routing approach, deployment environment
@@ -80,8 +91,11 @@ Generation targets:
      - `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
+     - `40.infra/01.environment-config-rules.md` paths: `["**/.env*", "**/next.config.*", "**/*.json"]` — env / Next.js config
+     - `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", "**/*.tsx"]` — 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:
      ```
      ---
@@ -96,6 +110,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
      ## Frontend UI
      - claudeos-core/standard/20.frontend-ui/01.component-patterns.md
      - claudeos-core/standard/20.frontend-ui/02.page-routing-patterns.md
@@ -112,18 +127,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)
    - 20.frontend-page/01.scaffold-page-feature.md (orchestrator)