claudeos-core 2.1.1 → 2.3.0

package/pass-prompts/templates/angular/pass3.md

@@ -21,17 +21,27 @@ Determine from pass2-merged.json how data flows between components, services, an
 This MUST be identical across architecture.md, component-patterns.md, http-patterns.md,
 state-management.md, and all rules files. Do NOT describe different data flows in different files.
 
-CRITICAL — CLAUDE.md Reference Table Completeness:
-The reference table in CLAUDE.md MUST list ALL generated standard files.
-
 Generation targets:
 
 1. CLAUDE.md (project root)
-   - Role definition (Angular frontend)
-   - Build & Run Commands (ng serve, ng build, ng test — using detected packageManager)
-   - Core architecture diagram (Module → Component → Service → HTTP)
-   - State management approach
-   - 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 (Angular):
+   - Project type for Section 1 PROJECT_CONTEXT: "Angular-based SPA" or the actual character of the project
+   - Architecture diagram (Section 4): Module → Component → Service → HTTP layers
+   - State management approach goes in Section 4 Core Patterns
+   - Use ng commands (ng serve, ng build, ng test) in Section 3
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack (Angular version, TypeScript version), project structure
@@ -68,14 +78,19 @@ Generation targets:
      - `00.core/*` rules: `paths: ["**/*"]`
      - `20.frontend/*` rules: `paths: ["**/*"]`
      - `30.security-db/*` rules: `paths: ["**/*"]`
-     - `40.infra/*` rules: `paths: ["**/*.json", "**/*.env*", "**/angular.json", "**/Dockerfile*", "**/*.yml", "**/*.yaml"]`
+     - `40.infra/01.environment-config-rules.md` paths: `["**/*.env*", "**/angular.json", "**/environments/**", "**/*.json"]` — env / Angular workspace config
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.ts", "**/*.html"]` — 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` 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)
    - 20.frontend-page/01.scaffold-feature-module.md (orchestrator — Angular feature module scaffolding)