trinity-method-sdk 2.1.0 → 2.2.1

package/dist/templates/.claude/commands/session/trinity-continue.md.template

@@ -13,16 +13,16 @@ Resume Trinity Method workflow after interruption.
 **Context:** User experienced a crash or is returning to an existing session with incomplete work.
 
 **When to use:**
-- Work orders in trinity/work-orders/ haven't been completed
-- Reports in trinity/reports/ haven't been analyzed
-- Session files in trinity/sessions/ need review
+- Work orders in .claude/trinity/work-orders/ haven't been completed
+- Reports in .claude/trinity/reports/ haven't been analyzed
+- Session files in .claude/trinity/sessions/ need review
 - User needs to pick up where they left off
 
 **Process:**
 1. **ALY (CTO)** reviews all current work:
-   - Check trinity/sessions/ for active session files
-   - Review trinity/work-orders/ for incomplete work orders
-   - Analyze trinity/reports/ for unprocessed reports
+   - Check .claude/trinity/sessions/ for active session files
+   - Review .claude/trinity/work-orders/ for incomplete work orders
+   - Analyze .claude/trinity/reports/ for unprocessed reports
 
 2. **ALY provides session summary:**
    - Last known state of work
@@ -52,7 +52,7 @@ git log --oneline -5
 
 2. **Work Order Checking**:
 ```bash
-cat trinity/work-orders/WO-042-jwt-refresh-implementation.md
+cat .claude/trinity/work-orders/WO-042-jwt-refresh-implementation.md
 # Status: IN PROGRESS
 # **Last Updated**: 2 hours ago
 # Progress: Task 3/7
@@ -60,14 +60,14 @@ cat trinity/work-orders/WO-042-jwt-refresh-implementation.md
 
 3. **Session File Reading**:
 ```bash
-cat trinity/sessions/SESSION-2025-12-18-14-30.md
+cat .claude/trinity/sessions/SESSION-2025-12-18-14-30.md
 # Last entry: "Implementing middleware integration (50% complete)"
 # Interrupted: Context window limit reached
 ```
 
 4. **Knowledge Base Review**:
 ```bash
-cat trinity/knowledge-base/To-do.md
+cat .claude/trinity/knowledge-base/To-do.md
 # Shows 4 remaining tasks for JWT implementation
 ```
 
@@ -209,7 +209,7 @@ The previous session (3 days ago) was completed successfully:
 - Or create new work order with `/trinity-workorder`
 
 **Option 2: Review Backlog**
-- Check trinity/work-orders/ for pending work orders
+- Check .claude/trinity/work-orders/ for pending work orders
 - Prioritize and select next task
 - Begin implementation
 
@@ -406,13 +406,13 @@ git diff HEAD
 ### 2. Work Order Checking
 ```bash
 # List all work orders
-ls -lt trinity/work-orders/
+ls -lt .claude/trinity/work-orders/
 
 # Find IN PROGRESS work orders
-grep -r "Status: IN PROGRESS" trinity/work-orders/
+grep -r "Status: IN PROGRESS" .claude/trinity/work-orders/
 
 # Read most recent work order
-cat trinity/work-orders/WO-042-*.md
+cat .claude/trinity/work-orders/WO-042-*.md
 ```
 
 **Information Gathered**:
@@ -424,10 +424,10 @@ cat trinity/work-orders/WO-042-*.md
 ### 3. Session File Reading
 ```bash
 # Find most recent session file
-ls -lt trinity/sessions/ | head -1
+ls -lt .claude/trinity/sessions/ | head -1
 
 # Read session log
-cat trinity/sessions/SESSION-2025-12-18-14-30.md
+cat .claude/trinity/sessions/SESSION-2025-12-18-14-30.md
 ```
 
 **Information Gathered**:
@@ -439,13 +439,13 @@ cat trinity/sessions/SESSION-2025-12-18-14-30.md
 ### 4. Knowledge Base Review
 ```bash
 # Check active tasks
-cat trinity/knowledge-base/To-do.md
+cat .claude/trinity/knowledge-base/To-do.md
 
 # Review known issues
