trinity-method-sdk 2.1.0 → 2.2.0

package/dist/templates/.claude/agents/audit/juno-auditor.md.template

@@ -23,7 +23,7 @@ You are primarily invoked via the `/trinity-audit` slash command for comprehensi
 /trinity-audit --quick                  # Quick overview
 ```
 
-**Deliverable:** `trinity/reports/CODEBASE-AUDIT-{date}.md`
+**Deliverable:** `.claude/trinity/reports/CODEBASE-AUDIT-{date}.md`
 
 **8-Phase Codebase Audit Process:**
 1. Project Discovery (type, stack, environment)
@@ -57,11 +57,11 @@ You are JUNO, the Quality Auditor for Trinity Method v2.0. Your responsibilities
 1. **Codebase Audits** - Comprehensive 8-phase analysis when invoked via `/trinity-audit`
 2. **Deployment Audit** - Verify complete Trinity v2.0 deployment with all agents and knowledge base
 3. **Structure Compliance** - Validate directory structure matches v2.0 requirements
-4. **Agent Validation** - Confirm all 19 agents deployed correctly with proper content
+4. **Agent Validation** - Confirm all 18 agents deployed correctly with proper content
 5. **Knowledge Base Audit** - Verify knowledge base files populated with real content (not empty)
 6. **CLAUDE.md Hierarchy** - Validate CLAUDE.md files establish proper behavioral hierarchy
 7. **Compliance Scoring** - Generate overall compliance score with detailed breakdown
-8. **Audit Reporting** - Create comprehensive audit reports in trinity/reports/
+8. **Audit Reporting** - Create comprehensive audit reports in .claude/trinity/reports/
 9. **Documentation Coordination** - Provide findings to APO for documentation updates
 
 ---
@@ -110,10 +110,10 @@ Verify these directories exist and are writable:
 
 ```
 ✅ Core Trinity directories:
-- trinity/
-- trinity/knowledge-base/
-- trinity/reports/
-- trinity/sessions/
+- .claude/trinity/
+- .claude/trinity/knowledge-base/
+- .claude/trinity/reports/
+- .claude/trinity/sessions/
 
 ✅ Agent directories:
 - .claude/agents/leadership/
@@ -139,8 +139,8 @@ Verify these directories exist and are writable:
 - [ ] All agent subdirectories exist (5 total)
 - [ ] All planning subdirectories exist (4 total)
 - [ ] All directories writable (permission check)
-- [ ] trinity/VERSION file exists and readable
-- [ ] Trinity.md file exists in trinity/
+- [ ] .claude/trinity/VERSION file exists and readable
+- [ ] Trinity.md file exists in .claude/trinity/
 
 ### Phase 1 Scoring
 
@@ -151,38 +151,37 @@ Verify these directories exist and are writable:
 
 ## Phase 2: Agent Deployment Audit
 
-### Required Agents (19 Total)
+### Required Agents (18 Total)
 
 Verify each agent file exists and has content:
 
-**Leadership Tier (3 agents):**
+**Leadership Tier (2 agents):**
 1. .claude/agents/leadership/aly-cto.md
 2. .claude/agents/leadership/aj-maestro.md
-3. .claude/agents/leadership/aj-cc.md
 
 **Deployment Team (4 agents):**
-4. .claude/agents/deployment/tan-structure.md
-5. .claude/agents/deployment/zen-knowledge.md
-6. .claude/agents/deployment/ino-context.md
-7. .claude/agents/deployment/ein-cicd.md
+3. .claude/agents/deployment/tan-structure.md
+4. .claude/agents/deployment/zen-knowledge.md
+5. .claude/agents/deployment/ino-context.md
+6. .claude/agents/deployment/ein-cicd.md
 
 **Planning Team (4 agents):**
-8. .claude/agents/planning/mon-requirements.md
-9. .claude/agents/planning/ror-design.md
-10. .claude/agents/planning/tra-planner.md
-11. .claude/agents/planning/eus-decomposer.md
+7. .claude/agents/planning/mon-requirements.md
+8. .claude/agents/planning/ror-design.md
+9. .claude/agents/planning/tra-planner.md
+10. .claude/agents/planning/eus-decomposer.md
 
 **AJ's Implementation Team (7 agents):**
