oh-my-customcode 0.6.2 → 0.8.0

package/templates/.claude/skills/dev-lead-routing/SKILL.md

@@ -18,6 +18,9 @@ Routes development tasks to appropriate language and framework expert agents. Th
 | sw-engineer/frontend | fe-vercel-agent, fe-vuejs-agent, fe-svelte-agent | Frontend frameworks |
 | sw-engineer/backend | be-fastapi-expert, be-springboot-expert, be-go-backend-expert, be-nestjs-expert, be-express-expert | Backend frameworks |
 | sw-engineer/tooling | tool-npm-expert, tool-optimizer, tool-bun-expert | Build tools and optimization |
+| sw-engineer/database | db-supabase-expert, db-postgres-expert, db-redis-expert | Database design and optimization |
+| sw-architect | arch-documenter, arch-speckit-agent | Architecture documentation and spec-driven development |
+| infra-engineer | infra-docker-expert, infra-aws-expert | Container and cloud infrastructure |
 
 ## Language/Framework Detection
 
@@ -34,6 +37,11 @@ Routes development tasks to appropriate language and framework expert agents. Th
 | `.js`, `.jsx` (React) | fe-vercel-agent | React/Next.js |
 | `.vue` | fe-vuejs-agent | Vue.js |
 | `.svelte` | fe-svelte-agent | Svelte |
+| `.sql` (PostgreSQL) | db-postgres-expert | PostgreSQL |
+| `.sql` (Supabase) | db-supabase-expert | Supabase PostgreSQL |
+| `Dockerfile`, `*.dockerfile` | infra-docker-expert | Docker |
+| `*.tf`, `*.tfvars` | infra-aws-expert | Terraform/IaC |
+| `*.yaml`, `*.yml` (CloudFormation) | infra-aws-expert | AWS CloudFormation |
 
 ### Keyword Mapping
 
@@ -55,6 +63,13 @@ Routes development tasks to appropriate language and framework expert agents. Th
 | "npm" | tool-npm-expert |
 | "optimize", "bundle" | tool-optimizer |
 | "bun" | tool-bun-expert |
+| "postgres", "postgresql", "pg_stat", "psql" | db-postgres-expert |
+| "redis", "cache", "pub/sub", "sorted set" | db-redis-expert |
+| "supabase", "rls", "edge function" | db-supabase-expert |
+| "docker", "dockerfile", "container", "compose" | infra-docker-expert |
+| "aws", "cloudformation", "cdk", "terraform", "vpc", "iam", "s3", "lambda" | infra-aws-expert |
+| "architecture", "adr", "openapi", "swagger", "diagram" | arch-documenter |
+| "spec", "specification", "tdd", "requirements" | arch-speckit-agent |
 
 ## Command Routing
 

