oh-my-customcode 0.1.3 → 0.2.0

package/templates/agents/manager/supplier/refs/skills/infrastructure/aws-best-practices/SKILL.md

@@ -1,279 +0,0 @@
-# AWS Best Practices Skill
-
-> **Category**: Infrastructure
-> **Source**: Internal (based on AWS Well-Architected Framework)
-
-## Purpose
-
-Apply AWS patterns for building scalable, secure, and cost-effective cloud infrastructure.
-
-## Well-Architected Framework Pillars
-
-### 1. Operational Excellence
-
-```yaml
-principles:
-  - Perform operations as code
-  - Make frequent, small, reversible changes
-  - Refine operations procedures frequently
-  - Anticipate failure
-  - Learn from all operational failures
-
-practices:
-  - Use CloudFormation/CDK for IaC
-  - Implement CI/CD pipelines
-  - Use CloudWatch for monitoring
-  - Set up alarms and dashboards
-  - Document runbooks
-```
-
-### 2. Security
-
-```yaml
-principles:
-  - Implement strong identity foundation
-  - Enable traceability
-  - Apply security at all layers
-  - Automate security best practices
-  - Protect data in transit and at rest
-  - Keep people away from data
-  - Prepare for security events
-
-iam:
-  - Use least privilege principle
-  - Never use root account for daily tasks
-  - Enable MFA for all users
-  - Use IAM roles for services
-  - Rotate credentials regularly
-
-patterns: |
-  # IAM Policy - Least Privilege
-  {
-    "Version": "2012-10-17",
-    "Statement": [{
-      "Effect": "Allow",
-      "Action": [
-        "s3:GetObject",
-        "s3:PutObject"
-      ],
-      "Resource": "arn:aws:s3:::my-bucket/*",
-      "Condition": {
-        "IpAddress": {
-          "aws:SourceIp": "10.0.0.0/8"
-        }
-      }
-    }]
-  }
-```
-
-### 3. Reliability
-
-```yaml
-principles:
-  - Automatically recover from failure
-  - Test recovery procedures
-  - Scale horizontally
-  - Stop guessing capacity
-  - Manage change through automation
-
-practices:
-  - Multi-AZ deployments
-  - Auto Scaling groups
-  - Health checks and self-healing
-  - Backup and disaster recovery
-  - Loose coupling with queues
-
-patterns:
-  high_availability: |
-    # Multi-AZ RDS
-    - Primary in us-east-1a
-    - Standby in us-east-1b
-    - Read replicas in us-east-1c
-
-  auto_scaling: |
-    # Target tracking scaling
-    - Metric: CPUUtilization
-    - Target: 70%
-    - Min: 2, Max: 10
-```
-
-### 4. Performance Efficiency
-
-```yaml
-principles:
-  - Democratize advanced technologies
-  - Go global in minutes
-  - Use serverless architectures
-  - Experiment more often
-  - Consider mechanical sympathy
-
-compute:
-  - Right-size instances
-  - Use Spot for fault-tolerant workloads
-  - Consider Graviton (ARM) processors
-  - Containerize with ECS/EKS
-
-storage:
-  - Use appropriate storage class
-  - S3 Intelligent-Tiering for variable access
-  - EBS volume types based on IOPS needs
-
-database:
-  - Aurora for MySQL/PostgreSQL
-  - DynamoDB for key-value/document
-  - ElastiCache for caching
-```
-
-### 5. Cost Optimization
-
-```yaml
-principles:
-  - Implement cloud financial management
-  - Adopt consumption model
-  - Measure overall efficiency
-  - Stop spending on undifferentiated heavy lifting
-  - Analyze and attribute expenditure
-
-practices:
-  - Use Reserved Instances/Savings Plans
-  - Right-size resources
-  - Delete unused resources
-  - Use Spot Instances
-  - Implement auto scaling
-
-tools:
-  - AWS Cost Explorer
-  - AWS Budgets
-  - AWS Trusted Advisor
-  - Cost Allocation Tags
-```
-
-### 6. Sustainability
-
-```yaml
-principles:
-  - Understand your impact
-  - Establish sustainability goals
-  - Maximize utilization
-  - Anticipate and adopt more efficient offerings
-  - Use managed services
-  - Reduce downstream impact
-
-practices:
-  - Use efficient instance types (Graviton)
-  - Optimize storage lifecycle
-  - Use serverless where possible
-  - Select regions with lower carbon intensity
-```
-
-## Common Patterns
-
-### VPC Design
-
-```yaml
-pattern: |
-  VPC (10.0.0.0/16)
-  ├── Public Subnets
-  │   ├── us-east-1a: 10.0.1.0/24
-  │   ├── us-east-1b: 10.0.2.0/24
-  │   └── us-east-1c: 10.0.3.0/24
-  ├── Private Subnets (App)
-  │   ├── us-east-1a: 10.0.11.0/24
-  │   ├── us-east-1b: 10.0.12.0/24
-  │   └── us-east-1c: 10.0.13.0/24
-  └── Private Subnets (Data)
-      ├── us-east-1a: 10.0.21.0/24
-      ├── us-east-1b: 10.0.22.0/24
-      └── us-east-1c: 10.0.23.0/24
-
-components:
-  - Internet Gateway (public access)
-  - NAT Gateway (private outbound)
-  - VPC Endpoints (AWS services)
-  - Network ACLs (subnet level)
-  - Security Groups (instance level)
-```
-
-### Three-Tier Architecture
-
-```yaml
-pattern: |
-  [Internet]
-      │
-  [CloudFront]
-      │
-  [ALB] ← Public Subnet
-      │
-  [ECS/EC2] ← Private Subnet (App)
-      │
-  [RDS Multi-AZ] ← Private Subnet (Data)
-
-components:
-  web_tier:
-    - CloudFront for CDN
-    - WAF for protection
-    - ALB for load balancing
-
-  app_tier:
-    - ECS Fargate or EC2
-    - Auto Scaling
-    - ElastiCache
-
-  data_tier:
-    - RDS Multi-AZ
-    - Read Replicas
-    - Automated backups
-```
-
-### Serverless Pattern
-
-```yaml
-pattern: |
-  [API Gateway]
-      │
-  [Lambda] → [DynamoDB]
-      │
-  [SQS] → [Lambda] → [S3]
-
-components:
-  - API Gateway for REST/HTTP APIs
-  - Lambda for compute
-  - DynamoDB for NoSQL
-  - SQS for decoupling
-  - S3 for storage
-  - Step Functions for orchestration
-```
-
-### CI/CD Pipeline
-
-```yaml
-pattern: |
-  [CodeCommit/GitHub]
-      │
-  [CodePipeline]
-      │
-  ├── [CodeBuild] - Build & Test
-  │
-  ├── [ECR] - Container Registry
-  │
-  └── [CodeDeploy/ECS] - Deploy
-
-practices:
-  - Blue/Green deployments
-  - Canary releases
-  - Automated rollback
-  - Infrastructure as Code
-```
-
-## Application
-
-When designing AWS architecture:
-
-1. **Always** follow least privilege for IAM
-2. **Always** use Multi-AZ for production
-3. **Always** encrypt data at rest and in transit
-4. **Prefer** managed services over self-managed
-5. **Implement** monitoring and alerting
-6. **Use** IaC for all infrastructure
-7. **Design** for failure
-8. **Optimize** costs continuously

