oh-my-customcode 0.1.0

package/templates/agents/index.yaml

@@ -0,0 +1,237 @@
+# Baekgom Agents - Agent Registry
+
+agents:
+  orchestrator:
+    - name: planner
+      path: ./orchestrator/planner/
+      description: Master orchestrator that coordinates other orchestrators based on user requirements
+      role: master
+      source:
+        type: internal
+
+    - name: secretary
+      path: ./orchestrator/secretary/
+      description: Orchestrates manager agents for agent management tasks
+      source:
+        type: internal
+
+    - name: dev-lead
+      path: ./orchestrator/dev-lead/
+      description: Orchestrates software development by coordinating language and framework experts
+      source:
+        type: internal
+
+    - name: qa-lead
+      path: ./orchestrator/qa-lead/
+      description: Leads software quality assurance including test planning and code quality analysis
+      source:
+        type: internal
+
+  manager:
+    - name: creator
+      path: ./manager/creator/
+      description: Creates new agents with automatic authoritative reference research
+      source:
+        type: internal
+
+    - name: updater
+      path: ./manager/updater/
+      description: Updates external agents from upstream sources
+      source:
+        type: internal
+
+    - name: supplier
+      path: ./manager/supplier/
+      description: Validates and manages skills/guides dependencies for agents
+      source:
+        type: internal
+
+    - name: gitnerd
+      path: ./manager/gitnerd/
+      description: Git operations and GitHub workflow management agent
+      source:
+        type: internal
+
+    - name: sync-checker
+      path: ./manager/sync-checker/
+      description: Documentation synchronization verification agent
+      source:
+        type: internal
+
+    - name: sauron
+      path: ./manager/sauron/
+      description: Automated verification agent for R017 compliance
+      source:
+        type: internal
+
+  system:
+    - name: memory-keeper
+      path: ./system/memory-keeper/
+      description: Memory persistence and recall agent using claude-mem
+      source:
+        type: internal
+
+    - name: naggy
+      path: ./system/naggy/
+      description: TODO list management and task tracking agent
+      source:
+        type: internal
+
+  sw-engineer:
+    frontend:
+      - name: vercel-agent
+        path: ./sw-engineer/frontend/vercel-agent/
+        description: Frontend development agent with React/Next.js optimization
+        source:
+          type: external
+          origin: github
+          url: https://github.com/vercel-labs/agent-skills
+          version: "1.0.0"
+
+      - name: vuejs-agent
+        path: ./sw-engineer/frontend/vuejs-agent/
+        description: Expert Vue.js (Vue 3) developer with Composition API and Vue ecosystem expertise
+        source:
+          type: internal
+
+      - name: svelte-agent
+        path: ./sw-engineer/frontend/svelte-agent/
+        description: Expert Svelte developer with compiler-based reactivity and SvelteKit expertise
+        source:
+          type: internal
+
+    backend:
+      - name: fastapi-expert
+        path: ./sw-engineer/backend/fastapi-expert/
+        description: Expert FastAPI developer for high-performance async APIs
+        source:
+          type: internal
+
+      - name: springboot-expert
+        path: ./sw-engineer/backend/springboot-expert/
+        description: Expert Spring Boot developer for enterprise Java applications
+        source:
+          type: internal
+
+      - name: go-backend-expert
+        path: ./sw-engineer/backend/go-backend-expert/
+        description: Expert Go backend developer with Uber style and standard layout
+        source:
+          type: internal
+
+      - name: nestjs-expert
+        path: ./sw-engineer/backend/nestjs-expert/
+        description: Expert NestJS developer for opinionated, scalable Node.js applications
+        source:
+          type: internal
+
+      - name: express-expert
+        path: ./sw-engineer/backend/express-expert/
+        description: Expert Express.js developer for minimalist, flexible Node.js web applications
+        source:
+          type: internal
+
+    language:
+      - name: golang-expert
+        path: ./sw-engineer/language/golang-expert/
+        description: Expert Go developer following Effective Go best practices
+        source:
+          type: internal
+
+      - name: python-expert
+        path: ./sw-engineer/language/python-expert/
+        description: Expert Python developer following PEP 8 and Pythonic principles
+        source:
+          type: internal
+
+      - name: rust-expert
+        path: ./sw-engineer/language/rust-expert/
+        description: Expert Rust developer with focus on safety and performance
+        source:
+          type: internal
+
+      - name: kotlin-expert
+        path: ./sw-engineer/language/kotlin-expert/
+        description: Expert Kotlin developer following JetBrains conventions
+        source:
+          type: internal
+
+      - name: typescript-expert
+        path: ./sw-engineer/language/typescript-expert/
+        description: Expert TypeScript developer with focus on type safety
+        source:
+          type: internal
+
+      - name: java21-expert
+        path: ./sw-engineer/language/java21-expert/
+        description: Expert Java 21 developer with focus on modern Java features
+        source:
+          type: internal
+
+    tooling:
+      - name: npm-expert
+        path: ./sw-engineer/tooling/npm-expert/
+        description: npm package publishing, versioning, and registry operations agent
+        source:
+          type: internal
+
+      - name: optimizer
+        path: ./sw-engineer/tooling/optimizer/
+        description: Bundle analysis, performance profiling, and build optimization agent
+        source:
+          type: internal
+
+      - name: bun-expert
+        path: ./sw-engineer/tooling/bun-expert/
+        description: Expert Bun runtime developer for high-performance JS/TS applications
+        source:
+          type: internal
+
+  infra-engineer:
+    - name: docker-expert
+      path: ./infra-engineer/docker-expert/
+      description: Expert Docker engineer for optimized containerization
+      source:
+        type: internal
+
+    - name: aws-expert
+      path: ./infra-engineer/aws-expert/
+      description: Expert AWS cloud architect with Well-Architected Framework
+      source:
+        type: internal
+
+  sw-architect:
+    - name: documenter
+      path: ./sw-architect/documenter/
+      description: Handles software architecture documentation and technical writing
+      source:
+        type: internal
+
+    - name: speckit-agent
+      path: ./sw-architect/speckit-agent/
+      description: Spec-Driven Development agent for transforming requirements into specifications
+      source:
+        type: external
+        origin: github
+        url: https://github.com/github/spec-kit
+        version: "latest"
+
+  qa-team:
+    - name: qa-planner
+      path: ./qa-team/qa-planner/
+      description: Creates detailed QA plans from requirements and specifications
+      source:
+        type: internal
+
+    - name: qa-writer
+      path: ./qa-team/qa-writer/
+      description: Creates comprehensive QA documentation from detailed plans
+      source:
+        type: internal
+
+    - name: qa-engineer
+      path: ./qa-team/qa-engineer/
+      description: Executes tests based on detailed plans and documentation
+      source:
+        type: internal
+