package/templates/.claude/skills/kafka-best-practices/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: kafka-best-practices
+description: Apache Kafka best practices for event streaming, topic design, and producer-consumer patterns
+user-invocable: false
+---
+
+# Apache Kafka Best Practices
+
+## Producer Patterns
+
+### Idempotent Producer (CRITICAL)
+- Enable `enable.idempotence=true`
+- Prevents duplicate messages
+- Requires `acks=all`, `retries > 0`, `max.in.flight.requests.per.connection <= 5`
+
+### Exactly-Once Semantics
+- Use transactional API: `initTransactions()`, `beginTransaction()`, `commitTransaction()`
+- For exactly-once end-to-end processing
+
+### Performance
+- Batching: `linger.ms` (wait for batch to fill)
+- Compression: `compression.type=snappy` or `lz4`
+- `batch.size`: 16KB default, tune based on message size
+
+## Consumer Patterns
+
+### Offset Management
+- Auto-commit: `enable.auto.commit=true` (at-least-once)
+- Manual commit: `commitSync()` or `commitAsync()` (better control)
+
+### Rebalancing
+- Cooperative sticky assignor: minimal rebalancing disruption
+- `session.timeout.ms` and `heartbeat.interval.ms` tuning
+
+### At-Least-Once vs Exactly-Once
+- At-least-once: default, idempotent processing required
+- Exactly-once: transactional consumer + producer
+
+## Topic Design
+
+### Partitioning
+- Partition count: based on throughput (MB/s ÷ partition throughput)
+- Key-based partitioning for ordering guarantees
+- More partitions = higher throughput (but more overhead)
+
+### Retention
+- Time-based: `retention.ms`
+- Size-based: `retention.bytes`
+- Log compaction: for changelog topics (`cleanup.policy=compact`)
+
+## References
+- [Kafka Documentation](https://kafka.apache.org/documentation/)

package/templates/.claude/skills/monitoring-setup/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: monitoring-setup
+description: Enable/disable OpenTelemetry console monitoring for Claude Code usage tracking
+argument-hint: "[enable|disable|status]"
+---
+
+# Monitoring Setup Skill
+
+Enable or disable OpenTelemetry console monitoring. When enabled, Claude Code outputs usage metrics (cost, tokens, sessions, LOC, commits, PRs, active time) and events (tool results, API requests) to the terminal.
+
+## Natural Language Triggers
+
+This skill activates when the user mentions any of:
+- Korean: "모니터링", "텔레메트리", "사용량 추적", "메트릭", "모니터링 켜줘", "텔레메트리 활성화"
+- English: "monitoring", "telemetry", "usage tracking", "metrics", "enable monitoring"
+- Combined with actions: "켜", "끄", "활성화", "비활성화", "설정", "enable", "disable", "setup"
+
+## Commands
+
+### enable (default)
+
+1. Read `.claude/settings.local.json` (create if not exists)
+2. Add or update `env` field with:
+   ```json
+   {
+     "env": {
+       "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
+       "OTEL_METRICS_EXPORTER": "console",
+       "OTEL_LOGS_EXPORTER": "console"
+     }
+   }
+   ```
+3. Preserve all existing settings
+4. Report to user:
+   ```
+   [Done] OpenTelemetry Console Monitoring enabled
+
+   Configured in: .claude/settings.local.json
+   Metrics: sessions, cost, tokens, LOC, commits, PRs, active time
+   Events: tool results, API requests, tool decisions
+
+   Note: Takes effect on next `claude` session restart.
+   To disable: /monitoring-setup disable
+   ```
+
+### disable
+
+1. Read `.claude/settings.local.json`
+2. Remove OTel-related keys from `env`:
+   - `CLAUDE_CODE_ENABLE_TELEMETRY`
+   - `OTEL_METRICS_EXPORTER`
+   - `OTEL_LOGS_EXPORTER`
+3. If `env` object becomes empty, remove `env` field entirely
+4. Report:
+   ```
+   [Done] OpenTelemetry Monitoring disabled
+
+   Removed from: .claude/settings.local.json
+   Takes effect on next session restart.
+   ```
+
+### status
+
+1. Read `.claude/settings.local.json`
+2. Check for OTel env vars
+3. Report current state:
+   ```
+   [Monitoring Status]
+   ├── Enabled: Yes/No
+   ├── Metrics exporter: console / otlp / none
+   ├── Logs exporter: console / otlp / none
+   └── Config: .claude/settings.local.json
+   ```
+
+## Implementation Notes
+
+- `settings.local.json` is NOT git-tracked (local to user)
+- Each user enables monitoring independently
+- No infrastructure required for console mode
+- Metrics appear in stderr during Claude Code execution
+- Default export interval: 60s for metrics, 5s for events
+
+## Available Metrics
+
+| Metric | Description | Unit |
+|--------|-------------|------|
+| `claude_code.session.count` | CLI sessions started | count |
+| `claude_code.cost.usage` | Session cost | USD |
+| `claude_code.token.usage` | Tokens used (input/output/cache) | tokens |
+| `claude_code.lines_of_code.count` | Code lines modified (added/removed) | count |
+| `claude_code.commit.count` | Git commits created | count |
+| `claude_code.pull_request.count` | Pull requests created | count |
+| `claude_code.active_time.total` | Active usage time | seconds |
+
+## Available Events
+
+| Event | Description |
+|-------|-------------|
+| `claude_code.tool_result` | Tool execution results with duration |
+| `claude_code.api_request` | API request details with cost/tokens |
+| `claude_code.api_error` | API error details |
+| `claude_code.tool_decision` | Tool accept/reject decisions |
+| `claude_code.user_prompt` | User prompt metadata (content redacted by default) |
+
+## Upgrade Path
+
+For production monitoring, upgrade from console to OTLP:
+
+```bash
+# In settings.local.json env:
+OTEL_METRICS_EXPORTER=otlp
+OTEL_LOGS_EXPORTER=otlp
+OTEL_EXPORTER_OTLP_PROTOCOL=grpc
+OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317
+```

package/templates/.claude/skills/pipeline-architecture-patterns/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: pipeline-architecture-patterns
+description: Data pipeline architecture patterns for ETL/ELT design, orchestration, and data quality frameworks
+user-invocable: false
+---
+
+# Data Pipeline Architecture Patterns
+
+## Pipeline Architectures
+
+### ETL vs ELT (CRITICAL)
+- **ETL**: Extract → Transform (staging) → Load
+  - Traditional, on-premise data warehouses
+  - Pre-aggregation, complex transformations
+- **ELT**: Extract → Load (raw) → Transform (in warehouse)
+  - Cloud warehouses (Snowflake, BigQuery)
+  - Leverage warehouse compute power
+
+### Lambda Architecture
+- Batch layer: historical data processing
+- Speed layer: real-time stream processing
+- Serving layer: merge batch + real-time views
+- Complexity: maintain two codebases
+
+### Kappa Architecture
+- Stream-only processing
+- Single codebase for batch + real-time
+- Reprocessing via replay
+- Simpler than Lambda
+
+### Medallion Architecture
+- **Bronze**: Raw data (append-only)
+- **Silver**: Cleaned, conformed data
+- **Gold**: Business-level aggregations
+- Databricks pattern
+
+## Orchestration Patterns
+
+### DAG-Based Orchestration
+- Airflow, Prefect, Dagster
+- Task dependencies as DAG
+- Retries, backfills, scheduling
+
+### Event-Driven Orchestration
+- Kafka, Pub/Sub triggers
+- Real-time, low-latency
+- Decoupled producers/consumers
+
+### Hybrid Orchestration
+- Scheduled batch + event-driven streams
+- Example: Airflow DAG triggered by Kafka event
+
+## Data Quality Frameworks
+
+### Data Contracts (CRITICAL)
+- Define schema, freshness, volume expectations
+- Producer-consumer agreement
+- Break build on violation
+
+### Validation Frameworks
+- **Great Expectations**: Python-based expectations
+- **dbt tests**: SQL-based tests
+- **Soda**: YAML-based checks
+
+### Data Lineage
+- Track data origin and transformations
+- Debug data quality issues
+- Compliance and auditing
+
+## Idempotency Patterns
+
+### Idempotent Design (CRITICAL)
+- Same input → same output (no side effects)
+- Upserts instead of inserts
+- Partition replacement instead of append
+
+### Deduplication
+- Use unique keys
+- Window-based deduplication
+- Consumer group offset management
+
+## References
+- [Data Engineering Design Patterns](https://www.oreilly.com/library/view/data-engineering-design/9781098130725/)

package/templates/.claude/skills/postgres-best-practices/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: postgres-best-practices
+description: PostgreSQL best practices for database design, query optimization, and performance tuning
+user-invocable: false
+---
+
+# PostgreSQL Best Practices
+
+## Query Optimization
+
+### EXPLAIN ANALYZE (CRITICAL)
+- Use `EXPLAIN ANALYZE` to understand query plans
+- Identify slow operations: Seq Scan, Nested Loop
+- Check row estimates vs actual rows
+- Monitor buffers: shared hit vs read
+
+### Indexing (CRITICAL)
+- B-tree: default, most use cases
+- GIN: JSONB, arrays, full-text search
+- GiST: geometry, range types
+- BRIN: large sequential tables (time-series)
+- Partial indexes: filtered queries
+- Covering indexes (INCLUDE): avoid heap fetches
+
+### Index Maintenance
+- Create indexes concurrently: `CREATE INDEX CONCURRENTLY`
+- Monitor usage: `pg_stat_user_indexes`
+- Remove unused indexes
+- Reindex bloated indexes
+
+## Table Design
+
+### Partitioning (HIGH)
+- Range partitioning: time-series data
+- List partitioning: categorical data
+- Hash partitioning: even distribution
+- Declarative partitioning (PG 10+)
+
+### Data Types
+- Use appropriate types (int vs bigint, varchar vs text)
+- JSONB for semi-structured data
+- Arrays for multi-value columns
+- UUIDs for distributed IDs
+
+## Performance Tuning
+
+### Vacuum and Autovacuum
+- Autovacuum: default enabled
+- Monitor bloat: `pg_stat_user_tables`
+- Tune autovacuum thresholds
+- Manual VACUUM for large updates
+
+### Connection Pooling
+- Use pgBouncer or PgPool
+- Transaction pooling for short transactions
+- Session pooling for long transactions
+- Max connections: tune based on workload
+
+### Configuration
+- `shared_buffers`: 25% of RAM
+- `work_mem`: per operation, tune carefully
+- `effective_cache_size`: 50-75% of RAM
+- `random_page_cost`: 1.1 for SSD
+
+## References
+- [PostgreSQL Performance Optimization](https://wiki.postgresql.org/wiki/Performance_Optimization)

package/templates/.claude/skills/redis-best-practices/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: redis-best-practices
+description: Redis best practices for caching, data structures, and in-memory data architecture
+user-invocable: false
+---
+
+# Redis Best Practices
+
+## Caching Patterns
+
+### Cache-Aside (CRITICAL)
+- Read: check cache → miss → read DB → set cache
+- Write: update DB → invalidate cache
+- Best for read-heavy workloads
+
+### Write-Through
+- Write: update cache AND DB simultaneously
+- Ensures consistency
+- Higher write latency
+
+### Write-Behind
+- Write: update cache → async DB update
+- Lowest latency
+- Risk of data loss
+
+## Data Structures
+
+### String
+- Simple key-value: `SET key value`
+- Counters: `INCR`, `DECR`, `INCRBY`
+- Bit operations: `SETBIT`, `BITCOUNT`
+
+### Hash
+- Object storage: `HSET user:1 name "Alice"`
+- Partial updates: `HINCRBY user:1 visits 1`
+- Memory efficient for small hashes
+
+### List
+- Queues: `LPUSH`, `RPOP` (FIFO)
+- Stacks: `LPUSH`, `LPOP` (LIFO)
+- Capped collections: `LTRIM`
+
+### Set
+- Unique collections: `SADD`, `SMEMBERS`
+- Intersections: `SINTER`
+- Random sampling: `SRANDMEMBER`
+
+### Sorted Set
+- Leaderboards: `ZADD`, `ZRANGEBYSCORE`
+- Rate limiting: `ZADD timestamp`
+- Priority queues
+
+### Stream
+- Event log: `XADD`, `XREAD`
+- Consumer groups: `XGROUP`, `XACK`
+- Pub/Sub with persistence
+
+## Performance
+
+### Memory Optimization
+- Set maxmemory policy: `allkeys-lru`, `volatile-lru`
+- Monitor memory: `INFO memory`
+- Use appropriate data structures (Hash vs String)
+
+### Pipelining
+- Batch multiple commands
+- Reduces round-trip latency
+- Use for bulk operations
+
+## High Availability
+
+### Redis Cluster
+- Horizontal scaling
+- Automatic sharding (16384 slots)
+- Multi-master replication
+
+### Redis Sentinel
+- Automatic failover
+- Monitoring and notifications
+- Configuration provider
+
+## References
+- [Redis Best Practices](https://redis.io/docs/manual/patterns/)

package/templates/.claude/skills/secretary-routing/SKILL.md

@@ -20,6 +20,9 @@ Routes agent management tasks to the appropriate manager agent. This skill conta
 | mgr-gitnerd | Git operations | "commit", "push", "pr" |
 | mgr-sync-checker | Sync verification | "sync check", "verify sync" |
 | mgr-sauron | R017 auto-verification | "verify", "full check" |
+| mgr-claude-code-bible | Claude Code spec compliance | "spec check", "verify compliance" |
+| sys-memory-keeper | Memory operations | "save memory", "recall", "memory search" |
+| sys-naggy | TODO management | "todo", "track tasks", "task list" |
 
 ## Command Routing
 
@@ -32,6 +35,9 @@ audit    → mgr-supplier
 git      → mgr-gitnerd
 sync     → mgr-sync-checker
 verify   → mgr-sauron
+spec     → mgr-claude-code-bible
+memory   → sys-memory-keeper
+todo     → sys-naggy
 batch    → multiple (parallel)
 ```
 
@@ -48,6 +54,9 @@ batch    → multiple (parallel)
    - "git commit/push/pr" → mgr-gitnerd
    - "sync check" → mgr-sync-checker
    - "verify" → mgr-sauron
+   - "spec check" → mgr-claude-code-bible
+   - "save/recall memory" → sys-memory-keeper
+   - "todo/task list" → sys-naggy
 3. Spawn Task with selected agent role
 4. Monitor execution
 5. Report result to user
@@ -92,6 +101,9 @@ Use Task tool's `model` parameter to optimize cost and performance:
 | mgr-gitnerd | `sonnet` | Commit message quality |
 | mgr-sync-checker | `haiku` | Fast verification |
 | mgr-sauron | `sonnet` | Multi-round verification |
+| mgr-claude-code-bible | `sonnet` | Spec compliance checks |
+| sys-memory-keeper | `sonnet` | Memory operations, search |
+| sys-naggy | `haiku` | Simple TODO tracking |
 
 ### Task Call Examples
 

package/templates/.claude/skills/snowflake-best-practices/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: snowflake-best-practices
+description: Snowflake best practices for cloud data warehouse design, query optimization, and cost management
+user-invocable: false
+---
+
+# Snowflake Best Practices
+
+## Warehouse Design
+
+### Sizing (CRITICAL)
+- Start small (XS or S), scale up as needed
+- Enable auto-scaling for concurrency
+- Enable auto-suspend (1 minute idle)
+- Separate warehouses for different workloads
+
+### Multi-Cluster Warehouses
+- Use for high concurrency (many users)
+- Set min/max clusters based on load
+- Scaling policy: Standard (default) or Economy
+
+## Query Optimization
+
+### Clustering Keys (CRITICAL)
+- Define clustering keys for frequently filtered columns
+- Improves micro-partition pruning
+- Monitor clustering depth
+- Automatic clustering: `ALTER TABLE ... CLUSTER BY (...)`
+
+### Result Caching
+- 24-hour cache for identical queries
+- Use SHOW PARAMETERS to check cache status
+- Bypass cache with query hint: `/*+ NO_RESULT_CACHE */`
+
+### Materialized Views
+- For repeated aggregations
+- Automatically refreshed on base table changes
+- Cost: storage + refresh compute
+
+## Data Loading
+
+### COPY INTO (CRITICAL)
+- Batch load from stages (S3/GCS/Azure)
+- File size: 100-250MB compressed (optimal)
+- Use pattern matching for multiple files
+
+### Snowpipe
+- Continuous ingestion
+- Event-driven (S3 notifications)
+- Serverless compute
+
+## Cost Optimization
+
+### Resource Monitors
+- Set credit quotas per warehouse
+- Alerts and suspend actions
+- Track consumption with WAREHOUSE_METERING_HISTORY
+
+### Storage
+- Use zero-copy cloning for dev/test
+- Time travel retention: 1 day (standard), 90 days (enterprise)
+- Fail-safe: 7 days (not configurable)
+
+## References
+- [Snowflake Best Practices](https://docs.snowflake.com/en/user-guide/best-practices)

package/templates/.claude/skills/spark-best-practices/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: spark-best-practices
+description: Apache Spark best practices for PySpark and Scala distributed data processing
+user-invocable: false
+---
+
+# Apache Spark Best Practices
+
+## Performance Optimization
+
+### Broadcast Joins (CRITICAL)
+- Use `broadcast(small_df)` for small-large table joins
+- Default broadcast threshold: 10MB (`spark.sql.autoBroadcastJoinThreshold`)
+- Avoid broadcast for tables > 100MB
+
+### Shuffles (CRITICAL)
+- Minimize shuffles: expensive operations
+- Use `coalesce()` to reduce partitions without shuffle
+- Use `repartition()` only when necessary (causes shuffle)
+- Predicate pushdown: filter before joins
+
+### Caching
+- Cache DataFrames used multiple times: `df.cache()` or `df.persist()`
+- Choose storage level: MEMORY_ONLY, MEMORY_AND_DISK, DISK_ONLY
+- Unpersist when done: `df.unpersist()`
+
+## Resource Management
+
+### Executor Configuration
+- Executor memory: 80% of available memory per executor
+- Executor cores: 4-5 cores per executor (optimal)
+- Dynamic allocation: enable for varying workloads
+
+### Partitioning
+- Optimal partition size: 100-200MB
+- Too few partitions: underutilized cluster
+- Too many partitions: task overhead
+
+## Data Processing
+
+### UDFs
+- Prefer built-in functions over UDFs
+- Use Pandas UDF for vectorized operations
+- Avoid Python UDFs (serialization overhead)
+
+### Storage Formats
+- Parquet: default for analytics (columnar, compression)
+- ORC: alternative to Parquet
+- Delta/Iceberg: ACID transactions, time travel
+
+## References
+- [Spark Performance Tuning](https://spark.apache.org/docs/latest/tuning.html)

package/templates/CLAUDE.md.en

@@ -151,6 +151,7 @@ Flow:
 | `/dev-refactor` | Refactor code |
 | `/memory-save` | Save session context to claude-mem |
 | `/memory-recall` | Search and recall memories |
+| `/monitoring-setup` | Enable/disable OTel console monitoring |
 | `/npm-publish` | Publish package to npm registry |
 | `/npm-version` | Manage semantic versions |
 | `/npm-audit` | Audit dependencies |
@@ -168,12 +169,12 @@ Flow:
 project/
 +-- CLAUDE.md                    # Entry point
 +-- .claude/
-|   +-- agents/                  # Subagent definitions (34 files)
-|   +-- skills/                  # Skills (41 directories)
+|   +-- agents/                  # Subagent definitions (42 files)
+|   +-- skills/                  # Skills (51 directories)
 |   +-- rules/                   # Global rules (R000-R018)
 |   +-- hooks/                   # Hook scripts (memory, HUD)
 |   +-- contexts/                # Context files (ecomode)
-+-- guides/                      # Reference docs (13 topics)
++-- guides/                      # Reference docs (22 topics)
 ```
 
 ## Orchestration
@@ -181,6 +182,7 @@ project/
 Orchestration is handled by routing skills in the main conversation:
 - **secretary-routing**: Routes management tasks to manager agents
 - **dev-lead-routing**: Routes development tasks to language/framework experts
+- **de-lead-routing**: Routes data engineering tasks to DE/pipeline experts
 - **qa-lead-routing**: Coordinates QA workflow
 
 The main conversation acts as the sole orchestrator. Subagents cannot spawn other subagents.
@@ -193,13 +195,14 @@ The main conversation acts as the sole orchestrator. Subagents cannot spawn othe
 | SW Engineer/Backend | 5 | be-fastapi-expert, be-springboot-expert, be-go-backend-expert, be-express-expert, be-nestjs-expert |
 | SW Engineer/Frontend | 3 | fe-vercel-agent, fe-vuejs-agent, fe-svelte-agent |
 | SW Engineer/Tooling | 3 | tool-npm-expert, tool-optimizer, tool-bun-expert |
-| SW Engineer/Database | 1 | db-supabase-expert |
+| DE Engineer | 6 | de-airflow-expert, de-dbt-expert, de-spark-expert, de-kafka-expert, de-snowflake-expert, de-pipeline-expert |
+| SW Engineer/Database | 3 | db-supabase-expert, db-postgres-expert, db-redis-expert |
 | SW Architect | 2 | arch-documenter, arch-speckit-agent |
 | Infra Engineer | 2 | infra-docker-expert, infra-aws-expert |
 | QA Team | 3 | qa-planner, qa-writer, qa-engineer |
 | Manager | 7 | mgr-creator, mgr-updater, mgr-supplier, mgr-gitnerd, mgr-sync-checker, mgr-sauron, mgr-claude-code-bible |
 | System | 2 | sys-memory-keeper, sys-naggy |
-| **Total** | **34** | |
+| **Total** | **42** | |
 
 ## Agent Teams
 

package/templates/CLAUDE.md.ko

@@ -151,6 +151,7 @@ oh-my-customcode로 구동됩니다.
 | `/dev-refactor` | 코드 리팩토링 |
 | `/memory-save` | 세션 컨텍스트를 claude-mem에 저장 |
 | `/memory-recall` | 메모리 검색 및 리콜 |
+| `/monitoring-setup` | OTel 콘솔 모니터링 활성화/비활성화 |
 | `/npm-publish` | npm 레지스트리에 패키지 배포 |
 | `/npm-version` | 시맨틱 버전 관리 |
 | `/npm-audit` | 의존성 감사 |
@@ -168,12 +169,12 @@ oh-my-customcode로 구동됩니다.
 project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
-|   +-- agents/                  # 서브에이전트 정의 (34 파일)
-|   +-- skills/                  # 스킬 (41 디렉토리)
+|   +-- agents/                  # 서브에이전트 정의 (42 파일)
+|   +-- skills/                  # 스킬 (51 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R018)
 |   +-- hooks/                   # 훅 스크립트 (메모리, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
-+-- guides/                      # 레퍼런스 문서 (13 토픽)
++-- guides/                      # 레퍼런스 문서 (22 토픽)
 ```
 
 ## 오케스트레이션
@@ -181,6 +182,7 @@ project/
 오케스트레이션은 메인 대화의 라우팅 스킬로 처리됩니다:
 - **secretary-routing**: 매니저 에이전트로 관리 작업 라우팅
 - **dev-lead-routing**: 언어/프레임워크 전문가에게 개발 작업 라우팅
+- **de-lead-routing**: 데이터 엔지니어링 작업을 DE/파이프라인 전문가에게 라우팅
 - **qa-lead-routing**: QA 워크플로우 조율
 
 메인 대화가 유일한 오케스트레이터 역할을 합니다. 서브에이전트는 다른 서브에이전트를 생성할 수 없습니다.
@@ -193,13 +195,14 @@ project/
 | SW Engineer/Backend | 5 | be-fastapi-expert, be-springboot-expert, be-go-backend-expert, be-express-expert, be-nestjs-expert |
 | SW Engineer/Frontend | 3 | fe-vercel-agent, fe-vuejs-agent, fe-svelte-agent |
 | SW Engineer/Tooling | 3 | tool-npm-expert, tool-optimizer, tool-bun-expert |
-| SW Engineer/Database | 1 | db-supabase-expert |
+| DE Engineer | 6 | de-airflow-expert, de-dbt-expert, de-spark-expert, de-kafka-expert, de-snowflake-expert, de-pipeline-expert |
+| SW Engineer/Database | 3 | db-supabase-expert, db-postgres-expert, db-redis-expert |
 | SW Architect | 2 | arch-documenter, arch-speckit-agent |
 | Infra Engineer | 2 | infra-docker-expert, infra-aws-expert |
 | QA Team | 3 | qa-planner, qa-writer, qa-engineer |
 | Manager | 7 | mgr-creator, mgr-updater, mgr-supplier, mgr-gitnerd, mgr-sync-checker, mgr-sauron, mgr-claude-code-bible |
 | System | 2 | sys-memory-keeper, sys-naggy |
-| **총계** | **34** | |
+| **총계** | **42** | |
 
 ## Agent Teams