package/templates/agents/manager/supplier/refs/skills/infrastructure/aws-best-practices/index.yaml

@@ -1,27 +0,0 @@
-# AWS Best Practices Skill
-
-metadata:
-  name: aws-best-practices
-  category: infrastructure
-  description: AWS patterns from Well-Architected Framework
-
-source:
-  type: internal
-  reference:
-    - https://docs.aws.amazon.com/wellarchitected/latest/framework/welcome.html
-    - https://docs.aws.amazon.com/
-    - https://aws.amazon.com/architecture/
-
-provides:
-  - Well-Architected Framework pillars
-  - Security best practices
-  - Reliability patterns
-  - Performance optimization
-  - Cost optimization
-  - VPC design patterns
-  - Three-tier architecture
-  - Serverless patterns
-  - CI/CD pipelines
-
-used_by:
-  - aws-expert

package/templates/agents/manager/supplier/refs/skills/infrastructure/docker-best-practices/index.yaml

@@ -1,26 +0,0 @@
-# Docker Best Practices Skill
-
-metadata:
-  name: docker-best-practices
-  category: infrastructure
-  description: Docker patterns for optimized containerization
-
-source:
-  type: internal
-  reference:
-    - https://docs.docker.com/
-    - https://docs.docker.com/develop/develop-images/dockerfile_best-practices/
-    - https://docs.docker.com/compose/compose-file/best-practices/
-
-provides:
-  - Layer optimization
-  - Multi-stage builds
-  - Security best practices
-  - Image size reduction
-  - Cache optimization
-  - ENTRYPOINT vs CMD
-  - Health checks
-  - Docker Compose patterns
-
-used_by:
-  - docker-expert

package/templates/agents/manager/supplier/refs/skills/orchestration/intent-detection/SKILL.md