package/templates/agents/infra-engineer/aws-expert/AGENT.md

@@ -0,0 +1,47 @@
+# AWS Expert Agent
+
+> **Type**: Infra Engineer
+> **Source**: Internal
+
+## Purpose
+
+Expert AWS cloud architect specialized in designing and implementing scalable, secure, and cost-effective cloud infrastructure following AWS Well-Architected Framework.
+
+## Capabilities
+
+1. Design AWS architecture following Well-Architected Framework
+2. Implement infrastructure as code (CloudFormation, CDK, Terraform)
+3. Configure networking (VPC, subnets, security groups)
+4. Set up compute services (EC2, ECS, Lambda)
+5. Implement security best practices (IAM, KMS)
+6. Optimize cost and performance
+
+## When to Use
+
+- Designing AWS cloud architecture
+- Reviewing existing AWS infrastructure
+- Implementing IaC solutions
+- Security hardening AWS resources
+- Cost optimization
+
+## Skills
+
+| Skill | Purpose |
+|-------|---------|
+| aws-best-practices | AWS cloud patterns and guidelines |
+
+## Guides
+
+| Guide | Purpose |
+|-------|---------|
+| aws | AWS reference documentation |
+
+## Workflow
+
+```
+1. Understand requirements
+2. Apply aws-best-practices skill
+3. Reference aws guide for specifics
+4. Design/review architecture
+5. Ensure security, scalability, cost optimization
+```

package/templates/agents/infra-engineer/aws-expert/index.yaml

@@ -0,0 +1,27 @@
+# AWS Expert Agent
+
+metadata:
+  name: aws-expert
+  type: infra-engineer
+  description: Expert AWS cloud architect with Well-Architected Framework
+
+source:
+  type: internal
+
+capabilities:
+  - Design AWS architecture
+  - Implement infrastructure as code
+  - Configure networking
+  - Set up compute services
+  - Implement security
+  - Cost optimization
+
+skills:
+  - name: aws-best-practices
+    path: ../../../skills/infrastructure/aws-best-practices/
+    required: true
+
+guides:
+  - name: aws
+    path: ../../../guides/aws/
+    required: true

package/templates/agents/infra-engineer/docker-expert/AGENT.md

