@juho0719/cckit 0.2.7 → 0.2.8

package/assets/commands/update-codemaps.md

@@ -1,72 +0,0 @@
-# Update Codemaps
-
-Analyze the codebase structure and generate token-lean architecture documentation.
-
-## Step 1: Scan Project Structure
-
-1. Identify the project type (monorepo, single app, library, microservice)
-2. Find all source directories (src/, lib/, app/, packages/)
-3. Map entry points (main.ts, index.ts, app.py, main.go, etc.)
-
-## Step 2: Generate Codemaps
-
-Create or update codemaps in `docs/CODEMAPS/` (or `.reports/codemaps/`):
-
-| File | Contents |
-|------|----------|
-| `architecture.md` | High-level system diagram, service boundaries, data flow |
-| `backend.md` | API routes, middleware chain, service → repository mapping |
-| `frontend.md` | Page tree, component hierarchy, state management flow |
-| `data.md` | Database tables, relationships, migration history |
-| `dependencies.md` | External services, third-party integrations, shared libraries |
-
-### Codemap Format
-
-Each codemap should be token-lean — optimized for AI context consumption:
-
-```markdown
-# Backend Architecture
-
-## Routes
-POST /api/users → UserController.create → UserService.create → UserRepo.insert
-GET  /api/users/:id → UserController.get → UserService.findById → UserRepo.findById
-
-## Key Files
-src/services/user.ts (business logic, 120 lines)
-src/repos/user.ts (database access, 80 lines)
-
-## Dependencies
-- PostgreSQL (primary data store)
-- Redis (session cache, rate limiting)
-- Stripe (payment processing)
-```
-
-## Step 3: Diff Detection
-
-1. If previous codemaps exist, calculate the diff percentage
-2. If changes > 30%, show the diff and request user approval before overwriting
-3. If changes <= 30%, update in place
-
-## Step 4: Add Metadata
-
-Add a freshness header to each codemap:
-
-```markdown
-<!-- Generated: 2026-02-11 | Files scanned: 142 | Token estimate: ~800 -->
-```
-
-## Step 5: Save Analysis Report
-
-Write a summary to `.reports/codemap-diff.txt`:
-- Files added/removed/modified since last scan
-- New dependencies detected
-- Architecture changes (new routes, new services, etc.)
-- Staleness warnings for docs not updated in 90+ days
-
-## Tips
-
-- Focus on **high-level structure**, not implementation details
-- Prefer **file paths and function signatures** over full code blocks
-- Keep each codemap under **1000 tokens** for efficient context loading
-- Use ASCII diagrams for data flow instead of verbose descriptions
-- Run after major feature additions or refactoring sessions

package/assets/commands/update-docs.md