@@ -1,214 +0,0 @@
-# Intent Detection Skill
-
-> **Category**: Orchestration
-> **Source**: Internal
-
-## Purpose
-
-Automatically detect user intent and route to the appropriate agent with full transparency.
-
-## Detection Algorithm
-
-### 1. Input Analysis
-
-```
-User Input: "Go 코드 리뷰해줘"
-            │
-            ▼
-┌─────────────────────────────┐
-│  Tokenize & Extract         │
-├─────────────────────────────┤
-│  Keywords: ["Go"]           │
-│  Actions: ["리뷰"]          │
-│  File refs: []              │
-│  Context: []                │
-└─────────────────────────────┘
-```
-
-### 2. Pattern Matching
-
-Match extracted tokens against agent triggers:
-
-```yaml
-# For each agent in agent-triggers.yaml
-match_score = 0
-
-# Keyword match
-for keyword in user_keywords:
-  if keyword in agent.keywords:
-    match_score += agent.keyword_weight (default: 40)
-
-# Action match
-for action in user_actions:
-  if action in agent.actions:
-    match_score += agent.action_weight (default: 40)
-
-# File pattern match
-for pattern in user_file_refs:
-  if matches(pattern, agent.file_patterns):
-    match_score += agent.file_weight (default: 30)
-
-# Context bonus
-if agent == recent_agent:
-  match_score += context_bonus (default: 10)
-```
-
-### 3. Confidence Calculation
-
-```
-confidence = min(100, match_score)
-```
-
-### 4. Decision
-
-```
-if confidence >= 90:
-    auto_execute()
-elif confidence >= 70:
-    request_confirmation()
-else:
-    list_options()
-```
-
-## Detection Patterns
-
-### Keyword Patterns
-
-```yaml
-# Korean keywords
-korean:
-  - "고" → go
-  - "파이썬" → python
-  - "러스트" → rust
-  - "타입스크립트" → typescript
-
-# Action verbs (Korean)
-actions_kr:
-  - "리뷰" → review
-  - "분석" → analyze
-  - "수정" → fix
-  - "생성" → create
-  - "만들어" → create
-  - "확인" → check
-```
-
-### File Pattern Matching
-
-```yaml
-patterns:
-  go: ["*.go", "go.mod", "go.sum"]
-  python: ["*.py", "requirements.txt", "pyproject.toml", "setup.py"]
-  rust: ["*.rs", "Cargo.toml"]
-  typescript: ["*.ts", "*.tsx", "tsconfig.json"]
-  kotlin: ["*.kt", "*.kts", "build.gradle.kts"]
-```
-
-## Output Format
-
-### High Confidence
-
-```
-[Intent Detected]
-├── Input: "Go 코드 리뷰해줘"
-├── Agent: golang-expert
-├── Confidence: 95%
-└── Reason: "Go" keyword + "리뷰" action
-
-┌─ Agent: golang-expert (sw-engineer)
-└─ Task: Code review
-```
-
-### Medium Confidence
-
-```
-[Intent Detected]
-├── Input: "백엔드 API 확인해줘"
-├── Detected: go-backend-expert (?)
-├── Confidence: 78%
-└── Alternatives available
-
-Select agent:
-  1. go-backend-expert (78%)
-  2. fastapi-expert (72%)
-  3. springboot-expert (68%)
-
-Choice [1-3, or agent name]:
-```
-
-### Override
-
-```
-[Override Detected]
-├── Input: "@python-expert review api.py"
-├── Agent: python-expert (explicit)
-└── Bypassing intent detection
-
-┌─ Agent: python-expert (sw-engineer)
-└─ Task: Review api.py
-```
-
-## Integration
-
-### With Secretary
-
-```
-Secretary uses this skill to:
-1. Parse incoming user requests
-2. Detect intent and select agent
-3. Display reasoning
-4. Handle confirmations
-5. Route to selected agent
-```
-
-### With Agent Triggers
-
-```
-Load triggers from:
-skills/orchestration/intent-detection/patterns/agent-triggers.yaml
-
-Each agent defines:
-- keywords (language names, tech terms)
-- file_patterns (extensions, config files)
-- actions (supported actions)
-- weights (scoring factors)
-```
-
-## Error Handling
-
-### No Match
-
-```
-[Intent Unclear]
-├── Input: "도와줘"
-├── Confidence: < 30%
-└── Too generic to detect intent
-
-How can I help? Please be more specific:
-- What type of task? (review, create, fix, ...)
-- What language/technology? (Go, Python, ...)
-- What file or project?
-```
-
-### Ambiguous Match
-
-```
-[Intent Ambiguous]
-├── Input: "코드 리뷰"
-├── Top matches:
-│   └── All experts: ~50% each
-└── Need file context or language hint
-
-Specify the language or provide a file path.
-```
-
-## Configuration
-
-```yaml
-intent_detection:
-  enabled: true
-  auto_execute_threshold: 90
-  confirm_threshold: 70
-  show_reasoning: true
-  max_alternatives: 3
-  korean_support: true
-```

package/templates/agents/manager/supplier/refs/skills/orchestration/intent-detection/index.yaml

@@ -1,30 +0,0 @@
-# Intent Detection Skill
-
-metadata:
-  name: intent-detection
-  category: orchestration
-  description: Automatically detect user intent and route to appropriate agent
-
-source:
-  type: internal
-
-provides:
-  - Keyword extraction from user input
-  - Action verb detection (Korean + English)
-  - File pattern matching
-  - Agent matching with confidence scores
-  - Transparent reasoning display
-  - Override support (@agent syntax)
-
-patterns:
-  location: ./patterns/agent-triggers.yaml
-
-thresholds:
-  auto_execute: 90
-  confirm: 70
-  unclear: 30
-
-used_by:
-  - secretary
-
-rule: R015