claudeos-core 2.1.0 → 2.2.0

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)

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

@@ -18,17 +18,29 @@ ALL code examples in rules and standards MUST use EXACT method names, class name
 and signatures from pass2-merged.json analysis data.
 Do NOT paraphrase, rename, or infer API names.
 
-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 (based on detected stack — Vite + React SPA)
-   - Build & Run Commands (use ONLY the detected packageManager)
-   - Core architecture diagram (client-side SPA, routing, state management)
-   - 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 (Vite + React SPA):
+   - Project type for Section 1 PROJECT_CONTEXT: "SPA" 
+     (reflect the actual character, e.g., Back Office / Front Office / Full-stack)
+   - Architecture diagram (Section 4): client-side routing, state management, data flow
+   - Detect multi-entry configs (vite.config.*.ts) and reflect in Section 2 / 4 / 5
+   - Detect codegen tools (orval, openapi-generator) and reflect in Section 5 emphasis
+     (auto-generated directories → "Do Not Modify Manually")
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, routing approach, deployment environment
@@ -64,14 +76,19 @@ Generation targets:
      - `00.core/*` rules: `paths: ["**/*"]`
      - `20.frontend/*` rules: `paths: ["**/*"]`
      - `30.security-db/*` rules: `paths: ["**/*"]`
-     - `40.infra/*` rules: `paths: ["**/*.json", "**/*.env*", "**/vite.config.*", "**/Dockerfile*", "**/*.yml", "**/*.yaml"]`
+     - `40.infra/01.environment-config-rules.md` paths: `["**/*.env*", "**/vite.config.*", "**/*.json"]` — env / build 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 with API origin / codegen references
      - `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.
 
-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)
    - 20.frontend-page/01.scaffold-page-feature.md (orchestrator)

package/pass-prompts/templates/python-django/pass3.md

@@ -28,20 +28,29 @@ Determine from pass2-merged.json which layer (View/ViewSet vs Service) calls
 the response wrapper. This MUST be identical across architecture.md, view-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, 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 (pip/poetry, manage.py, gunicorn/uwsgi)
-   - Core architecture diagram
-   - Django app structure
-   - 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 (Python Django):
+   - Project type for Section 1 PROJECT_CONTEXT: "REST API Server" or "Web Application"
+     (when DRF is used, "DRF-based REST API Server"; when detected, e.g., "Async Task Queue + Cache Layer")
+   - Architecture diagram (Section 4): MTV structure, request flow, app structure
+   - Section 3 commands: pip/poetry, manage.py (migrate/runserver/collectstatic), gunicorn/uwsgi
+   - Django apps: list in Section 2 (count only or the main apps), details in Section 5 tree
+   - Detect Celery/Redis/channels and reflect in Section 2 or Section 4 Absent / Not Adopted
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, app list, server info
@@ -80,8 +89,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: ["**/*"]` — always loaded (Django settings are .py files, so infra paths cannot be scoped separately)
+     - `40.infra/01.environment-config-rules.md` paths: `["**/.env*", "**/settings*.py", "**/settings/**/*.py", "**/*.toml", "**/*.cfg"]` — env / Django settings
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.py"]` — source code where logs live
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.py"]` — CI / deploy 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 +108,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.view-patterns.md
      - claudeos-core/standard/10.backend-api/02.serializer-patterns.md
@@ -113,18 +126,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/python-fastapi/pass3.md

@@ -28,20 +28,30 @@ Determine from pass2-merged.json which layer (router/endpoint vs service/CRUD) c
 the response wrapper. This MUST be identical across architecture.md, router-endpoint-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, 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 (pip/poetry, uvicorn, docker)
-   - Core architecture diagram
-   - Module structure
-   - 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 (Python FastAPI):
+   - Project type for Section 1 PROJECT_CONTEXT: "Asynchronous REST API Server"
+     (reflect pydantic-schema-based automatic OpenAPI documentation)
+   - Architecture diagram (Section 4): router → dependency → service → repository,
+     async request lifecycle, pydantic validation
+   - Section 3 commands: pip/poetry install, uvicorn dev, docker deployment
+   - Module structure: reflect in Section 5 tree (routers/, models/, schemas/, services/)
+   - Detect Celery/Redis/SQLAlchemy async and reflect in Section 2 or Section 4
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, modules, server info
@@ -80,8 +90,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: ["**/*.toml", "**/*.env*", "**/config/**", "**/Dockerfile*", "**/*.yml", "**/*.yaml"]` — loaded only for config/infra files
+     - `40.infra/01.environment-config-rules.md` paths: `["**/.env*", "**/config/**", "**/*.toml", "**/*.cfg"]` — env / config files
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.py"]` — source code where logs live
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.py"]` — CI / deploy 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 +109,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-endpoint-patterns.md
      - claudeos-core/standard/10.backend-api/02.schema-pydantic-patterns.md