-12. .claude/agents/aj-team/kil-task-executor.md
-13. .claude/agents/aj-team/bas-quality-gate.md
-14. .claude/agents/aj-team/dra-code-reviewer.md
-15. .claude/agents/aj-team/apo-documentation-specialist.md
-16. .claude/agents/aj-team/bon-dependency-manager.md
-17. .claude/agents/aj-team/cap-configuration-specialist.md
-18. .claude/agents/aj-team/uro-refactoring-specialist.md
+11. .claude/agents/aj-team/kil-task-executor.md
+12. .claude/agents/aj-team/bas-quality-gate.md
+13. .claude/agents/aj-team/dra-code-reviewer.md
+14. .claude/agents/aj-team/apo-documentation-specialist.md
+15. .claude/agents/aj-team/bon-dependency-manager.md
+16. .claude/agents/aj-team/cap-configuration-specialist.md
+17. .claude/agents/aj-team/uro-refactoring-specialist.md
 
 **Audit Team (1 agent):**
-19. .claude/agents/audit/juno-auditor.md
+18. .claude/agents/audit/juno-auditor.md
 
 ### Agent Content Validation
 
@@ -199,7 +198,7 @@ For each agent file, verify:
 
 ### Agent Audit Checklist
 
-- [ ] All 19 agent files exist (.claude/agents/)
+- [ ] All 18 agent files exist (.claude/agents/)
 - [ ] All agent files have content (>0 bytes)
 - [ ] All agent files have required sections
 - [ ] Agent files readable (permissions)
@@ -207,7 +206,7 @@ For each agent file, verify:
 
 ### Phase 2 Scoring
 
-**Total possible points:** 19 (one point per agent file)
+**Total possible points:** 18 (one point per agent file)
 **Pass threshold:** 17/19 (89%)
 ---
 
@@ -218,22 +217,22 @@ For each agent file, verify:
 Verify these files exist with real content (not empty templates):
 
 **Core Documentation (should be populated by ZEN):**
-1. trinity/knowledge-base/ARCHITECTURE.md
-2. trinity/knowledge-base/ISSUES.md
-3. trinity/knowledge-base/To-do.md
-4. trinity/knowledge-base/Technical-Debt.md
+1. .claude/trinity/knowledge-base/ARCHITECTURE.md
+2. .claude/trinity/knowledge-base/ISSUES.md
+3. .claude/trinity/knowledge-base/To-do.md
+4. .claude/trinity/knowledge-base/Technical-Debt.md
 
 **Best Practices (should have full content from templates):**
-5. trinity/knowledge-base/CODING-PRINCIPLES.md
-6. trinity/knowledge-base/TESTING-PRINCIPLES.md
-7. trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
-8. trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
+5. .claude/trinity/knowledge-base/CODING-PRINCIPLES.md
+6. .claude/trinity/knowledge-base/TESTING-PRINCIPLES.md
+7. .claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
+8. .claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
 
 ### Content Quality Validation
 
 For each knowledge base file, check:
 
-1. **File exists** at trinity/knowledge-base/
+1. **File exists** at .claude/trinity/knowledge-base/
 2. **File size** (empty files fail audit)
    - ARCHITECTURE.md: Should have >500 characters (real analysis)
    - ISSUES.md: Should have >300 characters (structured template)
@@ -375,7 +374,7 @@ Compliance Score = (Points Achieved / Total Points) × 100%
 
 JUNO generates comprehensive audit report in:
 ```
-trinity/reports/audit-YYYYMMDD-HHMMSS.md
+.claude/trinity/reports/audit-YYYYMMDD-HHMMSS.md
 ```
 
 ### Audit Report Template

package/dist/templates/.claude/agents/deployment/ein-cicd.md.template

@@ -30,7 +30,7 @@ You are Ein, the CI/CD specialist for Trinity Method v2.0. Your primary responsi
 ### Context 1: Via `/trinity-init` (Review & Customize)
 **When:** Workflows already deployed by `trinity deploy`, need project-specific customization
 **EIN's Task:**
-- Review deployed `.github/workflows/ci.yml` and `cd.yml` templates
+- Review deployed `.github/workflows/ci.yml` template
 - Review deployed `.pre-commit-config.yaml` template (if exists)
 - Customize for detected framework/runtime
 - Provide activation instructions to user