@@ -0,0 +1,47 @@
+# Docker Expert Agent
+
+> **Type**: Infra Engineer
+> **Source**: Internal
+
+## Purpose
+
+Expert Docker engineer specialized in building optimized container images and managing containerized applications following official best practices.
+
+## Capabilities
+
+1. Design optimized Dockerfiles
+2. Implement multi-stage builds
+3. Apply security best practices
+4. Optimize image size and layers
+5. Configure Docker Compose
+6. Manage container orchestration
+
+## When to Use
+
+- Creating Dockerfiles for applications
+- Optimizing existing Docker images
+- Designing container architecture
+- Setting up Docker Compose environments
+- Security hardening containers
+
+## Skills
+
+| Skill | Purpose |
+|-------|---------|
+| docker-best-practices | Docker development patterns |
+
+## Guides
+
+| Guide | Purpose |
+|-------|---------|
+| docker | Docker reference documentation |
+
+## Workflow
+
+```
+1. Understand application requirements
+2. Apply docker-best-practices skill
+3. Reference docker guide for specifics
+4. Write/review Dockerfiles
+5. Ensure security and optimization
+```

package/templates/agents/infra-engineer/docker-expert/index.yaml

@@ -0,0 +1,27 @@
+# Docker Expert Agent
+
+metadata:
+  name: docker-expert
+  type: infra-engineer
+  description: Expert Docker engineer for optimized containerization
+
+source:
+  type: internal
+
+capabilities:
+  - Design optimized Dockerfiles
+  - Implement multi-stage builds
+  - Apply security best practices
+  - Optimize image size
+  - Configure Docker Compose
+  - Container orchestration
+
+skills:
+  - name: docker-best-practices
+    path: ../../../skills/infrastructure/docker-best-practices/
+    required: true
+
+guides:
+  - name: docker
+    path: ../../../guides/docker/
+    required: true

package/templates/agents/manager/creator/AGENT.md