-cat trinity/knowledge-base/ISSUES.md
+cat .claude/trinity/knowledge-base/ISSUES.md
 
 # Check recent decisions
-tail -20 trinity/knowledge-base/ARCHITECTURE.md
+tail -20 .claude/trinity/knowledge-base/ARCHITECTURE.md
 ```
 
 **Information Gathered**:
@@ -495,7 +495,7 @@ git log origin/main..HEAD --oneline
 - Terminal history
 - In-memory variables
 
-**Persisted In**: `trinity/sessions/SESSION-{timestamp}.md`
+**Persisted In**: `.claude/trinity/sessions/SESSION-{timestamp}.md`
 
 ### Work Order State
 **What**: Progress on specific task
@@ -503,7 +503,7 @@ git log origin/main..HEAD --oneline
 - Current phase
 - Blockers/issues
 
-**Persisted In**: `trinity/work-orders/WO-XXX-{title}.md`
+**Persisted In**: `.claude/trinity/work-orders/WO-XXX-{title}.md`
 
 ### Key Difference
 
@@ -542,12 +542,12 @@ git log origin/main..HEAD --oneline
 **/trinity-continue**:
 - Analyzes current state (git, work orders, sessions)
 - Provides recovery options
-- Resumes with AJ MAESTRO or AJ CC
+- Resumes with AJ MAESTRO
 
 **/trinity-end**:
 - Creates session summary
 - Updates knowledge base
-- Archives work to trinity/archive/
+- Archives work to .claude/trinity/archive/
 - Clears session state
 
 **Don't Use /trinity-end** if you're just taking a break - context will be lost!

package/dist/templates/.claude/commands/session/trinity-end.md.template

@@ -1,7 +1,7 @@
 # Trinity End
 
 **Command:** `/session:trinity-end`
-**Purpose:** End session and archive work to trinity/archive/
+**Purpose:** End session and archive work to .claude/trinity/archive/
 **Architecture:** ALY session summary → Work archival → Documentation update
 **Trinity Version:** 2.1.0
 **Last Updated:** 2026-01-21
@@ -18,17 +18,17 @@ End current Trinity Method session and prepare for commit.
    **STRICT ARCHIVING PROTOCOL:**
 
    a. **Archive Completed Work Orders:**
-      - Read all files from `trinity/sessions/` matching `WO-*.md`
-      - Move each to `trinity/archive/work-orders/YYYY-MM-DD/`
+      - Read all files from `.claude/trinity/sessions/` matching `WO-*.md`
+      - Move each to `.claude/trinity/archive/work-orders/YYYY-MM-DD/`
       - These were moved to sessions/ after completion per work order template
 
    b. **Archive Completed Investigations:**
-      - Read all files from `trinity/sessions/` matching `INV-*.md`
-      - Move each to `trinity/archive/investigations/YYYY-MM-DD/`
+      - Read all files from `.claude/trinity/sessions/` matching `INV-*.md`
+      - Move each to `.claude/trinity/archive/investigations/YYYY-MM-DD/`
       - These were moved to sessions/ after completion per investigation template
 
    c. **Archive ALL Reports:**
-      - Move ALL files from `trinity/reports/` to `trinity/archive/reports/YYYY-MM-DD/`
+      - Move ALL files from `.claude/trinity/reports/` to `.claude/trinity/archive/reports/YYYY-MM-DD/`
       - This includes:
         - Implementation completion reports
         - Investigation findings reports
@@ -37,18 +37,18 @@ End current Trinity Method session and prepare for commit.
       - **NO EXCEPTIONS:** Every file in reports/ must be archived
 
    d. **Archive Session Files:**
-      - Move ALL remaining files from `trinity/sessions/` to `trinity/archive/sessions/YYYY-MM-DD/`
-      - Create session summary document in `trinity/archive/sessions/YYYY-MM-DD/SESSION-SUMMARY-{date}.md`
+      - Move ALL remaining files from `.claude/trinity/sessions/` to `.claude/trinity/archive/sessions/YYYY-MM-DD/`
+      - Create session summary document in `.claude/trinity/archive/sessions/YYYY-MM-DD/SESSION-SUMMARY-{date}.md`
 
    e. **Verify Clean Slate:**
-      - **CRITICAL:** After archiving, `trinity/sessions/` MUST be empty
-      - **CRITICAL:** After archiving, `trinity/reports/` MUST be empty
+      - **CRITICAL:** After archiving, `.claude/trinity/sessions/` MUST be empty
+      - **CRITICAL:** After archiving, `.claude/trinity/reports/` MUST be empty
       - If any files remain, archive them or report error
       - Next session MUST start with completely empty sessions/ and reports/ folders
 
    **Archive Structure:**
    ```
