claudeos-core 2.3.1 → 2.4.0

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

@@ -1,6 +1,60 @@
 Read claudeos-core/generated/project-analysis.json and
 perform a deep analysis of the following domains only: {{DOMAIN_GROUP}}
 
+## MANDATORY: Configuration file verification (read before analysis)
+
+Before analyzing domain source code, read the following configuration
+files if they exist in the project root. The stack metadata in
+`project-analysis.json` is produced by a regex-based static analyzer
+and may be incomplete for modern Gradle/Maven projects. Reading these
+files directly gives you the ground truth for Java version, server
+port, active profile, datasource configuration, and logging setup.
+
+Required reads (if the file exists):
+
+1. **`build.gradle` or `build.gradle.kts`** (or **`pom.xml`** for Maven).
+   Specifically check:
+   - Java version: look inside `java { ... }`, `java { toolchain { ... } }`,
+     `sourceCompatibility`, `targetCompatibility`, or `<java.version>` /
+     `<maven.compiler.source>` in pom.xml. If the value is a variable
+     reference (e.g., `sourceCompatibility = "${javaVersion}"`), resolve
+     the variable inside `ext { ... }` or `<properties>`. Record the
+     ACTUAL Java version — do NOT infer "Java 17+" from the Spring
+     Boot version.
+   - Spring Boot version: verify it matches `project-analysis.json`'s
+     frameworkVersion field; if they disagree, trust the build file.
+   - Dependencies that indicate specific patterns (MyBatis/iBatis/JPA,
+     multiple DB drivers, Jasypt, JWT library, Logback extras).
+
+2. **`application.yml` / `application.yaml` / `application.properties`
+   and their profile variants** (`application-{profile}.{yml,yaml,properties}`).
+   Specifically check:
+   - Server port: look for `server.port`. Spring Boot accepts property
+     placeholders with defaults like `port: ${G_PORT:8090}` — extract the
+     default value (the post-colon number) as the ACTUAL port. Do NOT
+     assume "port 8080" from the Spring Boot framework default.
+   - Active profile(s): `spring.profiles.active` and `spring.profiles.group`.
+   - Datasource: every `spring.datasource.*` block (multi-dialect projects
+     declare more than one; a `group` profile block like
+     `"local": "local,postgres"` reveals which DB is active per profile).
+   - Logging configuration file reference: `logging.config` points to
+     the real log setup (e.g., `classpath:logback-app.xml`). Read that
+     file too to understand appenders, levels, and JDBC logging
+     adapters like `log4jdbc`.
+
+3. **Any referenced logging configuration files**: `logback*.xml`,
+   `logback*.groovy`, `log4j*.xml`, `log4j*.properties`,
+   `log4jdbc*.properties`. These reveal the actual logging framework
+   in use (Logback is the Spring Boot default but legacy projects may
+   use Log4j2 or mix with JDBC adapters).
+
+When `project-analysis.json` and the configuration files disagree,
+record the configuration-file value as the truth and note the
+discrepancy in your analysis output. This is the path to eliminate
+"Java 17+" / "port 8080" hallucinations observed in pre-v2.3.2 runs.
+
+## Domain analysis
+
 For each domain, select one representative file per layer, read its code, and analyze it.
 Prioritize files with the richest patterns.
 

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

@@ -79,21 +79,21 @@ Generation targets:
    - 00.core/01.project-overview.md — Stack, modules, API server info
    - 00.core/02.architecture.md — Layer structure, request flow, package structure
    - 00.core/03.naming-conventions.md — Class/DTO/Entity/table naming conventions
