claudeos-core 2.2.0 → 2.3.1

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.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.
-
----
+## 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/node-vite/pass1.md

@@ -1,117 +1,117 @@
-Read claudeos-core/generated/project-analysis.json and
-perform a deep analysis of the following domains only: {{DOMAIN_GROUP}}
-
-For each domain, select one representative file per layer, read its code, and analyze it.
-Prioritize files with the richest patterns.
-
-Analysis items (per domain):
-
-1. Page/Routing Patterns
-   - Client-side routing (React Router, TanStack Router, custom)
-   - Route definition approach (file-based, config-based, lazy loading)
-   - Layout structure (nested layouts, outlet, wrapper components)
-   - Dynamic routes and route parameters
-   - Route guards and authentication redirects
-   - Error/404 handling
-
-2. Component Patterns
-   - Component structure (functional, forwardRef, memo)
-   - Props type definition (interface vs type, Generic usage)
-   - State management (useState, useReducer, external libraries)
-   - Styling approach and exact import paths (e.g., `import styles from './index.module.scss'`, `import { cn } from '@/lib/utils'`)
-   - Styling utility functions: record the EXACT import path used in source code
-   - UI library and exact package names (e.g., `@mui/material`, `antd`, `@shadcn/ui`)
-   - Component classification (UI, Feature, Layout, Page)
-   - Component entry file pattern: is the main file `index.tsx` or `ComponentName.tsx`? Record exactly.
-   - Directory structure pattern: record exact convention
-   - export pattern: default export vs named export in component files
-   - Reuse patterns (composition, compound components, render props)
-   - Accessibility (ARIA, semantic HTML, keyboard navigation)
-
-3. Data Fetching Patterns
-   - Client-side data fetching (TanStack Query, SWR, useEffect, axios)
-   - API client configuration (base URL, interceptors, error handling)
-   - Request/response typing
-   - Caching strategy (query keys, stale time, refetch)
-   - Error/loading state handling
-   - Optimistic updates
-   - Pagination/infinite scroll patterns
-
-4. State Management Patterns
-   - Global state (Zustand, Redux Toolkit, Jotai, Recoil, Context)
-   - Server state (TanStack Query, SWR)
-   - URL state (searchParams, useNavigate)
-   - Form state (React Hook Form, Formik)
-   - Local component state patterns
-
-5. Configuration/Environment Patterns
-   - Environment variable management (VITE_ prefix convention, .env separation)
-   - vite.config settings (proxy, aliases, plugins)
-   - Build optimization (chunk splitting, dynamic imports)
-   - Path aliases (@/, src/)
-
-6. Logging/Monitoring Patterns
-   - Client error tracking (Sentry, DataDog RUM)
-   - Performance monitoring
-   - Analytics tools (Google Analytics, PostHog, Mixpanel)
-
-7. Testing Patterns
-   - Test framework (Vitest, Jest, Playwright, Cypress)
-   - Component testing (React Testing Library, Storybook)
-   - E2E testing strategy
-   - Mocking strategy (MSW, vi.mock)
-   - Test naming conventions
-
-8. Domain-Specific Patterns
-   - Authentication/authorization (session, token, OAuth)
-   - Internationalization (i18next, react-intl)
-   - File upload patterns
-   - Real-time features (WebSocket, SSE)
-   - API versioning strategy
-
-9. Anti-patterns / Inconsistencies
-   - Patterns inconsistent with other domains
-   - Performance issues (unnecessary re-renders, bundle size)
-   - Type safety issues
-   - Accessibility issues
-   - Security issues (XSS, CSRF)
-
-Do not create or modify source files. Analysis only.
-Save results to claudeos-core/generated/pass1-{{PASS_NUM}}.json in the following format:
-
-{
-  "analyzedAt": "ISO timestamp",
-  "passNum": {{PASS_NUM}},
-  "domains": ["auth", "dashboard", "settings", "shared"],
-  "analysisPerDomain": {
-    "dashboard": {
-      "representativeFiles": {
-        "page": "src/pages/dashboard/index.tsx",
-        "component": "src/components/dashboard/StatsCard.tsx",
-        "hook": "src/hooks/useDashboardData.ts",
-        "api": "src/api/dashboard.ts"
-      },
-      "patterns": {
-        "page": { ... },
-        "component": {
-          "entryFilePattern": "index.tsx or ComponentName.tsx",
-          "exportPattern": "default export or named export",
-          "stylingImport": "exact import statement used for styling utility",
-          "uiLibraryImport": "exact import statement for UI components",
-          ...
-        },
-        "dataFetching": { ... },
-        "stateManagement": { ... },
-        "config": { ... },
-        "logging": { ... },
-        "testing": { ... }
-      },
-      "specialPatterns": [],
-      "antiPatterns": []
-    }
-  },
-  "crossDomainCommon": {
-    "description": "Patterns commonly used across domains in this group",
-    "patterns": []
-  }
-}
+Read claudeos-core/generated/project-analysis.json and
+perform a deep analysis of the following domains only: {{DOMAIN_GROUP}}
+
+For each domain, select one representative file per layer, read its code, and analyze it.
+Prioritize files with the richest patterns.
+
+Analysis items (per domain):
+
+1. Page/Routing Patterns
+   - Client-side routing (React Router, TanStack Router, custom)
+   - Route definition approach (file-based, config-based, lazy loading)
+   - Layout structure (nested layouts, outlet, wrapper components)
+   - Dynamic routes and route parameters
+   - Route guards and authentication redirects
+   - Error/404 handling
+
+2. Component Patterns
+   - Component structure (functional, forwardRef, memo)
+   - Props type definition (interface vs type, Generic usage)
+   - State management (useState, useReducer, external libraries)
+   - Styling approach and exact import paths (e.g., `import styles from './index.module.scss'`, `import { cn } from '@/lib/utils'`)
+   - Styling utility functions: record the EXACT import path used in source code
+   - UI library and exact package names (e.g., `@mui/material`, `antd`, `@shadcn/ui`)
+   - Component classification (UI, Feature, Layout, Page)
+   - Component entry file pattern: is the main file `index.tsx` or `ComponentName.tsx`? Record exactly.
+   - Directory structure pattern: record exact convention
+   - export pattern: default export vs named export in component files
+   - Reuse patterns (composition, compound components, render props)
+   - Accessibility (ARIA, semantic HTML, keyboard navigation)
+
+3. Data Fetching Patterns
+   - Client-side data fetching (TanStack Query, SWR, useEffect, axios)
+   - API client configuration (base URL, interceptors, error handling)
+   - Request/response typing
+   - Caching strategy (query keys, stale time, refetch)
+   - Error/loading state handling
+   - Optimistic updates
+   - Pagination/infinite scroll patterns
+
+4. State Management Patterns
+   - Global state (Zustand, Redux Toolkit, Jotai, Recoil, Context)
+   - Server state (TanStack Query, SWR)
+   - URL state (searchParams, useNavigate)
+   - Form state (React Hook Form, Formik)
+   - Local component state patterns
+
+5. Configuration/Environment Patterns
+   - Environment variable management (VITE_ prefix convention, .env separation)
+   - vite.config settings (proxy, aliases, plugins)
+   - Build optimization (chunk splitting, dynamic imports)
+   - Path aliases (@/, src/)
+
+6. Logging/Monitoring Patterns
+   - Client error tracking (Sentry, DataDog RUM)
+   - Performance monitoring
+   - Analytics tools (Google Analytics, PostHog, Mixpanel)
+
+7. Testing Patterns
+   - Test framework (Vitest, Jest, Playwright, Cypress)
+   - Component testing (React Testing Library, Storybook)
+   - E2E testing strategy
+   - Mocking strategy (MSW, vi.mock)
+   - Test naming conventions
+
+8. Domain-Specific Patterns
+   - Authentication/authorization (session, token, OAuth)
+   - Internationalization (i18next, react-intl)
+   - File upload patterns
+   - Real-time features (WebSocket, SSE)
+   - API versioning strategy
+
+9. Anti-patterns / Inconsistencies
+   - Patterns inconsistent with other domains
+   - Performance issues (unnecessary re-renders, bundle size)
+   - Type safety issues
+   - Accessibility issues
+   - Security issues (XSS, CSRF)
+
+Do not create or modify source files. Analysis only.
+Save results to claudeos-core/generated/pass1-{{PASS_NUM}}.json in the following format:
+
+{
+  "analyzedAt": "ISO timestamp",
+  "passNum": {{PASS_NUM}},
+  "domains": ["auth", "dashboard", "settings", "shared"],
+  "analysisPerDomain": {
+    "dashboard": {
+      "representativeFiles": {
+        "page": "src/pages/dashboard/index.tsx",
+        "component": "src/components/dashboard/StatsCard.tsx",
+        "hook": "src/hooks/useDashboardData.ts",
+        "api": "src/api/dashboard.ts"
+      },
+      "patterns": {
+        "page": { ... },
+        "component": {
+          "entryFilePattern": "index.tsx or ComponentName.tsx",
+          "exportPattern": "default export or named export",
+          "stylingImport": "exact import statement used for styling utility",
+          "uiLibraryImport": "exact import statement for UI components",
+          ...
+        },
+        "dataFetching": { ... },
+        "stateManagement": { ... },
+        "config": { ... },
+        "logging": { ... },
+        "testing": { ... }
+      },
+      "specialPatterns": [],
+      "antiPatterns": []
+    }
+  },
+  "crossDomainCommon": {
+    "description": "Patterns commonly used across domains in this group",
+    "patterns": []
+  }
+}

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