-   trinity/archive/
+   .claude/trinity/archive/
    ├── work-orders/YYYY-MM-DD/
    │   ├── WO-001-*.md
    │   ├── WO-002-*.md
@@ -68,25 +68,25 @@ End current Trinity Method session and prepare for commit.
    ```
 
    **Important Notes:**
-   - Keep ONLY active/in-progress work orders in `trinity/work-orders/`
-   - Keep ONLY active/in-progress investigations in `trinity/investigations/`
+   - Keep ONLY active/in-progress work orders in `.claude/trinity/work-orders/`
+   - Keep ONLY active/in-progress investigations in `.claude/trinity/investigations/`
    - Do NOT archive incomplete work
-   - Completed work is identified by presence in `trinity/sessions/` folder
+   - Completed work is identified by presence in `.claude/trinity/sessions/` folder
    - All reports are archived regardless of status
 
 2. **ALY analyzes session events:**
    - Review all work completed during session
    - Identify patterns and learnings
-   - Update trinity/knowledge-base/ARCHITECTURE.md with architectural changes
-   - Update trinity/knowledge-base/ISSUES.md with new known issues
-   - Update trinity/knowledge-base/To-do.md with next tasks
-   - Update trinity/knowledge-base/Technical-Debt.md with new debt
+   - Update .claude/trinity/knowledge-base/ARCHITECTURE.md with architectural changes
+   - Update .claude/trinity/knowledge-base/ISSUES.md with new known issues
+   - Update .claude/trinity/knowledge-base/To-do.md with next tasks
+   - Update .claude/trinity/knowledge-base/Technical-Debt.md with new debt
 
 3. **Clean workspace:**
-   - Verify trinity/work-orders/ contains only active work
-   - Verify trinity/investigations/ contains only active investigations
-   - Verify trinity/reports/ is empty
-   - Verify trinity/sessions/ is empty
+   - Verify .claude/trinity/work-orders/ contains only active work
+   - Verify .claude/trinity/investigations/ contains only active investigations
+   - Verify .claude/trinity/reports/ is empty
+   - Verify .claude/trinity/sessions/ is empty
    - Ready for next session
 
 4. **Git commit instructions:**

package/dist/templates/.claude/commands/session/trinity-start.md.template

@@ -65,7 +65,7 @@ For complex or long-running tasks, suggest creating a work order:
 /trinity-workorder
 ```
 
-This creates a structured investigation in `trinity/work-orders/` with:
+This creates a structured investigation in `.claude/trinity/work-orders/` with:
 - Problem statement
 - Requirements and acceptance criteria
 - Design decisions
@@ -77,7 +77,6 @@ This creates a structured investigation in `trinity/work-orders/` with:
 **Leadership:**
 - ALY (CTO) - Strategic planning, architecture decisions
 - AJ MAESTRO - Workflow orchestration and planning
-- AJ CC - Code quality oversight
 
 **Deployment:**
 - TAN - Trinity structure deployment

package/dist/templates/.claude/commands/utility/trinity-agents.md.template

@@ -16,11 +16,10 @@ Display the Trinity Method Agent Directory with all 19 specialized agents.
 
 Agents are organized in 5 subdirectories by role:
 