-   - 10.backend-api/01.controller-patterns.md — Controller writing rules + examples
-   - 10.backend-api/02.service-patterns.md — Transactions, DI, business logic patterns
-   - 10.backend-api/03.data-access-patterns.md — ORM patterns (tailored to detected MyBatis/JPA/QueryDSL)
-   - 10.backend-api/04.response-exception.md — Response/error handling patterns
-   - 10.backend-api/05.dto-validation.md — DTO writing rules, Validation
-   - 10.backend-api/06.interceptor-filter-aop.md — Middleware, AOP, logging interceptors
-   - 20.frontend-ui/* — (generate only if frontend detected)
+   - 10.backend/01.controller-patterns.md — Controller writing rules + examples
+   - 10.backend/02.service-patterns.md — Transactions, DI, business logic patterns
+   - 10.backend/03.data-access-patterns.md — ORM patterns (tailored to detected MyBatis/JPA/QueryDSL)
+   - 10.backend/04.response-exception.md — Response/error handling patterns
+   - 10.backend/05.dto-validation.md — DTO writing rules, Validation
+   - 10.backend/06.interceptor-filter-aop.md — Middleware, AOP, logging interceptors
+   - 20.frontend/* — (generate only if frontend detected)
    - 30.security-db/01.security-auth.md — Authentication, authorization, CORS
    - 30.security-db/02.database-schema.md — DDL, migrations, audit columns
    - 30.security-db/03.common-utilities.md — Common utilities, constants, Base classes
    - 40.infra/01.environment-config.md — Profiles, environment variables, configuration management
    - 40.infra/02.logging-monitoring.md — Logging standards, monitoring, alerts
    - 40.infra/03.cicd-deployment.md — CI/CD pipeline, deployment strategy
-   - 50.verification/01.development-verification.md — Build, startup, API testing
-   - 50.verification/02.testing-strategy.md — Testing strategy, mocking, coverage
+   - 80.verification/01.development-verification.md — Build, startup, API testing
+   - 80.verification/02.testing-strategy.md — Testing strategy, mocking, coverage
 
    Each file MUST include:
    - Correct examples (✅ code blocks)
@@ -107,17 +107,18 @@ Generation targets:
    - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
      ```
      ## Reference
-     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend-api/01.controller-patterns.md
+     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend/01.controller-patterns.md
      ```
    - `paths:` frontmatter per rule category:
      - `00.core/*` rules: `paths: ["**/*"]` — always loaded (architecture, naming are universally needed)
      - `10.backend/*` rules: `paths: ["**/*"]` — always loaded (backend rules needed for any source editing)
      - `30.security-db/*` rules: `paths: ["**/*"]` — always loaded (cross-cutting concerns)
      - `40.infra/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/02.logging-monitoring-rules.md` paths: `["**/*.java", "**/logback*.xml", "**/logback*.groovy", "**/log4j*.xml", "**/log4j*.properties", "**/log4jdbc*.properties"]` — source code where logs live + log config (covers Logback XML/Groovy DSL, Log4j/Log4j2 XML/properties, and log4jdbc JDBC-logging adapter properties)
      - `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.
+     - `70.domains/*` rules (multi-domain projects only): per-domain rules at `.claude/rules/70.domains/{type}/{domain}-rules.md` (where `{type}` is `backend` or `frontend`, ALWAYS present even in single-stack projects for uniform layout + zero-migration future-proofing), each with a `paths:` glob scoped to that domain's source directories so the rule auto-loads only when editing files within the relevant domain. Folder name is PLURAL (`domains/`) — collection of N per-domain files — and each file inside uses the SINGULAR domain name (`{domain}-rules.md`). DO NOT use `60.domains/` (collides with `60.memory/`) and DO NOT skip the `{type}/` sub-folder. See pass3-footer.md "Per-domain folder convention" for the full rationale.
    - 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:
      ```
      ---
@@ -134,12 +135,12 @@ Generation targets:
      - 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
-     - claudeos-core/standard/10.backend-api/03.data-access-patterns.md
-     - claudeos-core/standard/10.backend-api/04.response-exception.md
-     - claudeos-core/standard/10.backend-api/05.dto-validation.md
-     - claudeos-core/standard/10.backend-api/06.interceptor-filter-aop.md
+     - claudeos-core/standard/10.backend/01.controller-patterns.md
+     - claudeos-core/standard/10.backend/02.service-patterns.md
+     - claudeos-core/standard/10.backend/03.data-access-patterns.md
+     - claudeos-core/standard/10.backend/04.response-exception.md
+     - claudeos-core/standard/10.backend/05.dto-validation.md
+     - claudeos-core/standard/10.backend/06.interceptor-filter-aop.md
      ## Security & DB
      - claudeos-core/standard/30.security-db/01.security-auth.md
      - claudeos-core/standard/30.security-db/02.database-schema.md
@@ -148,8 +149,8 @@ Generation targets:
      - claudeos-core/standard/40.infra/01.environment-config.md
      - claudeos-core/standard/40.infra/02.logging-monitoring.md
      - 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
+     - claudeos-core/standard/80.verification/01.development-verification.md
+     - claudeos-core/standard/80.verification/02.testing-strategy.md
      ```
      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).
 

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

@@ -1,6 +1,51 @@
 Read claudeos-core/generated/project-analysis.json and
 perform a deep analysis of the following domains only: {{DOMAIN_GROUP}}
 
+## MANDATORY: Configuration file verification (read before analysis)
+
+Before analyzing domain source code, read the following configuration
+files if they exist in the project root. The stack metadata in
+`project-analysis.json` is produced by a regex-based static analyzer
+and may be incomplete for modern Gradle/Maven projects. Reading these
+files directly gives you the ground truth for Kotlin/Java version,
+server port, active profile, datasource configuration, and logging.
+
+Required reads (if the file exists):
+
+1. **`build.gradle.kts` or `build.gradle`** (or **`pom.xml`** for Maven).
+   Specifically check:
+   - Kotlin version: look inside `plugins { kotlin("jvm") version "..." }`
+     or `libs.versions.toml`. If it's a variable reference, resolve it.
+   - Java target: look inside `kotlin { jvmToolchain(N) }`,
+     `tasks.withType<KotlinCompile> { kotlinOptions.jvmTarget = "..." }`,
+     or `java { toolchain { languageVersion = JavaLanguageVersion.of(N) } }`.
+     Record the ACTUAL target — do NOT infer from the Spring Boot version.
+   - Spring Boot version: verify it matches `project-analysis.json`'s
+     frameworkVersion field; if they disagree, trust the build file.
+   - Dependencies that indicate specific patterns (Exposed/JPA/jOOQ/R2DBC,
+     multiple DB drivers, Koin/Kodein, coroutines extensions).
+
+2. **`application.yml` / `application.yaml` / `application.properties`
+   and their profile variants** (`application-{profile}.{yml,yaml,properties}`).
+   Specifically check:
+   - Server port: look for `server.port`. Spring Boot accepts property
+     placeholders with defaults like `port: ${PORT:8080}` — extract the
+     default value (the post-colon number) as the ACTUAL port. Do NOT
+     assume "port 8080" from the Spring Boot framework default.
+   - Active profile(s): `spring.profiles.active` and `spring.profiles.group`.
+   - Datasource: every `spring.datasource.*` block.
+   - Logging configuration file reference: `logging.config` points to
+     the real log setup. Read that file too.
+
+3. **Any referenced logging configuration files**: `logback*.xml`,
+   `logback*.groovy`, `log4j*.xml`, `log4j*.properties`.
+
+When `project-analysis.json` and the configuration files disagree,
+record the configuration-file value as the truth and note the
+discrepancy in your analysis output.
+
+## Domain analysis
+
 For each domain, select one representative file per layer, read its code, and analyze it.
 Prioritize files with the richest patterns.
 For multi-module domains, analyze files from EACH module (command, query, bff) separately.

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

@@ -81,23 +81,23 @@ Generation targets:
    - 00.core/01.project-overview.md — Stack (Kotlin version, Spring Boot version), module list, server ports
    - 00.core/02.architecture.md — CQRS architecture, BFF layer, request flow (Client → BFF → Feign → Command/Query → DB), module dependency diagram
    - 00.core/03.naming-conventions.md — Kotlin class/file/package naming, DTO naming (Command vs Query DTOs), module naming
-   - 10.backend-api/01.controller-patterns.md — Command controller vs Query controller rules + examples
-   - 10.backend-api/02.service-patterns.md — Transactions, DI, Kotlin idioms, command/query service separation
-   - 10.backend-api/03.data-access-patterns.md — ORM patterns (tailored to detected JPA/MyBatis/Exposed), read/write DB config
-   - 10.backend-api/04.response-exception.md — Response/error handling patterns, sealed class exceptions
-   - 10.backend-api/05.dto-vo-validation.md — Kotlin data class DTO rules, VO patterns (value class, immutability, equality by value), DTO vs VO usage guide, validation, nullable rules
-   - 10.backend-api/06.aggregate-patterns.md — Aggregate boundary definition, Aggregate Root rules, repository-per-aggregate, inter-aggregate references (by ID only), domain event publishing, Aggregator service patterns (SKIP if no DDD/Aggregate patterns detected in pass2-merged.json)
-   - 10.backend-api/07.bff-feign-patterns.md — BFF controller patterns, Feign Client conventions, response composition, error propagation (SKIP if project-analysis.json shows no BFF/CQRS architecture)
-   - 10.backend-api/08.inter-module-communication.md — Feign contracts, Pub/Sub events, shared library usage rules (SKIP if single-module project without multi-module in project-analysis.json)
-   - 20.frontend-ui/* — (generate only if frontend detected)
+   - 10.backend/01.controller-patterns.md — Command controller vs Query controller rules + examples
+   - 10.backend/02.service-patterns.md — Transactions, DI, Kotlin idioms, command/query service separation
+   - 10.backend/03.data-access-patterns.md — ORM patterns (tailored to detected JPA/MyBatis/Exposed), read/write DB config
+   - 10.backend/04.response-exception.md — Response/error handling patterns, sealed class exceptions
+   - 10.backend/05.dto-vo-validation.md — Kotlin data class DTO rules, VO patterns (value class, immutability, equality by value), DTO vs VO usage guide, validation, nullable rules
+   - 10.backend/06.aggregate-patterns.md — Aggregate boundary definition, Aggregate Root rules, repository-per-aggregate, inter-aggregate references (by ID only), domain event publishing, Aggregator service patterns (SKIP if no DDD/Aggregate patterns detected in pass2-merged.json)
+   - 10.backend/07.bff-feign-patterns.md — BFF controller patterns, Feign Client conventions, response composition, error propagation (SKIP if project-analysis.json shows no BFF/CQRS architecture)
+   - 10.backend/08.inter-module-communication.md — Feign contracts, Pub/Sub events, shared library usage rules (SKIP if single-module project without multi-module in project-analysis.json)
+   - 20.frontend/* — (generate only if frontend detected)
    - 30.security-db/01.security-auth.md — Authentication, authorization, CORS, inter-module auth
    - 30.security-db/02.database-schema.md — DDL, migrations, audit columns, read/write DB separation
    - 30.security-db/03.common-utilities.md — Shared-lib utilities, extension functions, constants, Base classes
    - 40.infra/01.environment-config.md — Profiles, multi-module config, Gradle Kotlin DSL, environment variables
    - 40.infra/02.logging-monitoring.md — kotlin-logging standards, structured logging, distributed tracing
    - 40.infra/03.cicd-deployment.md — CI/CD pipeline, Docker/K8s per module, deployment strategy
-   - 50.verification/01.development-verification.md — Build, startup (per module), API testing
-   - 50.verification/02.testing-strategy.md — Testing strategy (MockK, Kotest), per-module test approach
+   - 80.verification/01.development-verification.md — Build, startup (per module), API testing
+   - 80.verification/02.testing-strategy.md — Testing strategy (MockK, Kotest), per-module test approach
 
    Each file MUST include:
    - Correct examples (✅ code blocks in Kotlin)
@@ -112,17 +112,18 @@ Generation targets:
    - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
      ```
      ## Reference
-     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend-api/01.controller-patterns.md
+     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend/01.controller-patterns.md
      ```
    - `paths:` frontmatter per rule category:
      - `00.core/*` rules: `paths: ["**/*"]` — always loaded (architecture, naming are universally needed)
      - `10.backend/*` rules: `paths: ["**/*"]` — always loaded (backend rules needed for any source editing)
      - `30.security-db/*` rules: `paths: ["**/*"]` — always loaded (cross-cutting concerns)
      - `40.infra/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/02.logging-monitoring-rules.md` paths: `["**/*.kt", "**/*.kts", "**/logback*.xml", "**/logback*.groovy", "**/log4j*.xml", "**/log4j*.properties", "**/log4jdbc*.properties"]` — source code where logs live + log config (covers Logback XML/Groovy DSL, Log4j/Log4j2 XML/properties, and log4jdbc JDBC-logging adapter properties)
      - `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.
+     - `70.domains/*` rules (multi-domain projects only): per-domain rules at `.claude/rules/70.domains/{type}/{domain}-rules.md` (where `{type}` is `backend` or `frontend`, ALWAYS present even in single-stack projects for uniform layout + zero-migration future-proofing), each with a `paths:` glob scoped to that domain's source directories so the rule auto-loads only when editing files within the relevant domain. Folder name is PLURAL (`domains/`) — collection of N per-domain files — and each file inside uses the SINGULAR domain name (`{domain}-rules.md`). DO NOT use `60.domains/` (collides with `60.memory/`) and DO NOT skip the `{type}/` sub-folder. See pass3-footer.md "Per-domain folder convention" for the full rationale.
    - 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:
      ```
      ---
@@ -139,14 +140,14 @@ Generation targets:
      - 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
-     - claudeos-core/standard/10.backend-api/03.data-access-patterns.md
-     - claudeos-core/standard/10.backend-api/04.response-exception.md
-     - claudeos-core/standard/10.backend-api/05.dto-vo-validation.md
-     - claudeos-core/standard/10.backend-api/06.aggregate-patterns.md (if generated)
-     - claudeos-core/standard/10.backend-api/07.bff-feign-patterns.md (if generated)
-     - claudeos-core/standard/10.backend-api/08.inter-module-communication.md (if generated)
+     - claudeos-core/standard/10.backend/01.controller-patterns.md
+     - claudeos-core/standard/10.backend/02.service-patterns.md
+     - claudeos-core/standard/10.backend/03.data-access-patterns.md
+     - claudeos-core/standard/10.backend/04.response-exception.md
+     - claudeos-core/standard/10.backend/05.dto-vo-validation.md
+     - claudeos-core/standard/10.backend/06.aggregate-patterns.md (if generated)
+     - claudeos-core/standard/10.backend/07.bff-feign-patterns.md (if generated)
+     - claudeos-core/standard/10.backend/08.inter-module-communication.md (if generated)
      ## Security & DB
      - claudeos-core/standard/30.security-db/01.security-auth.md
      - claudeos-core/standard/30.security-db/02.database-schema.md
@@ -155,8 +156,8 @@ Generation targets:
      - claudeos-core/standard/40.infra/01.environment-config.md
      - claudeos-core/standard/40.infra/02.logging-monitoring.md
      - 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
+     - claudeos-core/standard/80.verification/01.development-verification.md
+     - claudeos-core/standard/80.verification/02.testing-strategy.md
      ```
      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).
 

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

@@ -55,20 +55,20 @@ Generation targets:
    - 00.core/01.project-overview.md — Stack, modules, API server info
    - 00.core/02.architecture.md — Layer structure, request flow, directory structure
    - 00.core/03.naming-conventions.md — File/variable/type naming conventions
-   - 10.backend-api/01.router-controller-patterns.md — Routing patterns + middleware
-   - 10.backend-api/02.service-patterns.md — DI, transactions, business logic
-   - 10.backend-api/03.data-access-patterns.md — ORM patterns, query optimization
-   - 10.backend-api/04.response-exception.md — Response/error handling patterns
-   - 10.backend-api/05.validation-dto.md — Validation, DTO patterns
-   - 10.backend-api/06.middleware-interceptor.md — Middleware, Guard, Interceptor
+   - 10.backend/01.router-controller-patterns.md — Routing patterns + middleware
+   - 10.backend/02.service-patterns.md — DI, transactions, business logic
+   - 10.backend/03.data-access-patterns.md — ORM patterns, query optimization
+   - 10.backend/04.response-exception.md — Response/error handling patterns
+   - 10.backend/05.validation-dto.md — Validation, DTO patterns
+   - 10.backend/06.middleware-interceptor.md — Middleware, Guard, Interceptor
    - 30.security-db/01.security-auth.md — JWT, Guard, CORS, Rate Limit
    - 30.security-db/02.database-schema.md — Migrations, seeds, schema conventions
    - 30.security-db/03.common-utilities.md — Common utils, helpers, constants
    - 40.infra/01.environment-config.md — Environment variables, config management
    - 40.infra/02.logging-monitoring.md — Logging standards, monitoring, alerts
    - 40.infra/03.cicd-deployment.md — CI/CD pipeline, deployment strategy
-   - 50.verification/01.development-verification.md — Build, startup, API testing
-   - 50.verification/02.testing-strategy.md — Testing strategy, mocking, coverage
+   - 80.verification/01.development-verification.md — Build, startup, API testing
+   - 80.verification/02.testing-strategy.md — Testing strategy, mocking, coverage
 
    Each file MUST include:
    - Correct examples (✅ code blocks)
@@ -82,7 +82,7 @@ Generation targets:
    - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
      ```
      ## Reference
-     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend-api/01.router-controller-patterns.md
+     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend/01.router-controller-patterns.md
      ```
    - `paths:` frontmatter per rule category:
      - `00.core/*` rules: `paths: ["**/*"]` — always loaded (architecture, naming are universally needed)