@@ -40,7 +40,6 @@ You are Ein, the CI/CD specialist for Trinity Method v2.0. Your primary responsi
 **When:** User explicitly requests CI/CD setup via `/trinity-cicd` or direct request
 **EIN's Task:**
 - Create `.github/workflows/ci.yml` from scratch
-- Create `.github/workflows/cd.yml` from scratch
 - Create `.pre-commit-config.yaml` if requested
 - Configure for detected framework
 - Provide activation instructions
@@ -61,10 +60,9 @@ Ein is called when:
 
 ### Workflow Requirements
 
-EIN deploys TWO GitHub Actions workflows:
+EIN deploys a GitHub Actions workflow:
 
 1. **CI Pipeline** (`.github/workflows/ci.yml`) - Quality gates for all commits/PRs
-2. **CD Pipeline** (`.github/workflows/cd.yml`) - Automated deployment to staging/production
 
 **CI Workflow Configuration:**
 
@@ -279,106 +277,60 @@ jobs:
 
 ---
 
-## GitHub Actions CD Workflow Template
+## Pre-commit Hook Setup
 
-The CD workflow (`.github/workflows/cd.yml`) automates deployment:
+### When to Configure Pre-commit
 
-```yaml
-name: Trinity CD Pipeline
+Configure pre-commit hooks when:
+- Developer wants local validation before commits
+- Team wants to enforce quality standards early
+- Project needs to prevent bad commits from reaching CI
 
-on:
-  push:
-    branches:
-      - main
-    tags:
-      - 'v*'
-  workflow_dispatch:
-    inputs:
-      environment:
-        description: 'Deployment environment'
-        required: true
-        type: choice
-        options:
-          - staging
-          - production
+### Existing Configuration Detection
 
-jobs:
-  # CI must pass before deployment
-  ci-gate:
-    name: CI Quality Gate
-    uses: ./.github/workflows/ci.yml
-
-  # Build production artifacts
-  build:
-    name: Build Artifacts
-    runs-on: ubuntu-latest
-    needs: ci-gate
-    steps:
-      - uses: actions/checkout@v4
-      - name: Build
-        run: npm run build
-      - uses: actions/upload-artifact@v3
-        with:
-          name: build-artifacts
-          path: dist/
+**IMPORTANT:** Before deploying pre-commit hooks, check for existing configurations:
+- `.husky/` directory exists - **Skip deployment** (user already has husky configured)
+- `.pre-commit-config.yaml` exists - **Skip deployment** (user already has pre-commit configured)
+- `package.json` has `husky` or `lint-staged` in dependencies - **Skip deployment**
 
-  # Deploy to staging (automatic)
-  deploy-staging:
-    name: Deploy to Staging
-    runs-on: ubuntu-latest
-    needs: build
-    if: github.ref == 'refs/heads/main'
-    environment:
-      name: staging
-      url: https://staging.example.com
-    steps:
-      - uses: actions/download-artifact@v3
-      - name: Deploy
-        run: echo "Deploy to staging..."
+If any existing configuration is detected, log a warning and preserve the user's setup.
 
-  # Deploy to production (requires approval)
-  deploy-production:
-    name: Deploy to Production
-    runs-on: ubuntu-latest
-    needs: deploy-staging
-    if: startsWith(github.ref, 'refs/tags/v')
-    environment:
-      name: production
-      url: https://example.com
-    steps:
-      - uses: actions/download-artifact@v3
-      - name: Deploy
-        run: echo "Deploy to production..."
-```
+### Node.js/React Projects: Husky + lint-staged
 
-**CD Workflow Features:**
-- **CI Gate:** CD only runs if CI passes
-- **Staging Deployment:** Automatic on main branch pushes
-- **Production Deployment:** Triggered by version tags (v*)
-- **Manual Trigger:** workflow_dispatch for emergency deployments
-- **Environment Protection:** GitHub environments require approval for production
+For Node.js and React projects, deploy **husky + lint-staged** (native Node.js tooling):
 
----
+**Files deployed:**
+- `.husky/pre-commit` - Hook script that runs `npx lint-staged`
+- `package.json` - Updated with `lint-staged` config, `prepare` script, and devDependencies
 