-### 1. Leadership Team (3 agents)
+### 1. Leadership Team (2 agents)
 Located in: `.claude/agents/leadership/`
 - **ALY (Chief Technology Officer)** - Strategic planning and architecture decisions
 - **AJ MAESTRO (Orchestration Lead)** - Workflow planning and agent coordination
-- **AJ CC (Code Coordinator)** - Code quality and implementation oversight
 
 ### 2. Deployment Team (4 agents)
 Located in: `.claude/agents/deployment/`
@@ -105,7 +104,6 @@ Ask which agent you want to learn more about, and Claude will read that agent's
 |-------|------|-------------|---------------|
 | **ALY** | CTO | Strategic decisions, stop point reviews | leadership/aly-cto.md |
 | **AJ MAESTRO** | Orchestrator | Coordinate Medium/Large workflows | leadership/aj-maestro.md |
-| **AJ CC** | Continuity | Session recovery, investigations | leadership/aj-cc.md |
 | **TAN** | Structure | Deploy Trinity folders (init only) | deployment/tan-structure.md |
 | **ZEN** | Knowledge | Populate knowledge base (init only) | deployment/zen-knowledge.md |
 | **INO** | Context | CLAUDE.md hierarchy (init only) | deployment/ino-context.md |
@@ -134,9 +132,9 @@ What do you need?
 │
 ├─ Start new work → ALY (determines scale) → AJ MAESTRO
 │
-├─ Resume interrupted work → AJ CC (session recovery)
+├─ Resume interrupted work → AJ MAESTRO (session recovery)
 │
-├─ Investigation only → AJ CC (read-only analysis)
+├─ Investigation only → ALY (read-only analysis)
 │
 └─ Specific task:
     │
@@ -165,7 +163,6 @@ What do you need?
 **Examples**:
 - **ALY** - Chief Technology Officer (CTO)
 - **AJ MAESTRO** - Implementation Orchestrator
-- **AJ CC** - Continuous Context Specialist
 - **MON** - Requirements Analyst
 - **KIL** - Task Executor
 

package/dist/templates/.claude/commands/utility/trinity-verify.md.template

@@ -12,27 +12,26 @@ Verify that Trinity Method is properly installed in this project.
 
 Check for:
 1. **Trinity Core Structure (14 directories):**
-   - trinity/knowledge-base/
-   - trinity/reports/
-   - trinity/sessions/
-   - trinity/investigations/
-   - trinity/investigations/plans/
-   - trinity/patterns/
-   - trinity/work-orders/
-   - trinity/templates/
-   - trinity/templates/work-orders/
-   - trinity/templates/investigations/
-   - trinity/archive/work-orders/
-   - trinity/archive/investigations/
-   - trinity/archive/reports/
-   - trinity/archive/sessions/
+   - .claude/trinity/knowledge-base/
+   - .claude/trinity/reports/
+   - .claude/trinity/sessions/
+   - .claude/trinity/investigations/
+   - .claude/trinity/investigations/plans/
+   - .claude/trinity/work-orders/
+   - .claude/trinity/templates/
+   - .claude/trinity/templates/work-orders/
+   - .claude/trinity/templates/investigations/
+   - .claude/trinity/archive/work-orders/
+   - .claude/trinity/archive/investigations/
+   - .claude/trinity/archive/reports/
+   - .claude/trinity/archive/sessions/
 
 2. **CLAUDE.md Context Files:**
    - Root CLAUDE.md (behavioral hierarchy)
-   - trinity/CLAUDE.md (Trinity-specific context)
+   - .claude/trinity/CLAUDE.md (Trinity-specific context)
 
-3. **Agent Organization (19 agents in 5 subdirectories):**
-   - .claude/agents/leadership/ (3 agents: ALY, AJ MAESTRO, AJ CC)
+3. **Agent Organization (18 agents in 5 subdirectories):**
+   - .claude/agents/leadership/ (2 agents: ALY, AJ MAESTRO)
    - .claude/agents/deployment/ (4 agents: TAN, ZEN, INO, EIN)
    - .claude/agents/audit/ (1 agent: JUNO)
    - .claude/agents/planning/ (4 agents: MON, ROR, TRA, EUS)