@@ -93,6 +93,7 @@ Generation targets:
      - `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.
+     - `70.domains/*` rules (multi-domain projects only): per-domain rules at `.claude/rules/70.domains/{type}/{domain}-rules.md` (where `{type}` is `backend` or `frontend`, ALWAYS present even in single-stack projects for uniform layout + zero-migration future-proofing), each with a `paths:` glob scoped to that domain's source directories so the rule auto-loads only when editing files within the relevant domain. Folder name is PLURAL (`domains/`) — collection of N per-domain files — and each file inside uses the SINGULAR domain name (`{domain}-rules.md`). DO NOT use `60.domains/` (collides with `60.memory/`) and DO NOT skip the `{type}/` sub-folder. See pass3-footer.md "Per-domain folder convention" for the full rationale.
    - 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:
      ```
      ---
@@ -109,12 +110,12 @@ Generation targets:
      - 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
-     - claudeos-core/standard/10.backend-api/03.data-access-patterns.md
-     - claudeos-core/standard/10.backend-api/04.response-exception.md
-     - claudeos-core/standard/10.backend-api/05.validation-dto.md
-     - claudeos-core/standard/10.backend-api/06.middleware-interceptor.md
+     - claudeos-core/standard/10.backend/01.router-controller-patterns.md
+     - claudeos-core/standard/10.backend/02.service-patterns.md
+     - claudeos-core/standard/10.backend/03.data-access-patterns.md
+     - claudeos-core/standard/10.backend/04.response-exception.md
+     - claudeos-core/standard/10.backend/05.validation-dto.md
+     - claudeos-core/standard/10.backend/06.middleware-interceptor.md
      ## Security & DB
      - claudeos-core/standard/30.security-db/01.security-auth.md
      - claudeos-core/standard/30.security-db/02.database-schema.md
@@ -123,8 +124,8 @@ Generation targets:
      - claudeos-core/standard/40.infra/01.environment-config.md
      - claudeos-core/standard/40.infra/02.logging-monitoring.md
      - 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
+     - claudeos-core/standard/80.verification/01.development-verification.md
+     - claudeos-core/standard/80.verification/02.testing-strategy.md
      ```
      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).
 

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

@@ -53,24 +53,24 @@ Generation targets:
    - 00.core/01.project-overview.md — Stack, modules, server info
    - 00.core/02.architecture.md — Plugin architecture, request lifecycle, hooks flow
    - 00.core/03.naming-conventions.md — File/route/schema/plugin naming conventions
-   - 10.backend-api/01.route-plugin-patterns.md — Route registration, plugin encapsulation, prefix
-   - 10.backend-api/02.service-patterns.md — DI (decorators/awilix), business logic
-   - 10.backend-api/03.data-access-patterns.md — ORM patterns, DB plugin lifecycle
-   - 10.backend-api/04.response-exception.md — Response format, error handling, setErrorHandler
-   - 10.backend-api/05.schema-validation.md — JSON Schema, TypeBox, shared schemas, serialization
-   - 10.backend-api/06.hooks-lifecycle.md — Hook order, scope, authentication hooks
+   - 10.backend/01.route-plugin-patterns.md — Route registration, plugin encapsulation, prefix
+   - 10.backend/02.service-patterns.md — DI (decorators/awilix), business logic
+   - 10.backend/03.data-access-patterns.md — ORM patterns, DB plugin lifecycle
+   - 10.backend/04.response-exception.md — Response format, error handling, setErrorHandler
+   - 10.backend/05.schema-validation.md — JSON Schema, TypeBox, shared schemas, serialization
+   - 10.backend/06.hooks-lifecycle.md — Hook order, scope, authentication hooks
    - 30.security-db/01.security-auth.md — JWT, @fastify/auth, CORS, Rate Limit
    - 30.security-db/02.database-schema.md — Migrations, seeds, schema conventions
    - 30.security-db/03.common-utilities.md — Common utils, decorators, constants
    - 40.infra/01.environment-config.md — @fastify/env, configuration management
    - 40.infra/02.logging-monitoring.md — Pino config, serializers, monitoring
    - 40.infra/03.cicd-deployment.md — CI/CD pipeline, deployment strategy
-   - 50.verification/01.development-verification.md — Build, startup, API testing
-   - 50.verification/02.testing-strategy.md — fastify.inject(), plugin testing, mocking
+   - 80.verification/01.development-verification.md — Build, startup, API testing
+   - 80.verification/02.testing-strategy.md — fastify.inject(), plugin testing, mocking
 
    Each file MUST include:
-   - Correct examples (code blocks)
-   - Incorrect examples (code blocks)
+   - Correct examples (✅ code blocks)
+   - Incorrect examples (❌ code blocks)
    - Key rules summary table
 
 3. .claude/rules/ (active domains only)
@@ -87,6 +87,7 @@ Generation targets:
      - `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.
+     - `70.domains/*` rules (multi-domain projects only): per-domain rules at `.claude/rules/70.domains/{type}/{domain}-rules.md` (where `{type}` is `backend` or `frontend`, ALWAYS present even in single-stack projects for uniform layout + zero-migration future-proofing), each with a `paths:` glob scoped to that domain's source directories so the rule auto-loads only when editing files within the relevant domain. Folder name is PLURAL (`domains/`) — collection of N per-domain files — and each file inside uses the SINGULAR domain name (`{domain}-rules.md`). DO NOT use `60.domains/` (collides with `60.memory/`) and DO NOT skip the `{type}/` sub-folder. See pass3-footer.md "Per-domain folder convention" for the full rationale.
    - MUST generate `.claude/rules/00.core/00.standard-reference.md` as a directory of all standard files
 
 4. .claude/rules/50.sync/ (2 sync rules)

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

@@ -56,21 +56,21 @@ Generation targets:
    - 00.core/01.project-overview.md — Stack, modules, API server info
    - 00.core/02.architecture.md — NestJS module structure, DI container, request lifecycle (middleware → guard → interceptor → pipe → handler → interceptor → filter)
    - 00.core/03.naming-conventions.md — File/variable/type/decorator naming conventions
-   - 10.backend-api/01.controller-patterns.md — @Controller, decorators, parameter binding, response handling
-   - 10.backend-api/02.service-patterns.md — @Injectable, DI, transactions, business logic
-   - 10.backend-api/03.data-access-patterns.md — ORM patterns, repository injection, query optimization
-   - 10.backend-api/04.response-exception.md — Response interceptor, HttpException hierarchy, ExceptionFilter
-   - 10.backend-api/05.validation-dto.md — class-validator, class-transformer, mapped types, ValidationPipe
-   - 10.backend-api/06.guard-interceptor-pipe.md — Guards (auth/role), Interceptors (logging/cache/transform), Pipes (validation/parse)
-   - 10.backend-api/07.module-provider-patterns.md — @Module structure, dynamic modules (forRoot/forFeature), custom providers, global modules
+   - 10.backend/01.controller-patterns.md — @Controller, decorators, parameter binding, response handling
+   - 10.backend/02.service-patterns.md — @Injectable, DI, transactions, business logic
+   - 10.backend/03.data-access-patterns.md — ORM patterns, repository injection, query optimization
+   - 10.backend/04.response-exception.md — Response interceptor, HttpException hierarchy, ExceptionFilter
+   - 10.backend/05.validation-dto.md — class-validator, class-transformer, mapped types, ValidationPipe
+   - 10.backend/06.guard-interceptor-pipe.md — Guards (auth/role), Interceptors (logging/cache/transform), Pipes (validation/parse)
+   - 10.backend/07.module-provider-patterns.md — @Module structure, dynamic modules (forRoot/forFeature), custom providers, global modules
    - 30.security-db/01.security-auth.md — JWT, Passport, Guards, CORS, @nestjs/throttler
    - 30.security-db/02.database-schema.md — Migrations, seeds, schema conventions
    - 30.security-db/03.common-utilities.md — Custom decorators, shared providers, constants
    - 40.infra/01.environment-config.md — @nestjs/config, ConfigModule, environment validation
    - 40.infra/02.logging-monitoring.md — NestJS Logger/pino, LoggingInterceptor, health checks
    - 40.infra/03.cicd-deployment.md — CI/CD pipeline, deployment strategy
-   - 50.verification/01.development-verification.md — Build, startup, API testing
-   - 50.verification/02.testing-strategy.md — Test.createTestingModule, mocking, E2E
+   - 80.verification/01.development-verification.md — Build, startup, API testing
+   - 80.verification/02.testing-strategy.md — Test.createTestingModule, mocking, E2E
 
    Each file MUST include:
    - Correct examples (✅ code blocks)
@@ -84,7 +84,7 @@ Generation targets:
    - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
      ```
      ## Reference
-     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend-api/01.controller-patterns.md
+     > For detailed patterns and examples, Read: claudeos-core/standard/10.backend/01.controller-patterns.md
      ```
    - `paths:` frontmatter per rule category:
      - `00.core/*` rules: `paths: ["**/*"]`
