/enhance

description: Enhance an existing CLAUDE.md with Bitwarden's standardized template structure and supplementary research
allowed-tools: Read, Edit(CLAUDE.md), WebFetch, Grep, Glob

Enhance the existing CLAUDE.md file with Bitwarden's standardized template format.

**Prerequisites**: This command expects a CLAUDE.md file to already exist in the repository root (typically generated by Anthropic's `/init` command).

**Instructions:**

1. **Read Existing CLAUDE.md**: First, read the current CLAUDE.md file to understand what has already been documented about the project.

2. **Supplementary Research**: Perform additional codebase analysis to fill gaps and gather information for Bitwarden's extended sections:

• Examine security-related code, authentication flows, and authorization patterns
• Identify anti-patterns, common mistakes, or areas of technical debt
• Review data models, database schemas, and API contracts
• Look for configuration management, environment variables, and secrets handling
• Find testing patterns, utilities, and coverage expectations
• Analyze build, deployment, and CI/CD pipelines
• Identify common issues and debugging approaches
• Identify external documentation sources and authoritative references

3. **Enhance CLAUDE.md**: Restructure the file to use **exactly** the following sections.

**CRITICAL REQUIREMENTS:**

• The final CLAUDE.md MUST use these exact headings verbatim - no other top-level headings are allowed
• ALL content from the original CLAUDE.md MUST be incorporated into one of these sections - do not remove any information
• Reorganize and merge existing content into the appropriate sections below
• Add new information from your supplementary research to fill gaps

---

**Required Sections (use these exact headings):**

[Project Name] - Claude Code Configuration

Brief description of the project and its primary purpose.

Overview

What This Project Does

• Primary function/purpose (1-2 sentences)
• Key interfaces or entry points
• Target users/consumers

Key Concepts

• Domain-specific terminology
• Important abstractions to understand

---

Architecture & Patterns

System Architecture

[ASCII diagram showing high-level request flow]

Example:
    Client Request
         ↓
    Entry Point (index.ts)
         ↓
    ┌─────────────┬─────────────┐
    │  Handler A  │  Handler B  │
    │      ↓     │      ↓     │
    │  Service A  │  Service B  │
    └─────────────┴─────────────┘

Code Organization

src/
├── handlers/       # Request handlers
├── schemas/        # Validation schemas
├── services/       # Business logic
├── utils/          # Shared utilities
└── index.ts        # Entry point

Key Principles

1. **Principle One**: Brief explanation 2. **Principle Two**: Brief explanation 3. **Principle Three**: Brief explanation

Core Patterns

[Pattern Name] (e.g., Validation Wrapper)

**Purpose**: Why this pattern exists

**Implementation**:

// Code example showing the canonical implementation

**Usage**:

// Code example showing how to use the pattern

---

Development Guide

Adding New [Primary Entity]

Step-by-step checklist for the most common development task.

**1. Define the Schema** (`src/schemas/[domain].ts`)

// Template code

**2. Define the [Entity]** (`src/[entities]/[domain].ts`)

// Template code

**3. Implement the Handler** (`src/handlers/[domain].ts`)

// Template code

**4. Register the Handler** (`src/index.ts`)

// Where and how to register

**5. Write Tests** (`tests/[domain].spec.ts`)

// Test template

**6. Update Documentation**

• Files that may need updates

Common Patterns

[Pattern Category 1] (e.g., Request Handling)

// Code example with comments explaining key parts

[Pattern Category 2] (e.g., Error Handling)

// Code example with comments explaining key parts

Response Formatting

// Standard response structure
return {
  // ...
};

---

Data Models

Core Types

// Key interfaces and types used throughout the project
interface ExampleModel {
  id: string;
  name: string;
  // ...
}

Validation Schemas

// Zod schemas or similar validation definitions
const exampleSchema = z.object({
  // ...
});

---

Security & Configuration

Security Rules

**MANDATORY - These rules have no exceptions:**

1. **Rule One**: Explanation and rationale 2. **Rule Two**: Explanation and rationale 3. **Rule Three**: Explanation and rationale

Security Functions

| Function | Purpose | Usage | | ---------------- | ------------ | -------------- | | `functionName()` | What it does | When to use it |

Environment Configuration

| Variable | Required | Description | Example | | ---------- | -------- | ------------------ | --------------- | | `VAR_NAME` | Yes/No | What it configures | `example-value` |

Authentication & Authorization

• How authentication works
• Required credentials/tokens
• Token lifecycle management

---

Testing

Test Structure

tests/
├── unit/              # Unit tests
├── integration/       # Integration tests
└── fixtures/          # Test data

Writing Tests

**Unit Test Template**:

describe("[Feature]", () => {
  it("should [expected behavior]", () => {
    // Arrange
    // Act
    // Assert
  });
});

**Integration Test Template**:

describe("[Feature] Integration", () => {
  // Setup/teardown
  // Test cases
});

Running Tests

npm test              # Run all tests
npm run test:watch    # Watch mode
npm test -- [file]    # Run specific file

Test Environment

• Required mocks
• Environment variable setup
• Test data location

---

Code Style & Standards

Fo