@@ -48,9 +47,9 @@ Check for:
    - Utility: verify, agents, workorder
 
 5. **Templates (13 total):**
-   - Work Orders: 6 templates in trinity/templates/work-orders/
-   - Investigations: 5 templates in trinity/templates/investigations/
-   - Documentation: 2 templates in trinity/templates/documentation/
+   - Work Orders: 6 templates in .claude/trinity/templates/work-orders/
+   - Investigations: 5 templates in .claude/trinity/templates/investigations/
+   - Documentation: 2 templates in .claude/trinity/templates/documentation/
 
 6. **Knowledge Base Files (9 files):**
    - ARCHITECTURE.md, Trinity.md, To-do.md, ISSUES.md, Technical-Debt.md
@@ -59,7 +58,6 @@ Check for:
 
 7. **CI/CD Workflows (if deployed):**
    - .github/workflows/ci.yml (BAS 6-phase quality gates)
-   - .github/workflows/cd.yml (Deployment pipeline)
 
 Report:
 - ✅ Installed components
@@ -86,17 +84,16 @@ Report:
 - ✅ .claude/
 - ✅ .claude/agents/ (5 subdirectories)
 - ✅ .claude/commands/
-- ✅ trinity/knowledge-base/
-- ✅ trinity/work-orders/
-- ✅ trinity/sessions/
-- ✅ trinity/planning/
-- ✅ trinity/reports/
-
-### 2. Agent Deployment ✅ (19/19)
-**Leadership** (3/3):
+- ✅ .claude/trinity/knowledge-base/
+- ✅ .claude/trinity/work-orders/
+- ✅ .claude/trinity/sessions/
+- ✅ .claude/trinity/planning/
+- ✅ .claude/trinity/reports/
+
+### 2. Agent Deployment ✅ (18/18)
+**Leadership** (2/2):
 - ✅ aly-cto.md (2.4 KB)
 - ✅ aj-maestro.md (18.2 KB)
-- ✅ aj-cc.md (12.1 KB)
 
 **Deployment** (4/4):
 - ✅ tan-structure.md (8.5 KB)
@@ -152,7 +149,6 @@ Report:
 
 ### 5. CI/CD Workflows ✅ (Optional)
 - ✅ .github/workflows/ci.yml (BAS 6-phase gates)
-- ✅ .github/workflows/cd.yml (Deployment pipeline)
 
 ## Summary
 **Status**: ✅ FULLY DEPLOYED
@@ -177,17 +173,16 @@ Report:
 - ✅ .claude/
 - ✅ .claude/agents/ (5 subdirectories)
 - ✅ .claude/commands/
-- ✅ trinity/knowledge-base/
-- ❌ trinity/work-orders/ (MISSING)
-- ✅ trinity/sessions/
-- ✅ trinity/planning/
-- ❌ trinity/reports/ (MISSING)
-
-### 2. Agent Deployment ⚠️ (17/19)
-**Leadership** (3/3):
+- ✅ .claude/trinity/knowledge-base/
+- ❌ .claude/trinity/work-orders/ (MISSING)
+- ✅ .claude/trinity/sessions/
+- ✅ .claude/trinity/planning/
+- ❌ .claude/trinity/reports/ (MISSING)
+
+### 2. Agent Deployment ⚠️ (16/18)
+**Leadership** (2/2):
 - ✅ aly-cto.md
 - ✅ aj-maestro.md
-- ✅ aj-cc.md
 
 **Deployment** (2/4):
 - ✅ tan-structure.md
@@ -250,8 +245,8 @@ Report:
 
 **Symptom**:
 ```
-❌ trinity/work-orders/ not found
-❌ trinity/reports/ not found
+❌ .claude/trinity/work-orders/ not found
+❌ .claude/trinity/reports/ not found
 ```
 
 **Cause**: Incomplete `trinity deploy` or TAN agent failure