@@ -95,6 +95,7 @@ Generation targets:
      - `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.
+     - `70.domains/*` rules (multi-domain projects only): per-domain rules at `.claude/rules/70.domains/{type}/{domain}-rules.md` (where `{type}` is `backend` or `frontend`, ALWAYS present even in single-stack projects for uniform layout + zero-migration future-proofing), each with a `paths:` glob scoped to that domain's source directories so the rule auto-loads only when editing files within the relevant domain. Folder name is PLURAL (`domains/`) — collection of N per-domain files — and each file inside uses the SINGULAR domain name (`{domain}-rules.md`). DO NOT use `60.domains/` (collides with `60.memory/`) and DO NOT skip the `{type}/` sub-folder. See pass3-footer.md "Per-domain folder convention" for the full rationale.
    - 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.
 

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

@@ -59,18 +59,18 @@ Generation targets:
    - 00.core/01.project-overview.md — Stack, routing approach, deployment environment
    - 00.core/02.architecture.md — App Router structure, component hierarchy, data flow
    - 00.core/03.naming-conventions.md — File/component/hook/type naming conventions
-   - 20.frontend-ui/01.component-patterns.md — Component writing rules, Props patterns, reuse
-   - 20.frontend-ui/02.page-routing-patterns.md — Pages/layouts/dynamic routes/middleware
-   - 20.frontend-ui/03.data-fetching.md — RSC, Server Actions, TanStack Query, caching
-   - 20.frontend-ui/04.state-management.md — Global/server/URL/form state management
-   - 20.frontend-ui/05.styling-patterns.md — Styling rules, theming, responsive, accessibility
-   - 10.backend-api/01.api-routes.md — Route Handlers, Server Actions patterns
+   - 20.frontend/01.component-patterns.md — Component writing rules, Props patterns, reuse
+   - 20.frontend/02.page-routing-patterns.md — Pages/layouts/dynamic routes/middleware
+   - 20.frontend/03.data-fetching.md — RSC, Server Actions, TanStack Query, caching
+   - 20.frontend/04.state-management.md — Global/server/URL/form state management
+   - 20.frontend/05.styling-patterns.md — Styling rules, theming, responsive, accessibility
+   - 10.backend/01.api-routes.md — Route Handlers, Server Actions patterns
    - 30.security-db/01.security-auth.md — NextAuth, middleware, environment variables, CSP
    - 40.infra/01.environment-config.md — Environment variables, next.config, build optimization
    - 40.infra/02.logging-monitoring.md — Error tracking, analytics tools, Web Vitals
    - 40.infra/03.cicd-deployment.md — CI/CD, Vercel/Docker deployment, preview
-   - 50.verification/01.development-verification.md — Build, startup, Lighthouse
-   - 50.verification/02.testing-strategy.md — Testing strategy, RTL, E2E, Storybook
+   - 80.verification/01.development-verification.md — Build, startup, Lighthouse
+   - 80.verification/02.testing-strategy.md — Testing strategy, RTL, E2E, Storybook
 
    Each file MUST include:
    - Correct examples (✅ code blocks)
@@ -84,7 +84,7 @@ Generation targets:
    - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
      ```
      ## Reference
-     > For detailed patterns and examples, Read: claudeos-core/standard/20.frontend-ui/01.component-patterns.md
+     > For detailed patterns and examples, Read: claudeos-core/standard/20.frontend/01.component-patterns.md
      ```
    - `paths:` frontmatter per rule category:
      - `00.core/*` rules: `paths: ["**/*"]` — always loaded (architecture, naming are universally needed)