@@ -113,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)
    - 10.backend-crud/01.scaffold-crud-feature.md (orchestrator)

package/pass-prompts/templates/python-flask/pass3.md

@@ -22,17 +22,30 @@ Determine from pass2-merged.json which layer (route handler vs service layer) fo
 the response. This MUST be identical across architecture.md, route-patterns.md,
 and all rules 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 (based on detected stack — Flask)
-   - Build & Run Commands (pip/poetry, flask run, gunicorn, docker)
-   - Core architecture diagram (application factory, Blueprint structure)
-   - Module structure
-   - 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 (Python Flask):
+   - Project type for Section 1 PROJECT_CONTEXT: "Lightweight Web Application" or "REST API Server"
+     (reflect the application factory pattern and Blueprint structure)
+   - Architecture diagram (Section 4): application factory → Blueprint → route → service,
+     request lifecycle
+   - Section 3 commands: pip/poetry install, flask run (dev), gunicorn (production), docker
+   - Module structure: reflect in Section 5 tree (blueprints/, models/, services/)
+   - Detect SQLAlchemy/marshmallow/WTForms and reflect in Section 2
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, modules, server info
@@ -64,14 +77,19 @@ Generation targets:
      - `00.core/*` rules: `paths: ["**/*"]`
      - `10.backend/*` rules: `paths: ["**/*"]`
      - `30.security-db/*` rules: `paths: ["**/*"]`
-     - `40.infra/*` rules: `paths: ["**/*.json", "**/*.env*", "**/*.cfg", "**/Dockerfile*", "**/*.yml", "**/*.yaml"]`
+     - `40.infra/01.environment-config-rules.md` paths: `["**/.env*", "**/config.py", "**/config/**", "**/*.cfg", "**/*.toml"]` — env / Flask config
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.py"]` — source code where logs live
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.py"]` — CI / deploy 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
 
-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/vue-nuxt/pass3.md

@@ -17,17 +17,31 @@ CRITICAL — Code Example Accuracy:
 ALL code examples MUST use EXACT method names, class names, and signatures from pass2-merged.json.
 Do NOT paraphrase, rename, or infer API names.
 
-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 (Vue/Nuxt frontend developer)
-   - Build & Run Commands (use ONLY the detected packageManager)
-   - 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 (Vue / Nuxt):
+   - Project type for Section 1 PROJECT_CONTEXT: when Nuxt is detected, "Full-stack Web Application"
+     or "SSR/SSG-based SPA"; when pure Vue is detected, "Vue SPA"
+   - Architecture diagram (Section 4): component hierarchy, data flow (useFetch/useAsyncData),
+     Nuxt projects include a Nitro server layer
+   - Use ONLY the detected packageManager in Section 3
+   - Directory structure (Section 5): Nuxt uses auto-routing-based pages/,
+     Vue uses an explicit router-config file structure
+   - Detect the state-management approach (Pinia vs Composables) and reflect in Section 4 Core Patterns
 
 2. claudeos-core/standard/ (active domains only)
    - 00.core/01.project-overview.md — Stack, routing approach, deployment environment
@@ -61,14 +75,19 @@ Generation targets:
      - `10.backend/*` rules: `paths: ["**/*"]`
      - `20.frontend/*` rules: `paths: ["**/*"]`
      - `30.security-db/*` rules: `paths: ["**/*"]`
-     - `40.infra/*` rules: `paths: ["**/*.json", "**/*.env*", "**/nuxt.config.*", "**/vite.config.*", "**/Dockerfile*", "**/*.yml", "**/*.yaml"]`
+     - `40.infra/01.environment-config-rules.md` paths: `["**/.env*", "**/nuxt.config.*", "**/vite.config.*", "**/*.json"]` — env / Nuxt/Vite config
+     - `40.infra/02.logging-monitoring-rules.md` paths: `["**/*.ts", "**/*.tsx", "**/*.vue", "**/*.js"]` — source code (including SFC) where logs live
+     - `40.infra/03.cicd-deployment-rules.md` paths: `["**/*.yml", "**/*.yaml", "**/Dockerfile*", "**/*.ts", "**/*.vue"]` — 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
 