@@ -259,19 +254,19 @@ Report:
 **Fix**:
 ```bash
 # Manually create missing directories
-mkdir -p trinity/work-orders
-mkdir -p trinity/reports
-mkdir -p trinity/sessions
-mkdir -p trinity/planning
+mkdir -p .claude/trinity/work-orders
+mkdir -p .claude/trinity/reports
+mkdir -p .claude/trinity/sessions
+mkdir -p .claude/trinity/planning
 
 # Verify creation
-ls -la trinity/
+ls -la .claude/trinity/
 ```
 
 **Verification**:
 ```bash
 # Should show all directories
-trinity/
+.claude/trinity/
 ├── work-orders/
 ├── reports/
 ├── sessions/
@@ -331,20 +326,20 @@ find .claude/agents -name "*.md" -type f
 
 # OR manually populate files
 # ISSUES.md should contain:
-echo "# Known Issues\n\nNo issues currently tracked." > trinity/knowledge-base/ISSUES.md
+echo "# Known Issues\n\nNo issues currently tracked." > .claude/trinity/knowledge-base/ISSUES.md
 
 # To-do.md should contain:
-echo "# Project To-Do List\n\nNo tasks currently tracked." > trinity/knowledge-base/To-do.md
+echo "# Project To-Do List\n\nNo tasks currently tracked." > .claude/trinity/knowledge-base/To-do.md
 ```
 
 **Verification**:
 ```bash
 # Check file sizes (should be >0 bytes)
-ls -lh trinity/knowledge-base/*.md
+ls -lh .claude/trinity/knowledge-base/*.md
 
 # Verify content
-cat trinity/knowledge-base/ISSUES.md
-cat trinity/knowledge-base/To-do.md
+cat .claude/trinity/knowledge-base/ISSUES.md
+cat .claude/trinity/knowledge-base/To-do.md
 ```
 
 ---
@@ -452,7 +447,6 @@ ls -la .github/workflows/
 
 # Expected (if CI/CD requested):
 # ci.yml