@@ -1,78 +1,78 @@
-Read all pass1-*.json files from the claudeos-core/generated/ directory and
-merge all domain analysis results into a single unified report.
-
-Merge items:
-
-1. Universal Patterns (shared by 100% of all domains)
-   - Page/routing structure (React Router / TanStack Router / custom)
-   - Component writing conventions (functional, Props types, styling)
-   - Data fetching strategy (TanStack Query, SWR, axios patterns)
-   - State management approach
-   - Error/loading handling patterns
-   - Route guard/protection patterns
-
-2. Majority Patterns (shared by 50%+ of domains)
-   - Specify which domains share them
-
-3. Domain-Specific Patterns (unique to a single domain)
-   - Auth: which domain
-   - Real-time features: which domain
-   - File upload: which domain
-   - i18n: which domain
-
-4. Anti-pattern Summary
-   - Consolidate all inconsistencies found across domains
-   - Classify by severity (CRITICAL / HIGH / MEDIUM / LOW)
-
-5. Naming Conventions Summary
-   - File/directory naming (kebab-case, PascalCase)
-   - Component entry file pattern (index.tsx vs ComponentName.tsx — pick ONE that the project actually uses)
-   - Component export pattern (default export vs named export)
-   - Hook naming (use* prefix)
-   - API function patterns
-
-6. Shared Types/Components List
-   - Common UI components with EXACT import paths
-   - Shared hooks with exact import paths
-   - Utility functions with EXACT import paths
-   - Path aliases used in the project (e.g., `@/` -> `src/`)
-   - Environment variable types
-   - Constants/Enum management
-
-7. Security/Authentication Patterns
-   - Authentication approach (JWT, session, OAuth)
-   - Route protection strategy
-   - CSRF/XSS prevention
-   - Environment variable management (VITE_ convention)
-
-8. Database Patterns
-   - API endpoint conventions
-   - Request/response format
-   - Error response handling
-
-9. Testing Strategy Summary
-   - Test coverage level
-   - Test classification system (unit/component/E2E)
-   - Mocking strategy (MSW, vi.mock)
-   - Storybook usage
-   - Test naming conventions
-
-10. Logging/Monitoring Strategy
-    - Error tracking approach (Sentry, DataDog)
-    - Analytics tools
-    - Performance monitoring
-
-11. Performance Patterns
-    - Code splitting strategy (lazy, Suspense)
-    - Bundle optimization (chunk splitting, tree shaking)
-    - Image optimization
-    - Caching strategy
-
-12. Code Quality Tools
-    - Lint/Format tools (ESLint, Prettier, Biome)
-    - Pre-commit hooks (husky, lint-staged)
-    - TypeScript strict mode
-    - CI integration status
-
-Do not generate code. Merge only.
-Save results to claudeos-core/generated/pass2-merged.json.
+Read all pass1-*.json files from the claudeos-core/generated/ directory and
+merge all domain analysis results into a single unified report.
+
+Merge items:
+
+1. Universal Patterns (shared by 100% of all domains)
+   - Page/routing structure (React Router / TanStack Router / custom)
+   - Component writing conventions (functional, Props types, styling)
+   - Data fetching strategy (TanStack Query, SWR, axios patterns)
+   - State management approach
+   - Error/loading handling patterns
+   - Route guard/protection patterns
+
+2. Majority Patterns (shared by 50%+ of domains)
+   - Specify which domains share them
+
+3. Domain-Specific Patterns (unique to a single domain)
+   - Auth: which domain
+   - Real-time features: which domain
+   - File upload: which domain
+   - i18n: which domain
+
+4. Anti-pattern Summary
+   - Consolidate all inconsistencies found across domains
+   - Classify by severity (CRITICAL / HIGH / MEDIUM / LOW)
+
+5. Naming Conventions Summary
+   - File/directory naming (kebab-case, PascalCase)
+   - Component entry file pattern (index.tsx vs ComponentName.tsx — pick ONE that the project actually uses)
+   - Component export pattern (default export vs named export)
+   - Hook naming (use* prefix)
+   - API function patterns
+
+6. Shared Types/Components List
+   - Common UI components with EXACT import paths
+   - Shared hooks with exact import paths
+   - Utility functions with EXACT import paths
+   - Path aliases used in the project (e.g., `@/` -> `src/`)
+   - Environment variable types
+   - Constants/Enum management
+
+7. Security/Authentication Patterns
+   - Authentication approach (JWT, session, OAuth)
+   - Route protection strategy
+   - CSRF/XSS prevention
+   - Environment variable management (VITE_ convention)
+
+8. Database Patterns
+   - API endpoint conventions
+   - Request/response format
+   - Error response handling
+
+9. Testing Strategy Summary
+   - Test coverage level
+   - Test classification system (unit/component/E2E)
+   - Mocking strategy (MSW, vi.mock)
+   - Storybook usage
+   - Test naming conventions
+
+10. Logging/Monitoring Strategy
+    - Error tracking approach (Sentry, DataDog)
+    - Analytics tools
+    - Performance monitoring
+
+11. Performance Patterns
+    - Code splitting strategy (lazy, Suspense)
+    - Bundle optimization (chunk splitting, tree shaking)
+    - Image optimization
+    - Caching strategy
+
+12. Code Quality Tools
+    - Lint/Format tools (ESLint, Prettier, Biome)
+    - Pre-commit hooks (husky, lint-staged)
+    - TypeScript strict mode
+    - CI integration status
+
+Do not generate code. Merge only.
+Save results to claudeos-core/generated/pass2-merged.json.