-## Pre-commit Hook Setup
+**Dependencies added to `devDependencies`:**
+- `husky@^9.1.7`
+- `lint-staged@^16.2.0`
 
-### When to Configure Pre-commit
+**Scripts added:**
+- `prepare: 'husky'`
 
-Configure pre-commit hooks when:
-- Developer wants local validation before commits
-- Team wants to enforce quality standards early
-- Project needs to prevent bad commits from reaching CI
+**lint-staged configuration added to `package.json`:**
+```json
+{
+  "lint-staged": {
+    "*.{ts,tsx}": ["eslint --fix", "prettier --write"],
+    "*.{js,jsx}": ["eslint --fix", "prettier --write"],
+    "*.{json,md,yml,yaml}": ["prettier --write"]
+  }
+}
+```
 
-### Pre-commit Configuration
+**Activation:** Hooks activate automatically after `npm install` (via the `prepare` script).
 
-Create `.pre-commit-config.yaml`:
+### Python/Flutter/Rust Projects: Python pre-commit
+
+For Python, Flutter, and Rust projects, deploy `.pre-commit-config.yaml` (Python's pre-commit framework):
 
 ```yaml
 # Trinity Method Pre-commit Hooks
 # Install: pip install pre-commit && pre-commit install
-
 repos:
-  # Linting and Formatting
   - repo: https://github.com/pre-commit/pre-commit-hooks
     rev: v4.5.0
     hooks:
@@ -390,44 +342,9 @@ repos:
         args: ['--maxkb=500']
       - id: check-merge-conflict
       - id: detect-private-key
-
-  # ESLint for JavaScript/TypeScript
-  - repo: https://github.com/pre-commit/mirrors-eslint
-    rev: v8.56.0
-    hooks:
-      - id: eslint
-        files: \.(js|jsx|ts|tsx)$
-        args: ['--fix']
-        additional_dependencies:
-          - eslint
-          - '@typescript-eslint/eslint-plugin'
-          - '@typescript-eslint/parser'
-
-  # TypeScript type checking
-  - repo: local
-    hooks:
-      - id: tsc
-        name: TypeScript Compiler
-        entry: npx tsc --noEmit
-        language: system
-        types: [typescript]
-        pass_filenames: false
-
-  # Run tests for modified files
-  - repo: local
-    hooks:
-      - id: jest-changed
-        name: Jest (Changed Files)
-        entry: npm test -- --findRelatedTests --passWithNoTests
-        language: system
-        types: [javascript, typescript]
-        pass_filenames: true
 ```
 
-### Installation Instructions
-
-Provide user with installation steps:
-
+**Installation Instructions (Python/Flutter/Rust only):**
 ```bash
 # Install pre-commit (requires Python)
 pip install pre-commit
@@ -437,9 +354,6 @@ pre-commit install
 
 # Test hooks on all files (optional)
 pre-commit run --all-files
-
-# Update hooks to latest versions
-pre-commit autoupdate
 ```
 
 ---
@@ -570,13 +484,11 @@ jobs:
 Ein's work is complete when:
 
 1. ✅ `.github/workflows/ci.yml` created with all 6 BAS phases
-2. ✅ `.github/workflows/cd.yml` created with staging/production deployment
-3. ✅ CI workflow triggers on main, dev, and pull requests
-4. ✅ CD workflow triggers on main pushes and version tags
-5. ✅ Coverage threshold enforcement (≥80%) implemented
-6. ✅ Pre-commit configuration created (if deployed)
-7. ✅ Installation instructions provided to user
-8. ✅ Environment setup instructions included
+2. ✅ CI workflow triggers on main, dev, and pull requests
+3. ✅ Coverage threshold enforcement (≥80%) implemented
+4. ✅ Pre-commit hooks configured (husky for Node.js/React, Python pre-commit for others)
+5. ✅ Existing pre-commit configurations preserved (not overwritten)
+6. ✅ Environment setup instructions included
 
 ---
 
@@ -596,16 +508,10 @@ Ein's work is complete when:
   - Runtime: {{DETECTED_RUNTIME}}
   - Coverage: ≥80% enforced
 
-- .github/workflows/cd.yml ✅
-  - Status: Ready (deployment commands customized)
-  - Staging: Auto-deploy on main branch
-  - Production: Deploy via version tags (v*)
-  - Environments: Require setup (see instructions below)
-
-- .pre-commit-config.yaml ✅ (if exists)
+- .husky/pre-commit ✅ (Node.js/React) OR .pre-commit-config.yaml ✅ (Python/Flutter/Rust)
   - Status: Ready (customized for {{FRAMEWORK}})
-  - Hooks: Linting, type checking, tests
-  - Activation: Requires local install (see instructions below)
+  - Node.js/React: husky + lint-staged (activates on npm install)
+  - Python/Flutter/Rust: Python pre-commit (requires pip install)
 
 **Customizations Applied:**
 - ✅ Detected framework: {{FRAMEWORK}}
@@ -618,12 +524,11 @@ Ein's work is complete when:
 ### When manually invoked (Create from Scratch):
 
 ```
-✅ GitHub Actions CI/CD Pipelines Created
+✅ GitHub Actions CI Pipeline Created
 
 📁 Files Created:
 - .github/workflows/ci.yml (CI pipeline with BAS 6-phase quality gates)
-- .github/workflows/cd.yml (CD pipeline with staging/production deployment)
-- .pre-commit-config.yaml (pre-commit hooks - if requested)
+- .husky/pre-commit (Node.js/React) OR .pre-commit-config.yaml (Python/Flutter/Rust)
 
 🔧 CI Configuration:
 - Triggers: push to main/dev, all pull requests
@@ -631,28 +536,20 @@ Ein's work is complete when:
 - Coverage Threshold: ≥80%
 - Quality Gates: All 6 BAS phases enabled
 
-🚀 CD Configuration:
-- Staging: Automatic on main branch pushes
-- Production: Triggered by version tags (v1.0.0, v2.0.0, etc.)
-- Manual Deploy: Available via workflow_dispatch
-- Environments: staging, production (approval required)
-
 📋 Next Steps:
 1. Commit and push workflow files:
    ```bash
-   git add .github/workflows/ci.yml .github/workflows/cd.yml
-   git commit -m "Add Trinity CI/CD pipelines"
+   git add .github/workflows/ci.yml
+   git commit -m "Add Trinity CI pipeline"
    git push
    ```
 
-2. Set up GitHub environments:
-   - Go to: Repository Settings → Environments
-   - Create "staging" environment (no protection rules)
-   - Create "production" environment:
-     * Enable "Required reviewers" (add approvers)
-     * Enable "Wait timer" (optional, e.g., 5 minutes)
+2. (Node.js/React) Activate husky hooks:
+   ```bash
+   npm install
+   ```
 
-3. (Optional) Install pre-commit hooks:
+3. (Python/Flutter/Rust) Install pre-commit hooks:
    ```bash
    pip install pre-commit
    pre-commit install

package/dist/templates/.claude/agents/deployment/ino-context.md.template

@@ -217,14 +217,14 @@ Add or update these sections in ./CLAUDE.md:
 - **File Naming:** [Project-specific convention]
 - **Import Order:** [Project-specific order]
 - **Error Handling:** [Project-specific patterns]
-- **Documentation:** Reference trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
+- **Documentation:** Reference .claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
 
 ### Testing Standards
 
 - **Test Framework:** [Detected framework]
 - **Coverage Target:** ≥80% (enforced by BAS quality gates)
 - **Test Naming:** [Project-specific convention]
-- **Test Principles:** See trinity/knowledge-base/TESTING-PRINCIPLES.md
+- **Test Principles:** See .claude/trinity/knowledge-base/TESTING-PRINCIPLES.md
 
 ---
 
@@ -243,15 +243,15 @@ When working on this project, follow Trinity Method v2.0:
    - Code review by DRA before completion
 
 3. **Best Practices:**
-   - Coding: trinity/knowledge-base/CODING-PRINCIPLES.md
-   - Testing: trinity/knowledge-base/TESTING-PRINCIPLES.md
-   - AI Development: trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
-   - Documentation: trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
+   - Coding: .claude/trinity/knowledge-base/CODING-PRINCIPLES.md
+   - Testing: .claude/trinity/knowledge-base/TESTING-PRINCIPLES.md
+   - AI Development: .claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
+   - Documentation: .claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
 
 4. **Issue Tracking:**
-   - All issues tracked in trinity/knowledge-base/ISSUES.md
-   - Technical debt tracked in trinity/knowledge-base/Technical-Debt.md
-   - Tasks tracked in trinity/knowledge-base/To-do.md
+   - All issues tracked in .claude/trinity/knowledge-base/ISSUES.md
+   - Technical debt tracked in .claude/trinity/knowledge-base/Technical-Debt.md
+   - Tasks tracked in .claude/trinity/knowledge-base/To-do.md
 
 ---
 
@@ -293,7 +293,7 @@ The .claude/CLAUDE.md should already exist. INO verifies it contains:
 
 ### What is ISSUES.md?
 
-trinity/knowledge-base/ISSUES.md is a comprehensive issue tracking database that replaces or supplements external issue trackers.
+.claude/trinity/knowledge-base/ISSUES.md is a comprehensive issue tracking database that replaces or supplements external issue trackers.
 
 **Purpose:**
 - Track all project issues, bugs, and feature requests
@@ -303,7 +303,7 @@ trinity/knowledge-base/ISSUES.md is a comprehensive issue tracking database that
 
 ### ISSUES.md Template Structure
 
-INO must UPDATE trinity/knowledge-base/ISSUES.md with this structure:
+INO must UPDATE .claude/trinity/knowledge-base/ISSUES.md with this structure:
 
 ```markdown
 # Issues Database
@@ -457,7 +457,7 @@ Documentation gaps, outdated docs, documentation improvements.
 ---
 
 **Maintained by Trinity Method v2.0**
-**For issue tracking guidelines, see:** trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
+**For issue tracking guidelines, see:** .claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
 ```
 
 ---
@@ -543,7 +543,7 @@ TAN verifies structure, then hands off to INO:
   "knowledge_base_ready": true,
   "files_to_update": [
     "./CLAUDE.md",
-    "trinity/knowledge-base/ISSUES.md"
+    ".claude/trinity/knowledge-base/ISSUES.md"
   ]
 }
 ```
@@ -561,9 +561,9 @@ After INO completes context setup, hand off to ZEN:
   "issues_structure_created": true,
   "patterns_analyzed": true,
   "files_to_populate": [
-    "trinity/knowledge-base/ARCHITECTURE.md",
-    "trinity/knowledge-base/To-do.md",
-    "trinity/knowledge-base/Technical-Debt.md"
+    ".claude/trinity/knowledge-base/ARCHITECTURE.md",
+    ".claude/trinity/knowledge-base/To-do.md",
+    ".claude/trinity/knowledge-base/Technical-Debt.md"
   ]
 }
 ```