-# cd.yml
 ```
 
 ---

package/dist/templates/.claude/commands/utility/trinity-workorder.md.template

@@ -42,7 +42,7 @@ When `/trinity-workorder` is invoked, the agent will:
    - Deliverables and acceptance criteria
    - Priority and estimated effort
 
-2. **Select appropriate template** from `trinity/templates/work-orders/`:
+2. **Select appropriate template** from `.claude/trinity/templates/work-orders/`:
    - **Investigation:** Research and analysis tasks
    - **Implementation:** Feature development tasks
    - **Analysis:** Code analysis and review tasks
@@ -50,7 +50,7 @@ When `/trinity-workorder` is invoked, the agent will:
    - **Pattern:** Pattern detection and analysis
    - **Verification:** Verification and validation tasks
 
-3. **Create work order file** in `trinity/work-orders/WO-XXX-{task-name}.md`
+3. **Create work order file** in `.claude/trinity/work-orders/WO-XXX-{task-name}.md`
 
 4. **Populate template** with:
    - Clear mission objective
@@ -78,13 +78,13 @@ When `/trinity-workorder` is invoked, the agent will:
 
 ## Orchestration
 
-Once work order is created in `trinity/work-orders/`, execute it:
+Once work order is created in `.claude/trinity/work-orders/`, execute it:
 
 ```bash
 /trinity-orchestrate @WO-001-example-task.md
 ```
 
-**AJ MAESTRO** picks up the work order from `trinity/work-orders/` and orchestrates the 19-agent team to complete the task following Trinity Method workflows.
+**AJ MAESTRO** picks up the work order from `.claude/trinity/work-orders/` and orchestrates the 18-agent team to complete the task following Trinity Method workflows.
 
 ---
 
@@ -96,7 +96,7 @@ See WO-042 example in work order files showing full structure with objectives, i
 
 ## Available Templates
 
-Work order templates are located in `trinity/templates/work-orders/`:
+Work order templates are located in `.claude/trinity/templates/work-orders/`:
 - **INVESTIGATION-TEMPLATE.md** - Research and analysis tasks
 - **IMPLEMENTATION-TEMPLATE.md** - Feature development tasks
 - **ANALYSIS-TEMPLATE.md** - Code analysis and review tasks

package/dist/templates/ci/ci.yml.template

@@ -1,9 +1,9 @@
-# {{PROJECT_NAME}} - Trinity Method CI/CD Pipeline
+# {{PROJECT_NAME}} - Trinity Method CI Pipeline
 # Trinity Method v{{TRINITY_VERSION}}
 # Framework: {{FRAMEWORK}}
 # Generated by: EIN (CI/CD Specialist)
 
-name: Trinity CI/CD Pipeline
+name: Trinity CI Pipeline
 
 on:
   push:

package/dist/templates/root/CLAUDE.md.template

@@ -20,7 +20,7 @@ This project uses the Trinity Method with layered context files:
 Project-specific overview, architecture, and living documentation references.
 
 ### 2. Trinity Method Context
-**File**: [trinity/CLAUDE.md](trinity/CLAUDE.md)
+**File**: [.claude/trinity/CLAUDE.md](.claude/trinity/CLAUDE.md)
 Enforces Trinity Method protocols: investigation-first development, quality gates, crisis management.
 
 ### 3. Technology-Specific Context
@@ -29,7 +29,7 @@ Framework-specific debugging standards, performance optimization, testing patter
 
 ### 4. Agent Directory
 **File**: [.claude/EMPLOYEE-DIRECTORY.md](.claude/EMPLOYEE-DIRECTORY.md)
-Complete guide to the 19-agent Trinity team and workflow orchestration.
+Complete guide to the 18-agent Trinity team and workflow orchestration.
 
 ---
 
@@ -37,29 +37,29 @@ Complete guide to the 19-agent Trinity team and workflow orchestration.
 
 ### Architecture
 
-See: [trinity/knowledge-base/ARCHITECTURE.md](trinity/knowledge-base/ARCHITECTURE.md)
+See: [.claude/trinity/knowledge-base/ARCHITECTURE.md](.claude/trinity/knowledge-base/ARCHITECTURE.md)
 
 ### Current Tasks
 
-See: [trinity/knowledge-base/To-do.md](trinity/knowledge-base/To-do.md)
+See: [.claude/trinity/knowledge-base/To-do.md](.claude/trinity/knowledge-base/To-do.md)
 
 ### Known Issues
 
-See: [trinity/knowledge-base/ISSUES.md](trinity/knowledge-base/ISSUES.md)
+See: [.claude/trinity/knowledge-base/ISSUES.md](.claude/trinity/knowledge-base/ISSUES.md)
 
 ### Technical Debt
 
-See: [trinity/knowledge-base/Technical-Debt.md](trinity/knowledge-base/Technical-Debt.md)
+See: [.claude/trinity/knowledge-base/Technical-Debt.md](.claude/trinity/knowledge-base/Technical-Debt.md)
 
 ### Testing Standards
 
-See: [trinity/knowledge-base/TESTING-PRINCIPLES.md](trinity/knowledge-base/TESTING-PRINCIPLES.md)
+See: [.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md](.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md)
 
 ### Coding Principles
 
-See: [trinity/knowledge-base/CODING-PRINCIPLES.md](trinity/knowledge-base/CODING-PRINCIPLES.md)
+See: [.claude/trinity/knowledge-base/CODING-PRINCIPLES.md](.claude/trinity/knowledge-base/CODING-PRINCIPLES.md)
 
 ---
 
 **Trinity Method:** Investigation-first development methodology
-**Session Location:** trinity/sessions/
+**Session Location:** .claude/trinity/sessions/

package/dist/templates/root/linting/nodejs/.husky-pre-commit.template

@@ -0,0 +1,5 @@
+#!/usr/bin/env sh
+# {{PROJECT_NAME}} - Pre-commit Quality Gates
+# Trinity Method v{{TRINITY_VERSION}}
+# Framework: {{FRAMEWORK}}
+npx lint-staged