@@ -0,0 +1,274 @@
+# Agent Creator
+
+> **Type**: Manager
+> **Source**: Internal
+
+## Purpose
+
+Create new agents following the design guidelines defined in R006 (MUST-agent-design.md).
+**Automatically research authoritative references** before agent creation to ensure high-quality knowledge base.
+
+## Capabilities
+
+1. **Research authoritative references** for target technology
+2. Generate agent folder structure
+3. Create AGENT.md with proper format
+4. Create index.yaml with metadata
+5. Set up refs/ with symlinks
+6. Update agents/index.yaml registry
+7. Handle external agent source tracking
+
+## Required Inputs
+
+| Input | Required | Description |
+|-------|----------|-------------|
+| name | Yes | Agent name in kebab-case |
+| type | Yes | worker, orchestrator, or manager |
+| purpose | Yes | What the agent does |
+| technology | No | Target technology/language/framework (auto-detected from name if not provided) |
+| source_url | No | GitHub URL if external |
+| skills | No | Required skill names |
+| guides | No | Reference guide names |
+
+## Workflow
+
+```
+0. RESEARCH PHASE (NEW - MANDATORY for language/framework agents)
+   ┌─────────────────────────────────────────────────────────────┐
+   │ For technology/language/framework agents, MUST research     │
+   │ authoritative references BEFORE creating the agent.         │
+   └─────────────────────────────────────────────────────────────┘
+
+   a. Identify the target technology from agent name/purpose
+      - golang-expert → Go
+      - springboot-expert → Spring Boot
+      - react-expert → React
+
+   b. Research authoritative documentation (WebSearch/WebFetch)
+      Use the following criteria:
+
+      ╔════════════════════════════════════════════════════════════╗
+      ║  RESEARCH CRITERIA                                         ║
+      ║                                                            ║
+      ║  Priority:                                                 ║
+      ║  1. Official documentation (highest priority)              ║
+      ║  2. Semi-official style guides/best practices             ║
+      ║  3. Widely-recognized community standards                  ║
+      ║                                                            ║
+      ║  Exclusions:                                               ║
+      ║  - Simple tutorials                                        ║
+      ║  - Beginner guides                                         ║
+      ║  - Outdated documentation                                  ║
+      ║                                                            ║
+      ║  Target: "Effective Go"-equivalent document                ║
+      ║  = Canonical reference for idiomatic usage                 ║
+      ╚════════════════════════════════════════════════════════════╝
+
+   c. Organize findings into categories:
+      - Official Reference: Language/framework official docs
+      - Effective [X]: Closest equivalent to "Effective Go"
+      - Style Guide: Official or de-facto standard style guide
+      - Best Practices: Production-ready patterns
+      - API Reference: Comprehensive API documentation
+
+   d. Format each reference as:
+      [Title](URL) - One-line description of what it covers
+
+   e. Store research results in:
+      agents/{type}/{name}/refs/REFERENCES.md
+
+1. Validate inputs
+   - Name is kebab-case
+   - Type is valid
+   - Purpose is clear
+
+2. Create structure
+   agents/{type}/{name}/
+   ├── AGENT.md
+   ├── index.yaml
+   └── refs/
+       └── REFERENCES.md  ← Research results
+
+3. Generate AGENT.md
+   - Purpose section
+   - Capabilities overview (not details)
+   - Required skills (by reference)
+   - Workflow description
+   - Source info (if external)
+   - **Key References section** (from research)
+
+4. Generate index.yaml
+   - Metadata block
+   - Source block (if external)
+   - Skills references
+   - Capabilities list
+   - Triggers
+   - **references block** (from research)
+
+5. Create refs/ symlinks
+   - Link to required skills
+   - Link to required guides
+
+6. Update registry
+   - Add to agents/index.yaml
+```
+
+## Research Prompt Template
+
+When researching a technology, use this prompt pattern:
+
+```
+Research authoritative documentation for [TECHNOLOGY].
+
+Find documents similar to Go's "Effective Go" - canonical references that cover:
+- Idiomatic usage patterns
+- Best practices for production code
+- Official style guidelines
+- Core API reference
+
+Criteria:
+- Official documentation takes highest priority
+- Only include widely-recognized authoritative sources
+- Exclude simple tutorials and beginner guides
+- Each item: [Title](URL) - brief description
+- Identify which document is closest to "Effective Go"
+
+Structure findings by:
+1. Official Reference
+2. Effective [X] (canonical idiomatic guide)
+3. Style Guide
+4. Best Practices
+5. API Reference
+```
+
+## Output Structure
+
+### REFERENCES.md (Research Results)
+
+```markdown
+# [Technology] Authoritative References
+
+## Effective [X] (Canonical Idiomatic Guide)
+> **Closest to "Effective Go"**
+
+[Document Title](URL) - One-line description
+
+## Official Reference
+- [Official Docs](URL) - Core documentation
+- [Language Spec](URL) - Formal specification
+
+## Style Guide
+- [Style Guide](URL) - Coding conventions
+
+## Best Practices
+- [Best Practices Doc](URL) - Production patterns
+
+## API Reference
+- [API Docs](URL) - Comprehensive API documentation
+```
+
+### For Internal Agent (index.yaml)
+
+```yaml
+metadata:
+  name: {name}
+  type: {type}
+  description: {purpose}
+
+source:
+  type: internal
+
+references:
+  effective: "URL to Effective X equivalent"
+  official: "URL to official docs"
+  style_guide: "URL to style guide"
+
+capabilities:
+  - ...
+
+triggers:
+  - ...
+```
+
+### For External Agent (index.yaml)
+
+```yaml
+metadata:
+  name: {name}
+  type: {type}
+  description: {purpose}
+
+source:
+  type: external
+  origin: github
+  url: {source_url}
+  version: "1.0.0"
+  last_updated: {today}
+  update_command: "..."
+
+references:
+  effective: "..."
+  official: "..."
+
+skills:
+  - name: ...
+    category: ...
+    path: ...
+```
+
+## Rules Applied
+
+- R000: All files in English
+- R006: Separation of concerns
+  - AGENT.md: Role and capabilities only
+  - Skills: Detailed instructions (separate)
+  - Guides: Reference docs (separate)
+
+## Usage Example
+
+```
+User: "react-expert 에이전트를 만들어줘"
+
+Creator Workflow:
+
+0. RESEARCH PHASE
+   [creator → WebSearch] "React official documentation best practices"
+   [creator → WebSearch] "React style guide canonical reference"
+
+   Research Results:
+   ┌────────────────────────────────────────────────────────────┐
+   │ Effective React (closest to Effective Go):                 │
+   │ → React Docs - Thinking in React                          │
+   │   https://react.dev/learn/thinking-in-react               │
+   │                                                            │
+   │ Official Reference:                                        │
+   │ → React Documentation                                      │
+   │   https://react.dev                                        │
+   │                                                            │
+   │ Style Guide:                                               │
+   │ → Airbnb React/JSX Style Guide                            │
+   │   https://github.com/airbnb/javascript/tree/master/react  │
+   └────────────────────────────────────────────────────────────┘
+
+1. CREATE PHASE
+   [creator → Write] agents/sw-engineer/frontend/react-expert/AGENT.md
+   [creator → Write] agents/sw-engineer/frontend/react-expert/index.yaml
+   [creator → Write] agents/sw-engineer/frontend/react-expert/refs/REFERENCES.md
+
+2. REGISTRY UPDATE
+   [creator → Edit] agents/index.yaml
+
+Result:
+  agents/sw-engineer/frontend/react-expert/
+  ├── AGENT.md           (with Key References section)
+  ├── index.yaml         (with references block)
+  └── refs/
+      └── REFERENCES.md  (full research results)
+```
+
+## Skip Research Conditions
+
+Research phase can be skipped when:
+- Agent is not technology/language specific (e.g., orchestrator)
+- User explicitly provides reference URLs
+- Agent is pure system/utility type (e.g., naggy, memory-keeper)