@@ -96,6 +96,7 @@ Generation targets:
      - `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.
+     - `70.domains/*` rules (multi-domain projects only): per-domain rules at `.claude/rules/70.domains/{type}/{domain}-rules.md` (where `{type}` is `backend` or `frontend`, ALWAYS present even in single-stack projects for uniform layout + zero-migration future-proofing), each with a `paths:` glob scoped to that domain's source directories so the rule auto-loads only when editing files within the relevant domain. Folder name is PLURAL (`domains/`) — collection of N per-domain files — and each file inside uses the SINGULAR domain name (`{domain}-rules.md`). DO NOT use `60.domains/` (collides with `60.memory/`) and DO NOT skip the `{type}/` sub-folder. See pass3-footer.md "Per-domain folder convention" for the full rationale.
    - 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:
      ```
      ---
@@ -112,21 +113,21 @@ Generation targets:
      - 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
-     - claudeos-core/standard/20.frontend-ui/03.data-fetching.md
-     - claudeos-core/standard/20.frontend-ui/04.state-management.md
-     - claudeos-core/standard/20.frontend-ui/05.styling-patterns.md
+     - claudeos-core/standard/20.frontend/01.component-patterns.md
+     - claudeos-core/standard/20.frontend/02.page-routing-patterns.md
+     - claudeos-core/standard/20.frontend/03.data-fetching.md
+     - claudeos-core/standard/20.frontend/04.state-management.md
+     - claudeos-core/standard/20.frontend/05.styling-patterns.md
      ## Backend API
-     - claudeos-core/standard/10.backend-api/01.api-routes.md
+     - claudeos-core/standard/10.backend/01.api-routes.md
      ## Security & DB
      - claudeos-core/standard/30.security-db/01.security-auth.md
      ## Infra & Verification
      - claudeos-core/standard/40.infra/01.environment-config.md
      - claudeos-core/standard/40.infra/02.logging-monitoring.md
      - 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
+     - claudeos-core/standard/80.verification/01.development-verification.md
+     - claudeos-core/standard/80.verification/02.testing-strategy.md
      ```
      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).
 

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

@@ -46,21 +46,21 @@ Generation targets:
    - 00.core/01.project-overview.md — Stack, routing approach, deployment environment
    - 00.core/02.architecture.md — SPA structure, component hierarchy, data flow
    - 00.core/03.naming-conventions.md — File/component/hook/type naming conventions
-   - 20.frontend-ui/01.component-patterns.md — Component writing rules, Props patterns, reuse
-   - 20.frontend-ui/02.page-routing-patterns.md — Client-side routing, layouts, route guards, lazy loading
-   - 20.frontend-ui/03.data-fetching.md — API client, TanStack Query/SWR, caching, error handling
-   - 20.frontend-ui/04.state-management.md — Global/server/URL/form state management
-   - 20.frontend-ui/05.styling-patterns.md — Styling rules, theming, responsive, accessibility
+   - 20.frontend/01.component-patterns.md — Component writing rules, Props patterns, reuse
+   - 20.frontend/02.page-routing-patterns.md — Client-side routing, layouts, route guards, lazy loading
+   - 20.frontend/03.data-fetching.md — API client, TanStack Query/SWR, caching, error handling
+   - 20.frontend/04.state-management.md — Global/server/URL/form state management
+   - 20.frontend/05.styling-patterns.md — Styling rules, theming, responsive, accessibility
    - 30.security-db/01.security-auth.md — Auth patterns, token management, route protection, environment variables
    - 40.infra/01.environment-config.md — Environment variables (VITE_ prefix), vite.config, build optimization
    - 40.infra/02.logging-monitoring.md — Error tracking, analytics tools, performance monitoring
    - 40.infra/03.cicd-deployment.md — CI/CD, static hosting deployment (Nginx, S3, Vercel, Netlify)
-   - 50.verification/01.development-verification.md — Build, startup, dev server
-   - 50.verification/02.testing-strategy.md — Testing strategy (Vitest, RTL, E2E, Storybook)
+   - 80.verification/01.development-verification.md — Build, startup, dev server
+   - 80.verification/02.testing-strategy.md — Testing strategy (Vitest, RTL, E2E, Storybook)
 
    Each file MUST include:
-   - Correct examples (code blocks)
-   - Incorrect examples (code blocks)
+   - Correct examples (✅ code blocks)
+   - Incorrect examples (❌ code blocks)
    - Key rules summary table
 
 3. .claude/rules/ (active domains only)
@@ -70,7 +70,7 @@ Generation targets:
    - Each rule file MUST end with a `## Reference` section linking to the corresponding standard file(s):
      ```
      ## Reference
-     > For detailed patterns and examples, Read: claudeos-core/standard/20.frontend-ui/01.component-patterns.md
+     > For detailed patterns and examples, Read: claudeos-core/standard/20.frontend/01.component-patterns.md
      ```
    - `paths:` frontmatter per rule category:
      - `00.core/*` rules: `paths: ["**/*"]`
@@ -81,6 +81,7 @@ Generation targets:
      - `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.
+     - `70.domains/*` rules (multi-domain projects only): per-domain rules at `.claude/rules/70.domains/{type}/{domain}-rules.md` (where `{type}` is `backend` or `frontend`, ALWAYS present even in single-stack projects for uniform layout + zero-migration future-proofing), each with a `paths:` glob scoped to that domain's source directories so the rule auto-loads only when editing files within the relevant domain. Folder name is PLURAL (`domains/`) — collection of N per-domain files — and each file inside uses the SINGULAR domain name (`{domain}-rules.md`). DO NOT use `60.domains/` (collides with `60.memory/`) and DO NOT skip the `{type}/` sub-folder. See pass3-footer.md "Per-domain folder convention" for the full rationale.
    - MUST generate `.claude/rules/00.core/00.standard-reference.md` — directory of all standard files.
 
 4. .claude/rules/50.sync/ (2 sync rules)