-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-page-feature.md (orchestrator)

package/plan-installer/index.js

@@ -91,6 +91,14 @@ async function main() {
   console.log();
 
   // Save outputs
+  //
+  // Port resolution precedence (stack.port):
+  //   1. stack.port already set by stack-detector (Spring application.yml
+  //      server.port, or .env file PORT variable) — highest authority.
+  //   2. defaultPort fallback below — framework convention, only used when
+  //      the project declares no port of its own. This is a last-resort
+  //      default; prefer that stack-detector extract it from .env.example
+  //      to keep CLAUDE.md truthful to what the project actually runs.
   const defaultPort = (stack.framework === "fastapi" || stack.framework === "django") ? 8000
     : stack.framework === "flask" ? 5000
     : stack.framework === "vite" ? 5173

package/plan-installer/prompt-generator.js

@@ -37,6 +37,23 @@ function generatePrompts(templates, lang, templatesDir, generatedDir) {
   const phase1Path = path.join(commonDir, "pass3-phase1.md");
   const phase1 = existsSafe(phase1Path) ? readFileSafe(phase1Path) + "\n" : "";
 
+  // v2.2: CLAUDE.md Scaffold — the 8-section deterministic template for CLAUDE.md.
+  // Embedded inline (not referenced by path) because the prompt runs in the user's
+  // project directory where the scaffold file does not exist. Stack-specific pass3
+  // templates and pass3-footer both reference "pass-prompts/templates/common/
+  // claude-md-scaffold.md" in their instructions, and this embed makes that
+  // reference resolvable via in-context content. Wrapped in explicit delimiters
+  // so the LLM can reliably locate the scaffold block.
+  const scaffoldPath = path.join(commonDir, "claude-md-scaffold.md");
+  const scaffold = existsSafe(scaffoldPath)
+    ? "\n---\n\n# === EMBEDDED: claude-md-scaffold.md ===\n\n"
+      + "The content below is the scaffold referenced by stack-specific sections\n"
+      + "and the Pass 3 footer. Treat this embedded block as the authoritative\n"
+      + "source when instructions mention `pass-prompts/templates/common/claude-md-scaffold.md`.\n\n"
+      + readFileSafe(scaffoldPath)
+      + "\n\n# === END EMBEDDED: claude-md-scaffold.md ===\n\n---\n\n"
+    : "";
+
   let langInstruction = "";
   if (lang && lang !== "en" && existsSafe(langPath)) {
     const langData = readJsonSafe(langPath);
@@ -100,7 +117,7 @@ function generatePrompts(templates, lang, templatesDir, generatedDir) {
 
     writeFileSafe(
       path.join(generatedDir, "pass3-prompt.md"),
-      header + langInstruction + stagingOverride + phase1 + combinedBody.trimEnd() + "\n" + footer
+      header + langInstruction + stagingOverride + phase1 + scaffold + combinedBody.trimEnd() + "\n" + footer
     );
     console.log(`    ✅ pass3-prompt.md${templates.frontend && templates.backend ? " (multi-stack combined)" : ""}`);
   }

package/plan-installer/stack-detector.js

@@ -9,6 +9,7 @@
 const path = require("path");
 const { glob } = require("glob");
 const { readFileSafe, readJsonSafe, existsSafe } = require("../lib/safe-fs");
+const { readStackEnvInfo } = require("../lib/env-parser");
 
 // ─── Lookup tables ──────────────────────────────────────────────
 
@@ -460,6 +461,21 @@ async function detectStack(ROOT) {
     }
   }
 
+  // ── .env-derived factual config ──
+  // Read .env.example (preferred) or .env to capture ports/hosts/API targets
+  // the project actually declares. This overrides framework-default guesses
+  // in downstream code (plan-installer/index.js defaultPort) and exposes the
+  // full variable map to Pass 3 prompts via project-analysis.json.
+  const envInfo = readStackEnvInfo(ROOT);
+  if (envInfo) {
+    stack.envInfo = envInfo;
+    // Promote .env-declared port to stack.port if no earlier detection won
+    // (e.g., Spring application.yml parsing at line 407).
+    if (!stack.port && envInfo.port) {
+      stack.port = envInfo.port;
+    }
+  }
+
   return stack;
 }