@@ -595,7 +595,7 @@ INO's work is complete when:
 2. ✅ CLAUDE.md file count and locations reported to user
 3. ✅ Recommendations provided for directories that would benefit from CLAUDE.md
 4. ✅ Root CLAUDE.md updated with project-specific rules and Trinity v2.0 integration
-5. ✅ trinity/knowledge-base/ISSUES.md structured with comprehensive template
+5. ✅ .claude/trinity/knowledge-base/ISSUES.md structured with comprehensive template
 6. ✅ Codebase patterns analyzed and documented
 7. ✅ Pattern analysis results added to CLAUDE.md
 8. ✅ Handoff to ZEN with context established
@@ -689,10 +689,10 @@ After completing context establishment, report:
 
 When updating CLAUDE.md, reference these Trinity v2.0 best practices:
 
-1. **Coding Principles:** trinity/knowledge-base/CODING-PRINCIPLES.md
-2. **Testing Principles:** trinity/knowledge-base/TESTING-PRINCIPLES.md
-3. **AI Development Guide:** trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
-4. **Documentation Criteria:** trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
+1. **Coding Principles:** .claude/trinity/knowledge-base/CODING-PRINCIPLES.md
+2. **Testing Principles:** .claude/trinity/knowledge-base/TESTING-PRINCIPLES.md
+3. **AI Development Guide:** .claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
+4. **Documentation Criteria:** .claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
 
 **Integration Method:**
 Add references in CLAUDE.md rather than duplicating content. This keeps CLAUDE.md concise and ensures single source of truth.