@fermindi/pwn-cli 0.3.0 → 0.3.2

package/cli/inject.js

@@ -65,7 +65,9 @@ export default async function injectCommand(args = []) {
   console.log('   ├── patterns/       (auto-applied patterns)');
   console.log('   ├── workflows/      (batch execution)');
   console.log('   ├── agents/         (AI agent configs)');
-  console.log('   └── config/         (notifications, etc)\n');
+  console.log('   └── config/         (notifications, etc)');
+  console.log('   .claude/');
+  console.log('   └── commands/       (slash commands: /save)\n');
 
   // Show ntfy topic if generated
   const notifyPath = join(process.cwd(), '.ai', 'config', 'notifications.json');

package/cli/patterns.js

@@ -237,7 +237,7 @@ async function addPattern(args) {
   console.log(`Created pattern: ${patternId}`);
   console.log(`Directory: .ai/patterns/${category}/${name}/`);
   console.log('\nNext steps:');
-  console.log(`  1. Edit .ai/patterns/${category}/${name}/README.md`);
+  console.log(`  1. Create .ai/patterns/${category}/${name}/${name}.md with your pattern`);
   console.log('  2. Add trigger: pwn patterns triggers add');
 }
 

package/cli/update.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { existsSync, readFileSync, writeFileSync, cpSync, renameSync } from 'fs';
+import { existsSync, readFileSync, writeFileSync, cpSync, renameSync, mkdirSync, readdirSync } from 'fs';
 import { join, dirname } from 'path';
 import { fileURLToPath } from 'url';
 
@@ -13,14 +13,21 @@ const FRAMEWORK_FILES = [
   'agents/claude.md',
   'agents/README.md',
   'patterns/index.md',
-  'patterns/frontend/README.md',
-  'patterns/backend/README.md',
-  'patterns/universal/README.md',
+  'patterns/frontend/frontend.template.md',
+  'patterns/backend/backend.template.md',
+  'patterns/universal/universal.template.md',
   'workflows/batch-task.md',
   'config/README.md',
   'README.md',
 ];
 
+/**
+ * Claude Code slash commands (in .claude/commands/)
+ */
+const CLAUDE_COMMANDS = [
+  'save.md',
+];
+
 /**
  * Files that should NOT be updated (user data)
  * These contain user customizations
@@ -148,6 +155,64 @@ export default async function updateCommand(args = []) {
     }
   }
 
+  // Update .claude/commands/ (slash commands)
+  const claudeCommandsDir = join(cwd, '.claude', 'commands');
+  const templateCommandsDir = join(__dirname, '../templates/workspace/.claude/commands');
+
+  if (existsSync(templateCommandsDir)) {
+    for (const cmdFile of CLAUDE_COMMANDS) {
+      const templateFile = join(templateCommandsDir, cmdFile);
+      const targetFile = join(claudeCommandsDir, cmdFile);
+
+      if (!existsSync(templateFile)) {
+        continue;
+      }
+
+      const templateContent = readFileSync(templateFile, 'utf8');
+      const targetExists = existsSync(targetFile);
+      const targetContent = targetExists ? readFileSync(targetFile, 'utf8') : '';
+
+      if (templateContent !== targetContent) {
+        if (dryRun) {
+          console.log(`   📝 Would update: .claude/commands/${cmdFile}`);
+        } else {
+          // Ensure directory exists
+          if (!existsSync(claudeCommandsDir)) {
+            mkdirSync(claudeCommandsDir, { recursive: true });
+          }
+          writeFileSync(targetFile, templateContent);
+          console.log(`   📝 Updated: .claude/commands/${cmdFile}`);
+        }
+        updated.push(`.claude/commands/${cmdFile}`);
+      }
+    }
+  }
+
+  // ============================================
+  // MIGRATION: v1.1.0 (can remove after 2025-07-01)
+  // Rename README.md → .template.md in patterns/
+  // ============================================
+  const migrations = [
+    { from: 'patterns/frontend/README.md', to: 'patterns/frontend/frontend.template.md' },
+    { from: 'patterns/backend/README.md', to: 'patterns/backend/backend.template.md' },
+    { from: 'patterns/universal/README.md', to: 'patterns/universal/universal.template.md' },
+  ];
+
+  for (const { from, to } of migrations) {
+    const oldPath = join(aiDir, from);
+    const newPath = join(aiDir, to);
+    if (existsSync(oldPath) && !existsSync(newPath)) {
+      if (dryRun) {
+        console.log(`   🔄 Would migrate: ${from} → ${to}`);
+      } else {
+        renameSync(oldPath, newPath);
+        console.log(`   🔄 Migrated: ${from} → ${to}`);
+      }
+      updated.push(`${from} → ${to}`);
+    }
+  }
+  // ============================================
+
   // Update state.json with new version
   if (!dryRun && existsSync(statePath)) {
     try {
@@ -185,5 +250,6 @@ export default async function updateCommand(args = []) {
   console.log('🔒 Preserved (user data):');
   console.log('   .ai/memory/     (decisions, patterns, deadends)');
   console.log('   .ai/tasks/      (active, backlog)');
-  console.log('   .ai/state.json  (session state)\n');
+  console.log('   .ai/state.json  (session state)');
+  console.log('   .claude/        (your custom commands preserved)\n');
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fermindi/pwn-cli",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Professional AI Workspace - Inject structured memory and automation into any project for AI-powered development",
   "type": "module",
   "bin": {

package/src/core/inject.js

@@ -86,6 +86,14 @@ export function getTemplatePath() {
   return join(__dirname, '../../templates/workspace/.ai');
 }
 
+/**
+ * Get the path to the .claude commands template
+ * @returns {string} Path to .claude template directory
+ */
+export function getClaudeCommandsTemplatePath() {
+  return join(__dirname, '../../templates/workspace/.claude');
+}
+
 /**
  * Inject PWN workspace into a project
  * @param {object} options - Injection options
@@ -104,7 +112,9 @@ export async function inject(options = {}) {
   } = options;
 
   const templateDir = getTemplatePath();
+  const claudeTemplateDir = getClaudeCommandsTemplatePath();
   const targetDir = join(cwd, '.ai');
+  const claudeDir = join(cwd, '.claude');
 
   const log = silent ? () => {} : console.log;
 
@@ -193,6 +203,24 @@ export async function inject(options = {}) {
       }
     }
 
+    // Copy .claude/commands/ for slash commands
+    if (existsSync(claudeTemplateDir)) {
+      // Create .claude/commands/ if it doesn't exist
+      const commandsDir = join(claudeDir, 'commands');
+      if (!existsSync(commandsDir)) {
+        mkdirSync(commandsDir, { recursive: true });
+      }
+
+      // Copy all command files
+      const claudeCommandsSource = join(claudeTemplateDir, 'commands');
+      if (existsSync(claudeCommandsSource)) {
+        cpSync(claudeCommandsSource, commandsDir, { recursive: true });
+        if (!silent) {
+          console.log('📝 Created .claude/commands/ with PWN slash commands');
+        }
+      }
+    }
+
     // Backup other AI files (not CLAUDE.md) to .ai/
     const otherFiles = Object.fromEntries(
       Object.entries(backedUpContent).filter(([k]) => k.toLowerCase() !== 'claude.md')

package/src/patterns/registry.js

@@ -85,14 +85,14 @@ export class PatternRegistry {
         if (!entry.isDirectory()) continue;
 
         const patternPath = join(categoryPath, entry.name);
-        const readmePath = join(patternPath, 'README.md');
+        const mainFile = this.findMainPatternFile(patternPath);
 
         const pattern = {
           id: `${category}/${entry.name}`,
           name: this.formatName(entry.name),
           category,
           path: relative(this.aiPath, patternPath),
-          description: this.extractDescription(readmePath),
+          description: this.extractDescription(mainFile),
           triggers: [],
           metadata: {
             usageCount: 0,
@@ -110,10 +110,29 @@ export class PatternRegistry {
   }
 
   /**
-   * Extract description from README.md first line
+   * Find the main pattern file in a directory
+   * Looks for .md files (excluding .template.md)
    */
-  extractDescription(readmePath) {
-    if (!existsSync(readmePath)) {
+  findMainPatternFile(patternPath) {
+    if (!existsSync(patternPath)) return null;
+
+    try {
+      const files = readdirSync(patternPath);
+      // Find first .md file that's not a template
+      const mdFile = files.find(f =>
+        f.endsWith('.md') && !f.endsWith('.template.md')
+      );
+      return mdFile ? join(patternPath, mdFile) : null;
+    } catch {
+      return null;
+    }
+  }
+
+  /**
+   * Extract description from pattern file first line
+   */
+  extractDescription(filePath) {
+    if (!filePath || !existsSync(filePath)) {
       return 'No description available';
     }
 
@@ -213,9 +232,10 @@ export class PatternRegistry {
     if (!existsSync(patternDir)) {
       mkdirSync(patternDir, { recursive: true });
 
-      // Create README.md with description
-      const readmePath = join(patternDir, 'README.md');
-      writeFileSync(readmePath, `# ${pattern.name}\n\n${pattern.description || ''}\n`);
+      // Create pattern file with description (use pattern name as filename)
+      const patternName = basename(pattern.path || pattern.id);
+      const patternFile = join(patternDir, `${patternName}.md`);
+      writeFileSync(patternFile, `# ${pattern.name}\n\n${pattern.description || ''}\n`);
     }
 
     // Set metadata
@@ -252,7 +272,7 @@ export class PatternRegistry {
   }
 
   /**
-   * Get pattern content (README.md)
+   * Get pattern content (first .md file, excluding templates)
    * @param {string} id - Pattern ID
    * @returns {string|null}
    */
@@ -261,10 +281,12 @@ export class PatternRegistry {
     if (!pattern) return null;
 
     // pattern.path is relative to aiPath (e.g., "patterns/frontend/react")
-    const readmePath = join(this.aiPath, pattern.path, 'README.md');
-    if (!existsSync(readmePath)) return null;
+    const patternDir = join(this.aiPath, pattern.path);
+    const mainFile = this.findMainPatternFile(patternDir);
+
+    if (!mainFile) return null;
 
-    return readFileSync(readmePath, 'utf8');
+    return readFileSync(mainFile, 'utf8');
   }
 
   /**

package/templates/workspace/.ai/patterns/backend/backend.template.md

@@ -0,0 +1,19 @@
+<!--
+  AI: This is an example template. DO NOT edit this file.
+  Create new .md files as you discover patterns.
+  Examples: api-routes.md, prisma-queries.md, auth-flow.md
+-->
+
+# [Pattern Name]
+
+## Context
+When to apply this pattern.
+
+## Pattern
+Description or code example.
+
+## Rationale
+Why this approach works better.
+
+## Examples
+- `src/routes/users.ts:28`

package/templates/workspace/.ai/patterns/frontend/frontend.template.md

@@ -0,0 +1,19 @@
+<!--
+  AI: This is an example template. DO NOT edit this file.
+  Create new .md files as you discover patterns.
+  Examples: react-hooks.md, form-validation.md, state-management.md
+-->
+
+# [Pattern Name]
+
+## Context
+When to apply this pattern.
+
+## Pattern
+Description or code example.
+
+## Rationale
+Why this approach works better.
+
+## Examples
+- `src/components/Button.tsx:42`

package/templates/workspace/.ai/patterns/index.md

@@ -208,9 +208,9 @@ patterns/
 ```
 
 Each directory contains:
-- `README.md` - Pattern documentation
+- `<category>.template.md` - Template showing pattern format (don't edit)
+- `<pattern-name>.md` - Actual patterns created by AI as it learns
 - `*.example.ts` - Code examples (optional)
-- `checklist.md` - Verification checklist (optional)
 
 ---
 
@@ -220,22 +220,22 @@ Each directory contains:
 
 **Condition:** User edits `src/components/Button.tsx`
 **Triggers:** `*.tsx` matches
-**Load:** `patterns/frontend/react/README.md`
-**Apply:** React component best practices to Button component
+**Load:** `patterns/frontend/react-components.md` (if exists)
+**Apply:** React component patterns learned in this project
 
 ### Example 2: API Endpoint Trigger
 
 **Condition:** User imports `from 'express'`
 **Triggers:** `import.*express` matches
-**Load:** `patterns/backend/express/README.md` + `patterns/universal/rest-api/README.md`
-**Apply:** Express + REST API patterns to new route
+**Load:** `patterns/backend/api-routes.md` (if exists)
+**Apply:** Express + REST API patterns learned in this project
 
 ### Example 3: Test File Trigger
 
 **Condition:** User creates `src/__tests__/utils.test.ts`
-**Triggers:** `*.test.ts` matches + `import jest` matches
-**Load:** `patterns/universal/testing/unit/README.md`
-**Apply:** Unit test patterns and Jest best practices
+**Triggers:** `*.test.ts` matches
+**Load:** `patterns/universal/testing.md` (if exists)
+**Apply:** Test patterns learned in this project
 
 ---
 

package/templates/workspace/.ai/patterns/universal/universal.template.md

@@ -0,0 +1,19 @@
+<!--
+  AI: This is an example template. DO NOT edit this file.
+  Create new .md files as you discover patterns.
+  Examples: error-handling.md, testing.md, typescript-utils.md
+-->
+
+# [Pattern Name]
+
+## Context
+When to apply this pattern.
+
+## Pattern
+Description or code example.
+
+## Rationale
+Why this approach works better.
+
+## Examples
+- `src/lib/errors.ts:15`

package/templates/workspace/.claude/commands/save.md

@@ -0,0 +1,142 @@
+# /save - PWN Session Save
+
+Save your current work state to PWN framework files (.ai/state.json and .ai/memory/).
+
+## What this command does
+
+1. Updates .ai/state.json with current session state
+2. Updates .ai/tasks/active.md with task progress
+3. Logs new dead ends to .ai/memory/deadends.md
+4. Optionally updates .ai/memory/decisions.md with new decisions
+5. Creates archive entry in .ai/memory/archive/
+
+---
+
+## Instructions
+
+First, identify the current developer by running:
+
+```bash
+git config user.name
+```
+
+Then, analyze the current session and update PWN files accordingly.
+
+## Files to Update
+
+### 1. State File (.ai/state.json)
+
+Update the session state:
+
+```json
+{
+  "developer": "{username from git config}",
+  "session_started": "{ISO timestamp}",
+  "session_mode": "interactive",
+  "current_task": "{task ID or null}",
+  "context_loaded": ["memory", "patterns", "tasks"],
+  "last_save": "{current ISO timestamp}"
+}
+```
+
+### 2. Active Tasks (.ai/tasks/active.md)
+
+If there are tasks in progress:
+- Update checkbox status ([ ] or [x])
+- Add notes about blockers
+- Update priority if changed
+
+### 3. Dead Ends (.ai/memory/deadends.md)
+
+When a new dead end is discovered:
+
+1. **Get next ID** from existing entries (last DE-XXX + 1)
+
+2. **Add detailed entry**:
+```markdown
+## DE-XXX: Title
+
+**Date:** YYYY-MM-DD
+**Attempted:** What was tried
+**Problem:** Why it failed
+**Solution:** What worked instead
+**Tags:** relevant, keywords
+```
+
+### 4. Decisions (.ai/memory/decisions.md)
+
+If new architectural decisions were made:
+
+1. **Get next ID** from existing entries (last DEC-XXX + 1)
+
+2. **Add entry**:
+```markdown
+## DEC-XXX: Decision Title
+
+**Date:** YYYY-MM-DD
+**Status:** Active
+**Context:** Why this decision was needed
+**Decision:** What was decided
+**Rationale:** Why this is the best choice
+```
+
+### 5. Archive Entry (.ai/memory/archive/{date}-session.md)
+
+Create a session summary:
+
+```markdown
+# Session: YYYY-MM-DD
+
+## Summary
+{brief description of what was done this session}
+
+## Tasks
+### Completed
+- [x] Task descriptions...
+
+### In Progress
+- [ ] Task descriptions...
+
+## Decisions Made
+- DEC-XXX: description (if any)
+
+## Dead Ends
+- DE-XXX: description (if any)
+
+---
+*Saved: {ISO timestamp}*
+```
+
+---
+
+## Output Format
+
+After updating all files, confirm to the user:
+
+```
+PWN Save Complete:
+- State: .ai/state.json updated (developer: {username})
+- Tasks: {X} active, {Y} completed
+- Dead Ends: {new count or "no new"}
+- Decisions: {new count or "no new"}
+- Archive: .ai/memory/archive/{filename}
+- Last updated: {timestamp}
+```
+
+---
+
+## Rules
+
+1. **state.json**: Only current session state, no history
+2. **deadends.md**: Detailed entries with proper DE-XXX IDs
+3. **decisions.md**: Organized entries with proper DEC-XXX IDs
+4. **active.md**: Only current sprint tasks
+5. **archive/**: One file per session with summary
+
+---
+
+## Notes
+
+- This command replaces the old /checkpoint command
+- Uses PWN framework structure in .ai/ directory
+- Always get the next available ID number before adding entries

package/templates/workspace/.ai/patterns/backend/README.md

@@ -1,126 +0,0 @@
-# Backend Patterns
-
-This directory contains design patterns and best practices for backend development.
-
-## Overview
-
-Backend patterns cover:
-- Express.js route structure
-- REST API design
-- Database queries and migrations
-- Error handling and logging
-- Authentication and authorization
-- Data validation
-- Performance optimization
-- Middleware patterns
-- Integration patterns
-
-## Structure
-
-```
-backend/
-├── README.md                  # This file
-├── express/                   # Express.js patterns
-│   └── README.md             # Express routing and middleware
-├── database/                  # Database patterns
-│   └── README.md             # Query and ORM patterns
-├── api-design/                # REST API patterns
-│   └── README.md             # API structure and conventions
-├── security/                  # Security patterns
-│   └── README.md             # Auth, validation, sanitization
-└── integration/               # Integration patterns
-    └── README.md             # Working with external services
-```
-
-## Auto-Apply Triggers
-
-These patterns are automatically loaded when:
-
-- **File:** `*.routes.ts`, `routes/*.ts` (Express routes)
-- **Import:** `from.*express`, `import.*Router`
-- **Path:** `src/routes/`, `src/api/`
-- **Keyword:** `app.get`, `app.post`, `router.use`
-
-See `patterns/index.md` for trigger configuration.
-
-## Common Patterns
-
-### Route Structure
-```typescript
-// Group related routes together
-// Use middleware for common operations (auth, logging)
-// Keep route handlers thin, logic in services
-// Consistent error handling
-```
-
-### Express Middleware
-- Authentication middleware early in chain
-- Error handling middleware last
-- Logging middleware for all requests
-- Request validation middleware
-- CORS middleware appropriately configured
-
-### API Design
-- RESTful conventions (GET, POST, PUT, DELETE)
-- Consistent response format
-- Proper HTTP status codes
-- Pagination for list endpoints
-- Filtering and sorting support
-
-### Database Queries
-- Use ORM/query builder (not raw SQL)
-- Eager load relationships when needed
-- Avoid N+1 query problems
-- Index frequently-queried columns
-- Use transactions for multi-step operations
-
-### Error Handling
-- Custom error classes for different error types
-- Consistent error response format
-- Log errors with full context
-- Don't expose internal errors to clients
-- Use HTTP status codes correctly
-
-### Validation
-- Validate all user input
-- Use schema validation (Zod, Joi, etc.)
-- Sanitize input to prevent injection
-- Custom validation rules for domain logic
-- Clear error messages for users
-
-### Authentication
-- Use industry-standard auth (JWT, OAuth, etc.)
-- Secure token storage
-- Token expiration and refresh strategy
-- Role-based access control (RBAC)
-- Audit logging of auth events
-
-## Usage
-
-1. Read the relevant sub-directory README for your task
-2. Check code examples for reference implementations
-3. Follow patterns in new routes and services
-4. Update patterns if you discover improvements
-
-## Contributing
-
-Found a better pattern?
-
-1. Document it with examples
-2. Add to appropriate subdirectory
-3. Update this README
-4. Commit with message: `docs: add [pattern name] pattern`
-5. Update triggers in `patterns/index.md` if widely applicable
-
-## Links
-
-- [Express Patterns](express/README.md)
-- [Database Patterns](database/README.md)
-- [API Design](api-design/README.md)
-- [Security Patterns](security/README.md)
-- [Integration Patterns](integration/README.md)
-
-## Version
-
-**Last Updated:** (Set on template injection)
-**Maintained By:** Development Team

package/templates/workspace/.ai/patterns/frontend/README.md

@@ -1,103 +0,0 @@
-# Frontend Patterns
-
-This directory contains design patterns and best practices for frontend development.
-
-## Overview
-
-Frontend patterns cover:
-- React component architecture
-- TypeScript type definitions
-- Styling and CSS strategies
-- State management
-- Performance optimization
-- Accessibility (a11y)
-- Component composition
-- Hook patterns
-
-## Structure
-
-```
-frontend/
-├── README.md                  # This file
-├── react/                     # React-specific patterns
-│   └── README.md             # React component patterns
-├── styling/                   # CSS and styling patterns
-│   └── README.md             # Styling strategies
-├── component-libs/            # UI component library patterns
-│   └── README.md             # Working with component libraries
-└── accessibility/             # A11y patterns
-    └── README.md             # Accessibility patterns
-```
-
-## Auto-Apply Triggers
-
-These patterns are automatically loaded when:
-
-- **File:** `*.tsx`, `*.jsx` (React components)
-- **Import:** `import.*React`, `from.*react`
-- **Path:** `src/components/`
-- **Keyword:** `function Component`, `export default`
-
-See `patterns/index.md` for trigger configuration.
-
-## Common Patterns
-
-### Component Architecture
-- Functional components with hooks (not class components)
-- One component per file
-- Props interfaces at top of file
-- Hooks (useState, useEffect, useContext)
-- Custom hooks for reusable logic
-
-### TypeScript
-- Define interfaces for component props
-- Use `React.FC<Props>` for component type
-- Strict null checks enabled
-- Export types alongside components
-
-### State Management
-- Local state with `useState` for component-only state
-- Context API for shared state
-- Consider Redux/Zustand for complex state
-- Avoid prop drilling (use Context instead)
-
-### Performance
-- Memoize expensive components with `React.memo`
-- Use `useCallback` for stable function references
-- Use `useMemo` for expensive computations
-- Lazy load routes with `React.lazy`
-
-### Styling
-- TailwindCSS for utility-first styling
-- CSS modules for scoped styles
-- Avoid inline styles except for dynamic values
-- Use design tokens for consistency
-
-## Usage
-
-1. Read the relevant sub-directory README for your task
-2. Check code examples for reference implementations
-3. Follow patterns in new components
-4. Update patterns if you discover improvements
-
-## Contributing
-
-Found a better pattern?
-
-1. Document it with examples
-2. Add to appropriate subdirectory
-3. Update this README
-4. Commit with message: `docs: add [pattern name] pattern`
-5. Update triggers in `patterns/index.md` if widely applicable
-
-## Links
-
-- [React Component Patterns](react/README.md)
-- [Styling Strategies](styling/README.md)
-- [Component Libraries](component-libs/README.md)
-- [Accessibility Patterns](accessibility/README.md)
-
-## Version
-
-**Last Updated:** (Set on template injection)
-**Maintained By:** Development Team

package/templates/workspace/.ai/patterns/universal/README.md

@@ -1,141 +0,0 @@
-# Universal Patterns
-
-This directory contains cross-cutting patterns that apply to both frontend and backend development.
-
-## Overview
-
-Universal patterns cover:
-- TypeScript best practices
-- Testing strategies (unit, integration, e2e)
-- Error handling and logging
-- Git workflow and commit conventions
-- Build tool configuration
-- Code organization
-- Documentation standards
-- Performance profiling
-- Security principles
-
-## Structure
-
-```
-universal/
-├── README.md                  # This file
-├── typescript/                # TypeScript patterns
-│   └── README.md             # Type definitions, generics, etc.
-├── testing/                   # Testing patterns
-│   ├── unit/README.md        # Unit test patterns
-│   ├── integration/README.md # Integration test patterns
-│   └── e2e/README.md         # End-to-end test patterns
-├── error-handling/            # Error handling patterns
-│   └── README.md             # Exception handling, logging
-├── git/                       # Git workflow patterns
-│   └── README.md             # Branching, commits, PRs
-├── build-tools/               # Build and package patterns
-│   └── README.md             # Webpack, Vite, etc.
-├── performance/               # Performance optimization
-│   └── README.md             # Profiling, optimization
-└── security/                  # Security patterns
-    └── README.md             # Input validation, secrets, etc.
-```
-
-## Auto-Apply Triggers
-
-These patterns are automatically loaded when:
-
-- **File:** `*.ts`, `*.tsx` (TypeScript)
-- **File:** `*.test.ts`, `*.spec.ts` (Tests)
-- **Import:** `from 'jest'`, `from 'vitest'` (Testing)
-- **Command:** `git commit`, `npm build` (Git, Build)
-- **Path:** `src/__tests__/`, `cypress/`, `playwright/`
-
-See `patterns/index.md` for trigger configuration.
-
-## Common Patterns
-
-### TypeScript
-- Enable strict mode in `tsconfig.json`
-- Use interfaces for object shapes, types for aliases
-- Avoid `any` - use `unknown` with type guards instead
-- Export types alongside implementations
-- Use generics for reusable, type-safe code
-- Document complex types with JSDoc comments
-
-### Testing Strategy
-- Unit tests for utilities and pure functions
-- Integration tests for API endpoints and workflows
-- E2E tests for critical user journeys
-- Test file co-located with source: `feature.ts` + `feature.test.ts`
-- Aim for >80% code coverage on critical paths
-- Mock external dependencies, test real business logic
-
-### Error Handling
-- Use custom error classes that extend Error
-- Include error context (what, why, how to fix)
-- Log errors with full stack traces
-- Different handling strategies for different error types
-- Never silently catch and ignore errors
-- Provide user-friendly error messages
-
-### Git Workflow
-- Descriptive commit messages (50 char subject, blank line, details)
-- Atomic commits (one logical change per commit)
-- Branch naming: `feature/name`, `fix/name`, `docs/name`
-- Pull request template with context
-- Code review before merge
-- Squash or rebase to keep history clean
-
-### Build Tools
-- Consistent build configuration across projects
-- Separate dev and production builds
-- Fast development build (hot reload, source maps)
-- Optimized production build (minification, tree-shaking)
-- Automate with npm/pnpm scripts
-- Cache dependencies to speed up builds
-
-### Code Organization
-- Organize by feature, not by type
-- Keep related code together
-- Use barrel exports (`index.ts`) for clean imports
-- Avoid circular dependencies
-- Monorepo structure for related packages
-- Clear separation of concerns
-
-### Documentation
-- JSDoc comments for public APIs
-- README files in each directory explaining purpose
-- Architecture decision records (ADRs)
-- Code examples for complex logic
-- Keep docs in sync with code
-- Link to external references where relevant
-
-## Usage
-
-1. Read the relevant sub-directory README for your task
-2. Check code examples for reference implementations
-3. Apply patterns to new code
-4. Update patterns if you discover improvements
-
-## Contributing
-
-Found a better pattern?
-
-1. Document it with examples
-2. Add to appropriate subdirectory
-3. Update this README
-4. Commit with message: `docs: add [pattern name] pattern`
-5. Update triggers in `patterns/index.md` if widely applicable
-
-## Links
-
-- [TypeScript Patterns](typescript/README.md)
-- [Testing Strategies](testing/README.md)
-- [Error Handling](error-handling/README.md)
-- [Git Workflow](git/README.md)
-- [Build Tools](build-tools/README.md)
-- [Performance Profiling](performance/README.md)
-- [Security Principles](security/README.md)
-
-## Version
-
-**Last Updated:** (Set on template injection)
-**Maintained By:** Development Team