@@ -1,84 +0,0 @@
-# Update Documentation
-
-Sync documentation with the codebase, generating from source-of-truth files.
-
-## Step 1: Identify Sources of Truth
-
-| Source | Generates |
-|--------|-----------|
-| `package.json` scripts | Available commands reference |
-| `.env.example` | Environment variable documentation |
-| `openapi.yaml` / route files | API endpoint reference |
-| Source code exports | Public API documentation |
-| `Dockerfile` / `docker-compose.yml` | Infrastructure setup docs |
-
-## Step 2: Generate Script Reference
-
-1. Read `package.json` (or `Makefile`, `Cargo.toml`, `pyproject.toml`)
-2. Extract all scripts/commands with their descriptions
-3. Generate a reference table:
-
-```markdown
-| Command | Description |
-|---------|-------------|
-| `npm run dev` | Start development server with hot reload |
-| `npm run build` | Production build with type checking |
-| `npm test` | Run test suite with coverage |
-```
-
-## Step 3: Generate Environment Documentation
-
-1. Read `.env.example` (or `.env.template`, `.env.sample`)
-2. Extract all variables with their purposes
-3. Categorize as required vs optional
-4. Document expected format and valid values
-
-```markdown
-| Variable | Required | Description | Example |
-|----------|----------|-------------|---------|
-| `DATABASE_URL` | Yes | PostgreSQL connection string | `postgres://user:pass@host:5432/db` |
-| `LOG_LEVEL` | No | Logging verbosity (default: info) | `debug`, `info`, `warn`, `error` |
-```
-
-## Step 4: Update Contributing Guide
-
-Generate or update `docs/CONTRIBUTING.md` with:
-- Development environment setup (prerequisites, install steps)
-- Available scripts and their purposes
-- Testing procedures (how to run, how to write new tests)
-- Code style enforcement (linter, formatter, pre-commit hooks)
-- PR submission checklist
-
-## Step 5: Update Runbook
-
-Generate or update `docs/RUNBOOK.md` with:
-- Deployment procedures (step-by-step)
-- Health check endpoints and monitoring
-- Common issues and their fixes
-- Rollback procedures
-- Alerting and escalation paths
-
-## Step 6: Staleness Check
-
-1. Find documentation files not modified in 90+ days
-2. Cross-reference with recent source code changes
-3. Flag potentially outdated docs for manual review
-
-## Step 7: Show Summary
-
-```
-Documentation Update
-──────────────────────────────
-Updated:  docs/CONTRIBUTING.md (scripts table)
-Updated:  docs/ENV.md (3 new variables)
-Flagged:  docs/DEPLOY.md (142 days stale)
-Skipped:  docs/API.md (no changes detected)
-──────────────────────────────
-```
-
-## Rules
-
-- **Single source of truth**: Always generate from code, never manually edit generated sections
-- **Preserve manual sections**: Only update generated sections; leave hand-written prose intact
-- **Mark generated content**: Use `<!-- AUTO-GENERATED -->` markers around generated sections
-- **Don't create docs unprompted**: Only create new doc files if the command explicitly requests it

package/assets/commands/verify.md

@@ -1,59 +0,0 @@
-# Verification Command
-
-Run comprehensive verification on current codebase state.
-
-## Instructions
-
-Execute verification in this exact order:
-
-1. **Build Check**
-   - Run the build command for this project
-   - If it fails, report errors and STOP
-
-2. **Type Check**
-   - Run TypeScript/type checker
-   - Report all errors with file:line
-
-3. **Lint Check**
-   - Run linter
-   - Report warnings and errors
-
-4. **Test Suite**
-   - Run all tests
-   - Report pass/fail count
-   - Report coverage percentage
-
-5. **Console.log Audit**
-   - Search for console.log in source files
-   - Report locations
-
-6. **Git Status**
-   - Show uncommitted changes
-   - Show files modified since last commit
-
-## Output
-
-Produce a concise verification report:
-
-```
-VERIFICATION: [PASS/FAIL]
-
-Build:    [OK/FAIL]
-Types:    [OK/X errors]
-Lint:     [OK/X issues]
-Tests:    [X/Y passed, Z% coverage]
-Secrets:  [OK/X found]
-Logs:     [OK/X console.logs]
-
-Ready for PR: [YES/NO]
-```
-
-If any critical issues, list them with fix suggestions.
-
-## Arguments
-
-$ARGUMENTS can be:
-- `quick` - Only build + types
-- `full` - All checks (default)
-- `pre-commit` - Checks relevant for commits
-- `pre-pr` - Full checks plus security scan

package/assets/hooks/agent-track.sh

@@ -1,53 +0,0 @@
-#!/usr/bin/env bash
-# Agent 툴 실행 추적 — 여러 에이전트 동시 지원
-# @hook-event PreToolUse|Agent|pre
-# @hook-event PostToolUse|Agent|post
-
-AGENT_STATE_DIR="/tmp/claude-agents"
-mkdir -p "$AGENT_STATE_DIR"
-
-EVENT="${1:-post}"
-INPUT=$(cat)
-
-# subagent_type + description으로 고유 파일명 생성
-AGENT_ID=$(echo "$INPUT" | python3 -c "
-import sys, json, hashlib
-try:
-    d = json.load(sys.stdin)
-    ti = d.get('tool_input', {})
-    key = (ti.get('subagent_type', '') or '') + '|' + (ti.get('description', '') or '')
-    print(hashlib.md5(key.encode()).hexdigest()[:12])
-except:
-    print('')
-" 2>/dev/null)
-
-if [ -z "$AGENT_ID" ]; then
-  exit 0
-fi
-
-if [ "$EVENT" = "pre" ]; then
-  SUBAGENT_TYPE=$(echo "$INPUT" | python3 -c "
-import sys, json
-try:
-    d = json.load(sys.stdin)
-    print(d.get('tool_input', {}).get('subagent_type', '') or '')
-except:
-    print('')
-" 2>/dev/null)
-
-  DESCRIPTION=$(echo "$INPUT" | python3 -c "
-import sys, json
-try:
-    d = json.load(sys.stdin)
-    desc = d.get('tool_input', {}).get('description', '') or ''
-    print(desc[:50] if len(desc) > 50 else desc)
-except:
-    print('')
-" 2>/dev/null)
-
-  if [ -n "$SUBAGENT_TYPE" ]; then
-    echo "${SUBAGENT_TYPE}|${DESCRIPTION}" > "${AGENT_STATE_DIR}/${AGENT_ID}"
-  fi
-else
-  rm -f "${AGENT_STATE_DIR}/${AGENT_ID}"
-fi

package/assets/hooks/auto-commit-push.sh

@@ -1,123 +0,0 @@
-#!/bin/bash
-# Auto commit & push hook - runs when Claude Code finishes a response
-# @hook-event Stop||
-# Compatible with bash 3.2 (macOS default)
-
-# Get the working directory from the hook input
-WORK_DIR=$(echo "$CLAUDE_HOOK_INPUT" | jq -r '.cwd // empty' 2>/dev/null)
-if [ -z "$WORK_DIR" ]; then
-  WORK_DIR="$(pwd)"
-fi
-
-cd "$WORK_DIR" 2>/dev/null || exit 0
-
-# Check if we're in a git repo
-if ! git rev-parse --is-inside-work-tree &>/dev/null; then
-  exit 0
-fi
-
-# Check if there are any changes
-if git diff --quiet && git diff --cached --quiet && [ -z "$(git ls-files --others --exclude-standard)" ]; then
-  exit 0
-fi
-
-BRANCH=$(git symbolic-ref --short HEAD 2>/dev/null)
-if [ -z "$BRANCH" ]; then
-  exit 0
-fi
-
-# Stage all changes
-git add -A
-
-# ── 변경 파일 목록 수집 ───────────────────────────────
-ADDED_FILES=$(git diff --cached --diff-filter=A --name-only)
-MODIFIED_FILES=$(git diff --cached --diff-filter=M --name-only)
-DELETED_FILES=$(git diff --cached --diff-filter=D --name-only)
-
-ALL_FILES=$(git diff --cached --name-only)
-ADDED_COUNT=$(echo "$ADDED_FILES"   | grep -c . || true)
-MODIFIED_COUNT=$(echo "$MODIFIED_FILES" | grep -c . || true)
-DELETED_COUNT=$(echo "$DELETED_FILES"  | grep -c . || true)
-
-# ── 커밋 타입 감지 ────────────────────────────────────
-# test: 파일이 모두 테스트/설정 관련이면 test/chore
-HAS_TEST=$(echo "$ALL_FILES" | grep -E "(\.test\.|\.spec\.|__tests__|e2e/)" | head -1)
-HAS_CONFIG=$(echo "$ALL_FILES" | grep -E "\.(config|json|yaml|yml|env|toml)$" | head -1)
-HAS_ROADMAP=$(echo "$ALL_FILES" | grep -E "roadmap|ROADMAP|\.md$" | head -1)
-HAS_SRC=$(echo "$ALL_FILES" | grep -E "^src/" | head -1)
-
-if [ -n "$HAS_TEST" ] && [ -z "$HAS_SRC" ]; then
-  COMMIT_TYPE="test"
-elif [ -n "$HAS_CONFIG" ] && [ -z "$HAS_SRC" ]; then
-  COMMIT_TYPE="chore"
-elif [ -n "$HAS_ROADMAP" ] && [ -z "$HAS_SRC" ]; then
-  COMMIT_TYPE="docs"
-else
-  COMMIT_TYPE="feat"
-fi
-
-# ── 스코프: 가장 많이 변경된 2단계 디렉토리 ────────────
-SCOPE=$(echo "$ALL_FILES" \
-  | awk -F'/' 'NF>=2 {print $1"/"$2} NF==1 {print $1}' \
-  | sort | uniq -c | sort -rn \
-  | awk 'NR==1{print $2}')
-[ -z "$SCOPE" ] && SCOPE="root"
-
-# ── Subject: 주요 파일명 나열 (확장자 제거, 최대 3개) ───
-key_files() {
-  echo "$1" | while IFS= read -r f; do
-    [ -n "$f" ] && basename "$f" | sed 's/\.[^.]*$//'
-  done | head -3 | tr '\n' ',' | sed 's/,$//' | sed 's/,/, /g'
-}
-
-ADDED_NAMES=$(key_files "$ADDED_FILES")
-MODIFIED_NAMES=$(key_files "$MODIFIED_FILES")
-DELETED_NAMES=$(key_files "$DELETED_FILES")
-
-SUBJECT_PARTS=""
-[ -n "$ADDED_NAMES" ]   && SUBJECT_PARTS="${SUBJECT_PARTS}add ${ADDED_NAMES}"
-[ -n "$MODIFIED_NAMES" ] && SUBJECT_PARTS="${SUBJECT_PARTS:+$SUBJECT_PARTS; }update ${MODIFIED_NAMES}"
-[ -n "$DELETED_NAMES" ]  && SUBJECT_PARTS="${SUBJECT_PARTS:+$SUBJECT_PARTS; }remove ${DELETED_NAMES}"
-
-# 파일이 4개 이상이면 개수도 병기
-TOTAL=$((ADDED_COUNT + MODIFIED_COUNT + DELETED_COUNT))
-if [ "$TOTAL" -gt 3 ]; then
-  SUBJECT_PARTS="${SUBJECT_PARTS} (+$((TOTAL - 3)) more)"
-fi
-
-SUBJECT="${COMMIT_TYPE}(${SCOPE}): ${SUBJECT_PARTS}"
-
-# ── Body: 전체 파일 목록 ─────────────────────────────
-BODY=""
-if [ -n "$ADDED_FILES" ]; then
-  BODY="${BODY}New files:\n"
-  while IFS= read -r f; do
-    [ -n "$f" ] && BODY="${BODY}  + ${f}\n"
-  done <<< "$ADDED_FILES"
-fi
-if [ -n "$MODIFIED_FILES" ]; then
-  [ -n "$BODY" ] && BODY="${BODY}\n"
-  BODY="${BODY}Modified:\n"
-  while IFS= read -r f; do
-    [ -n "$f" ] && BODY="${BODY}  ~ ${f}\n"
-  done <<< "$MODIFIED_FILES"
-fi
-if [ -n "$DELETED_FILES" ]; then
-  [ -n "$BODY" ] && BODY="${BODY}\n"
-  BODY="${BODY}Deleted:\n"
-  while IFS= read -r f; do
-    [ -n "$f" ] && BODY="${BODY}  - ${f}\n"
-  done <<< "$DELETED_FILES"
-fi
-
-FULL_MSG="${SUBJECT}\n\n${BODY}"
-
-git commit -m "$(printf "%b" "$FULL_MSG")" --no-verify 2>/dev/null
-
-# Push to remote if available
-REMOTE=$(git remote 2>/dev/null | head -1)
-if [ -n "$REMOTE" ]; then
-  git push "$REMOTE" "$BRANCH" --no-verify 2>/dev/null
-fi
-
-exit 0

package/assets/hooks/on-prompt-start.sh

@@ -1,6 +0,0 @@
-#!/usr/bin/env bash
-# 새 요청 시작 시 agent 상태 파일 초기화
-# @hook-event UserPromptSubmit||
-
-rm -f /tmp/claude-agents/* 2>/dev/null
-exit 0

package/assets/hooks/post-edit-format.js

@@ -1,48 +0,0 @@
-#!/usr/bin/env node
-/**
- * PostToolUse Hook: Auto-format JS/TS files with Prettier after edits
- *
- * Cross-platform (Windows, macOS, Linux)
- *
- * Runs after Edit tool use. If the edited file is a JS/TS file,
- * formats it with Prettier. Fails silently if Prettier isn't installed.
- */
-
-const { execFileSync } = require('child_process');
-const path = require('path');
-
-const MAX_STDIN = 1024 * 1024; // 1MB limit
-let data = '';
-process.stdin.setEncoding('utf8');
-
-process.stdin.on('data', chunk => {
-  if (data.length < MAX_STDIN) {
-    const remaining = MAX_STDIN - data.length;
-    data += chunk.substring(0, remaining);
-  }
-});
-
-process.stdin.on('end', () => {
-  try {
-    const input = JSON.parse(data);
-    const filePath = input.tool_input?.file_path;
-
-    if (filePath && /\.(ts|tsx|js|jsx)$/.test(filePath)) {
-      try {
-        // Use npx.cmd on Windows to avoid shell: true which enables command injection
-        const npxBin = process.platform === 'win32' ? 'npx.cmd' : 'npx';
-        execFileSync(npxBin, ['prettier', '--write', filePath], {
-          cwd: path.dirname(path.resolve(filePath)),
-          stdio: ['pipe', 'pipe', 'pipe'],
-          timeout: 15000
-        });
-      } catch {
-        // Prettier not installed, file missing, or failed — non-blocking
-      }
-    }
-  } catch {
-    // Invalid input — pass through
-  }
-
-  process.exit(0);
-});

package/assets/hooks/post-edit-typecheck.js

@@ -1,94 +0,0 @@
-#!/usr/bin/env node
-/**
- * PostToolUse Hook: TypeScript check after editing .ts/.tsx files
- *
- * Cross-platform (Windows, macOS, Linux)
- *
- * Runs after Edit tool use on TypeScript files. Walks up from the file's
- * directory to find the nearest tsconfig.json, then runs tsc --noEmit
- * and reports only errors related to the edited file.
- */
-
-const { execFileSync } = require("child_process");
-const fs = require("fs");
-const path = require("path");
-
-const MAX_STDIN = 1024 * 1024; // 1MB limit
-let data = "";
-process.stdin.setEncoding("utf8");
-
-process.stdin.on("data", (chunk) => {
-  if (data.length < MAX_STDIN) {
-    const remaining = MAX_STDIN - data.length;
-    data += chunk.substring(0, remaining);
-  }
-});
-
-process.stdin.on("end", () => {
-  try {
-    const input = JSON.parse(data);
-    const filePath = input.tool_input?.file_path;
-
-    if (filePath && /\.(ts|tsx)$/.test(filePath)) {
-      const resolvedPath = path.resolve(filePath);
-      if (!fs.existsSync(resolvedPath)) {
-        process.exit(0);
-      }
-      // Find nearest tsconfig.json by walking up (max 20 levels to prevent infinite loop)
-      let dir = path.dirname(resolvedPath);
-      const root = path.parse(dir).root;
-      let depth = 0;
-
-      while (dir !== root && depth < 20) {
-        if (fs.existsSync(path.join(dir, "tsconfig.json"))) {
-          break;
-        }
-        dir = path.dirname(dir);
-        depth++;
-      }
-
-      if (fs.existsSync(path.join(dir, "tsconfig.json"))) {
-        try {
-          // Use npx.cmd on Windows to avoid shell: true which enables command injection
-          const npxBin = process.platform === "win32" ? "npx.cmd" : "npx";
-          execFileSync(npxBin, ["tsc", "--noEmit", "--pretty", "false"], {
-            cwd: dir,
-            encoding: "utf8",
-            stdio: ["pipe", "pipe", "pipe"],
-            timeout: 30000,
-          });
-        } catch (err) {
-          // tsc exits non-zero when there are errors — filter to edited file
-          const output = (err.stdout || "") + (err.stderr || "");
-          // Compute paths that uniquely identify the edited file.
-          // tsc output uses paths relative to its cwd (the tsconfig dir),
-          // so check for the relative path, absolute path, and original path.
-          // Avoid bare basename matching — it causes false positives when
-          // multiple files share the same name (e.g., src/utils.ts vs tests/utils.ts).
-          const relPath = path.relative(dir, resolvedPath);
-          const candidates = new Set([filePath, resolvedPath, relPath]);
-          const relevantLines = output
-            .split("\n")
-            .filter((line) => {
-              for (const candidate of candidates) {
-                if (line.includes(candidate)) return true;
-              }
-              return false;
-            })
-            .slice(0, 10);
-
-          if (relevantLines.length > 0) {
-            console.error(
-              "[Hook] TypeScript errors in " + path.basename(filePath) + ":",
-            );
-            relevantLines.forEach((line) => console.error(line));
-          }
-        }
-      }
-    }
-  } catch {
-    // Invalid input — pass through
-  }
-
-  process.exit(0);
-});

package/assets/hooks/skill-track.sh

@@ -1,26 +0,0 @@
-#!/usr/bin/env bash
-# Skill 툴 실행 추적
-# @hook-event PreToolUse|Skill|pre
-# @hook-event PostToolUse|Skill|post
-
-SKILL_STATE_FILE="/tmp/claude-active-skill.txt"
-
-EVENT="${1:-post}"
-INPUT=$(cat)
-
-if [ "$EVENT" = "pre" ]; then
-  SKILL_NAME=$(echo "$INPUT" | python3 -c "
-import sys, json
-try:
-    d = json.load(sys.stdin)
-    print(d.get('tool_input', {}).get('skill', '') or '')
-except:
-    print('')
-" 2>/dev/null)
-
-  if [ -n "$SKILL_NAME" ]; then
-    echo "$SKILL_NAME" > "$SKILL_STATE_FILE"
-  fi
-else
-  rm -f "$SKILL_STATE_FILE"
-fi

package/assets/hooks/subagent-notify.sh

@@ -1,20 +0,0 @@
-#!/usr/bin/env bash
-# 응답 완료 시 macOS 알림 발송 — 마지막 커밋 메시지를 요약으로 표시
-# @hook-event Stop||
-
-WORK_DIR=$(echo "$CLAUDE_HOOK_INPUT" | jq -r '.cwd // empty' 2>/dev/null)
-if [ -z "$WORK_DIR" ]; then
-  WORK_DIR="$(pwd)"
-fi
-
-# 마지막 git 커밋 메시지를 알림 본문으로 사용
-MSG=""
-if git -C "$WORK_DIR" rev-parse --is-inside-work-tree &>/dev/null; then
-  MSG=$(git -C "$WORK_DIR" log --oneline -1 --format="%s" 2>/dev/null)
-fi
-
-if [ -z "$MSG" ]; then
-  MSG="응답이 완료됐습니다."
-fi
-
-osascript -e "display notification \"${MSG}\" with title \"Claude Code\" subtitle \"응답 완료\" sound name \"Glass\""

package/assets/rules/common/agents.md

@@ -1,49 +0,0 @@
-# Agent Orchestration
-
-## Available Agents
-
-Located in `~/.claude/agents/`:
-
-| Agent | Purpose | When to Use |
-|-------|---------|-------------|
-| planner | Implementation planning | Complex features, refactoring |
-| architect | System design | Architectural decisions |
-| tdd-guide | Test-driven development | New features, bug fixes |
-| code-reviewer | Code review | After writing code |
-| security-reviewer | Security analysis | Before commits |
-| build-error-resolver | Fix build errors | When build fails |
-| e2e-runner | E2E testing | Critical user flows |
-| refactor-cleaner | Dead code cleanup | Code maintenance |
-| doc-updater | Documentation | Updating docs |
-
-## Immediate Agent Usage
-
-No user prompt needed:
-1. Complex feature requests - Use **planner** agent
-2. Code just written/modified - Use **code-reviewer** agent
-3. Bug fix or new feature - Use **tdd-guide** agent
-4. Architectural decision - Use **architect** agent
-
-## Parallel Task Execution
-
-ALWAYS use parallel Task execution for independent operations:
-
-```markdown
-# GOOD: Parallel execution
-Launch 3 agents in parallel:
-1. Agent 1: Security analysis of auth module
-2. Agent 2: Performance review of cache system
-3. Agent 3: Type checking of utilities
-
-# BAD: Sequential when unnecessary
-First agent 1, then agent 2, then agent 3
-```
-
-## Multi-Perspective Analysis
-
-For complex problems, use split role sub-agents:
-- Factual reviewer
-- Senior engineer
-- Security expert
-- Consistency reviewer
-- Redundancy checker

package/assets/rules/common/coding-style.md

@@ -1,48 +0,0 @@
-# Coding Style
-
-## Immutability (CRITICAL)
-
-ALWAYS create new objects, NEVER mutate existing ones:
-
-```
-// Pseudocode
-WRONG:  modify(original, field, value) → changes original in-place
-CORRECT: update(original, field, value) → returns new copy with change
-```
-
-Rationale: Immutable data prevents hidden side effects, makes debugging easier, and enables safe concurrency.
-
-## File Organization
-
-MANY SMALL FILES > FEW LARGE FILES:
-- High cohesion, low coupling
-- 200-400 lines typical, 800 max
-- Extract utilities from large modules
-- Organize by feature/domain, not by type
-
-## Error Handling
-
-ALWAYS handle errors comprehensively:
-- Handle errors explicitly at every level
-- Provide user-friendly error messages in UI-facing code
-- Log detailed error context on the server side
-- Never silently swallow errors
-
-## Input Validation
-
-ALWAYS validate at system boundaries:
-- Validate all user input before processing
-- Use schema-based validation where available
-- Fail fast with clear error messages
-- Never trust external data (API responses, user input, file content)
-
-## Code Quality Checklist
-
-Before marking work complete:
-- [ ] Code is readable and well-named
-- [ ] Functions are small (<50 lines)
-- [ ] Files are focused (<800 lines)
-- [ ] No deep nesting (>4 levels)
-- [ ] Proper error handling
-- [ ] No hardcoded values (use constants or config)
-- [ ] No mutation (immutable patterns used)