oh-my-customcode 0.12.1 → 0.12.3

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

@@ -1,203 +0,0 @@
----
-name: secretary-routing
-description: Routes agent management tasks to the correct manager agent. Use when user requests agent creation, updates, audits, git operations, sync checks, or verification.
-user-invocable: false
----
-
-# Secretary Routing Skill
-
-## Purpose
-
-Routes agent management tasks to the appropriate manager agent. This skill contains the coordination logic for orchestrating manager agents (mgr-creator, mgr-updater, mgr-supplier, mgr-gitnerd, mgr-sync-checker, mgr-sauron).
-
-## Manager Agents
-
-| Agent | Purpose | Triggers |
-|-------|---------|----------|
-| mgr-creator | Create new agents | "create agent", "new agent" |
-| mgr-updater | Update external agents | "update agent", "sync" |
-| mgr-supplier | Validate dependencies | "audit", "check deps" |
-| mgr-gitnerd | Git operations | "commit", "push", "pr" |
-| mgr-sync-checker | Sync verification | "sync check", "verify sync" |
-| mgr-sauron | R016 auto-verification | "verify", "full check" |
-| mgr-claude-code-bible | Codex 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
-
-```
-User Input → Routing → Manager Agent
-
-create   → mgr-creator
-update   → mgr-updater
-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)
-```
-
-## Routing Rules
-
-### 1. Single Task Routing
-
-```
-1. Parse user command and identify intent
-2. Select appropriate manager agent:
-   - "create agent X" → mgr-creator
-   - "update agent Y" → mgr-updater
-   - "audit agent Z" → mgr-supplier
-   - "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
-```
-
-### 2. Batch/Parallel Task Routing
-
-When command requires multiple independent operations:
-
-```
-1. Break down into sub-tasks
-2. Identify parallelizable tasks (max 4)
-3. Spawn parallel Task instances
-4. Coordinate execution following R009
-5. Aggregate results following R013 (ecomode)
-6. Report summary to user
-```
-
-Example:
-```
-User: "Create golang, python, rust expert agents"
-
-Route:
-  Task(mgr-creator role → create lang-golang-expert, model: "balanced")
-  Task(mgr-creator role → create lang-python-expert, model: "balanced")
-  Task(mgr-creator role → create lang-rust-expert, model: "balanced")
-
-Result: 3 agents created in parallel
-```
-
-## Sub-agent Model Selection
-
-Use Task tool's `model` parameter to optimize cost and performance:
-
-### Model Mapping
-
-| Agent | Recommended Model | Reason |
-|-------|-------------------|--------|
-| mgr-creator | `balanced` | File generation, balanced |
-| mgr-updater | `balanced` | External sync, web fetch |
-| mgr-supplier | `fast` | File scan, validation |
-| mgr-gitnerd | `balanced` | Commit message quality |
-| mgr-sync-checker | `fast` | Fast verification |
-| mgr-sauron | `balanced` | Multi-round verification |
-| mgr-claude-code-bible | `balanced` | Spec compliance checks |
-| sys-memory-keeper | `balanced` | Memory operations, search |
-| sys-naggy | `fast` | Simple TODO tracking |
-
-### Task Call Examples
-
-```
-# Complex analysis (rare)
-Task(
-  subagent_type: "general-purpose",
-  prompt: "Analyze agent dependencies and suggest improvements",
-  model: "reasoning"
-)
-
-# Standard manager task (create agent)
-Task(
-  subagent_type: "general-purpose",
-  prompt: "Create new lang-golang-expert agent following mgr-creator workflow",
-  model: "balanced"
-)
-
-# Simple file operation
-Task(
-  subagent_type: "general-purpose",
-  prompt: "Search for all AGENT.md files and validate symlinks",
-  model: "fast"
-)
-```
-
-## Parallel Execution
-
-Following R009:
-- Maximum 4 parallel instances
-- Only non-orchestrator agents
-- Independent tasks only
-- Proper resource management
-
-## Display Format
-
-When spawning parallel tasks, use format: `{task-name}:{model}`
-
-```
-[Parallel] Spawning 3 instances...
-
-[Instance 1] create-golang:balanced → lang-golang-expert
-[Instance 2] create-python:balanced → lang-python-expert
-[Instance 3] create-rust:balanced → lang-rust-expert
-
-[Progress] ████████░░░░ 2/3
-
-[Instance 1] create-golang:balanced ✓ lang-golang-expert created
-[Instance 2] create-python:balanced ✓ lang-python-expert created
-[Instance 3] create-rust:balanced ✓ lang-rust-expert created
-
-[Summary] 3/3 tasks completed successfully
-```
-
-## Ecomode Integration
-
-When 4+ parallel tasks are spawned, activate ecomode (R013):
-- Compact output format (status + 1-2 sentence summary)
-- Skip intermediate steps
-- Return essential results only
-- Aggregate with icons: ✓ (success), ✗ (failed), ⚠ (partial)
-
-## Error Handling
-
-```yaml
-retry_policy:
-  max_retries: 3
-  backoff: exponential
-
-failure_modes:
-  single_failure: Report and continue
-  critical_failure: Stop and escalate
-  timeout: Retry or skip with notice
-```
-
-## Agent Teams Awareness
-
-Before routing via Task tool, check if Agent Teams is available (`CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` or TeamCreate/SendMessage tools present).
-
-**Self-check:** Does this task need 3+ agents, shared state, or inter-agent communication? If yes, prefer Agent Teams over Task tool. See R018 for the full decision matrix.
-
-| Scenario | Preferred |
-|----------|-----------|
-| Single manager task | Task Tool |
-| Batch agent creation (3+) | Agent Teams |
-| Multi-round verification (sauron) | Task Tool |
-| Agent audit + fix cycle | Agent Teams |
-
-## Usage
-
-This skill is NOT user-invocable. It should be automatically triggered when the main conversation detects agent management intent.
-
-Detection criteria:
-- User mentions agent creation/update/audit
-- Command starts with manager agent name
-- System operation requires coordination
-- Batch operation on agents/skills/guides

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

@@ -1,65 +0,0 @@
----
-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/.codex/skills/spark-best-practices/SKILL.md

@@ -1,52 +0,0 @@
----
-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/.codex/skills/springboot-best-practices/SKILL.md

@@ -1,218 +0,0 @@
----
-name: springboot-best-practices
-description: Spring Boot patterns for enterprise Java applications
-user-invocable: false
----
-
-## Rules
-
-### 1. Project Structure
-Layered architecture: controller (REST), service (business logic), repository (data access), model/entity, dto, config, exception.
-
-### 2. Dependency Injection
-Constructor injection preferred. Use @RequiredArgsConstructor with final fields. Avoid field injection with @Autowired.
-
-```java
-// GOOD: Constructor injection
-@Service
-@RequiredArgsConstructor
-public class UserService {
-    private final UserRepository userRepository;
-    private final EmailService emailService;
-}
-```
-
-### 3. REST API Design
-@RestController + @RequestMapping. Use @Validated for input, ResponseEntity for responses, proper HTTP status codes.
-
-```java
-@RestController
-@RequestMapping("/api/v1/users")
-@RequiredArgsConstructor
-public class UserController {
-    private final UserService userService;
-
-    @GetMapping("/{id}")
-    public ResponseEntity<UserResponse> getUser(@PathVariable Long id) {
-        return ResponseEntity.ok(userService.findById(id));
-    }
-
-    @PostMapping
-    @ResponseStatus(HttpStatus.CREATED)
-    public UserResponse createUser(@Valid @RequestBody UserRequest request) {
-        return userService.create(request);
-    }
-}
-```
-
-### 4. Service Layer
-Business logic in services. @Transactional boundaries at service level. Interface + implementation pattern.
-
-```java
-@Service
-@Transactional(readOnly = true)
-@RequiredArgsConstructor
-public class UserServiceImpl implements UserService {
-    private final UserRepository userRepository;
-
-    @Override
-    public UserResponse findById(Long id) {
-        User user = userRepository.findById(id)
-            .orElseThrow(() -> new UserNotFoundException(id));
-        return userMapper.toResponse(user);
-    }
-
-    @Override
-    @Transactional
-    public UserResponse create(UserRequest request) {
-        User user = userMapper.toEntity(request);
-        return userMapper.toResponse(userRepository.save(user));
-    }
-}
-```
-
-### 5. Data Access
-Spring Data JPA. @Query or method naming for custom queries. @Entity with proper JPA annotations.
-
-```java
-public interface UserRepository extends JpaRepository<User, Long> {
-    Optional<User> findByEmail(String email);
-
-    @Query("SELECT u FROM User u WHERE u.status = :status")
-    List<User> findByStatus(@Param("status") UserStatus status);
-}
-
-@Entity
-@Table(name = "users")
-@Getter
-@NoArgsConstructor(access = AccessLevel.PROTECTED)
-public class User {
-    @Id
-    @GeneratedValue(strategy = GenerationType.IDENTITY)
-    private Long id;
-
-    @Column(nullable = false, unique = true)
-    private String email;
-
-    @Enumerated(EnumType.STRING)
-    private UserStatus status;
-}
-```
-
-### 6. Exception Handling
-@RestControllerAdvice for global handling. Domain-specific exceptions with proper HTTP status mapping.
-
-```java
-@RestControllerAdvice
-public class GlobalExceptionHandler {
-    @ExceptionHandler(UserNotFoundException.class)
-    @ResponseStatus(HttpStatus.NOT_FOUND)
-    public ErrorResponse handleUserNotFound(UserNotFoundException ex) {
-        return new ErrorResponse("USER_NOT_FOUND", ex.getMessage());
-    }
-
-    @ExceptionHandler(MethodArgumentNotValidException.class)
-    @ResponseStatus(HttpStatus.BAD_REQUEST)
-    public ErrorResponse handleValidation(MethodArgumentNotValidException ex) {
-        List<String> errors = ex.getBindingResult()
-            .getFieldErrors()
-            .stream()
-            .map(e -> e.getField() + ": " + e.getDefaultMessage())
-            .toList();
-        return new ErrorResponse("VALIDATION_ERROR", errors);
-    }
-}
-```
-
-### 7. Configuration
-Profile-based: application-{profile}.yml. @ConfigurationProperties for type-safe config. Externalize sensitive values.
-
-```yaml
-# application.yml
-spring:
-  profiles:
-    active: ${SPRING_PROFILES_ACTIVE:local}
-  datasource:
-    url: ${DATABASE_URL}
-    username: ${DATABASE_USERNAME}
-    password: ${DATABASE_PASSWORD}
-```
-
-```java
-@Configuration
-@ConfigurationProperties(prefix = "app")
-@Validated
-public class AppProperties {
-    @NotBlank
-    private String name;
-
-    @Min(1)
-    private int maxConnections;
-}
-```
-
-### 8. Security
-Spring Security with SecurityFilterChain. Externalize secrets. Proper authentication/authorization patterns.
-
-```java
-@Configuration
-@EnableWebSecurity
-@RequiredArgsConstructor
-public class SecurityConfig {
-    @Bean
-    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
-        return http
-            .csrf(csrf -> csrf.disable())
-            .sessionManagement(session ->
-                session.sessionCreationPolicy(SessionCreationPolicy.STATELESS))
-            .authorizeHttpRequests(auth -> auth
-                .requestMatchers("/api/v1/auth/**").permitAll()
-                .requestMatchers("/api/v1/admin/**").hasRole("ADMIN")
-                .anyRequest().authenticated())
-            .build();
-    }
-}
-```
-
-### 9. Testing
-@WebMvcTest (controller), @DataJpaTest (repository), @SpringBootTest (integration), @MockBean for mocking.
-
-```java
-// Controller test
-@WebMvcTest(UserController.class)
-class UserControllerTest {
-    @Autowired
-    private MockMvc mockMvc;
-
-    @MockBean
-    private UserService userService;
-
-    @Test
-    void getUser_shouldReturnUser() throws Exception {
-        given(userService.findById(1L))
-            .willReturn(new UserResponse(1L, "test@example.com"));
-
-        mockMvc.perform(get("/api/v1/users/1"))
-            .andExpect(status().isOk())
-            .andExpect(jsonPath("$.email").value("test@example.com"));
-    }
-}
-
-// Repository test
-@DataJpaTest
-class UserRepositoryTest {
-    @Autowired
-    private UserRepository userRepository;
-
-    @Test
-    void findByEmail_shouldReturnUser() {
-        User user = userRepository.save(new User("test@example.com"));
-        Optional<User> found = userRepository.findByEmail("test@example.com");
-        assertThat(found).isPresent();
-    }
-}
-```
-
-## Application
-
-Always: constructor injection, layered architecture, DTOs, global exception handling, externalized config, proper security, layer-appropriate tests.

package/templates/.codex/skills/status/SKILL.md

@@ -1,153 +0,0 @@
----
-name: status
-description: Show system status and health checks
-argument-hint: "[--verbose] [--health]"
----
-
-# System Status Skill
-
-Show comprehensive system status including agents, skills, guides, and health checks.
-
-## Options
-
-```
---verbose, -v    Detailed status
---health, -h     Health checks only
-```
-
-## Output Format
-
-### Default Status
-```
-AI Agent System - Status
-
-System:
-  Rules: 10 loaded (R000-R009)
-
-Agents:
-  Orchestrator:     1 (secretary)
-  Manager:          3 (mgr-creator, mgr-updater, mgr-supplier)
-  SW Engineer:      6
-  Backend Engineer: 3
-  Infra Engineer:   2
-  Total:           15 agents
-
-Skills:
-  Development:     8
-  Backend:         3
-  Infrastructure:  2
-  Total:          13 skills
-
-Guides:            12 loaded
-Commands:          10 available
-
-Health: ✓ OK
-```
-
-### Verbose Status
-```
-status --verbose
-
-AI Agent System - Detailed Status
-
-Rules:
-  MUST:
-    ✓ R000 language-policy
-    ✓ R001 safety
-    ✓ R002 permissions
-    ✓ R006 agent-design
-
-  SHOULD:
-    ✓ R003 interaction
-    ✓ R004 error-handling
-    ✓ R007 agent-identification
-    ✓ R008 tool-identification
-
-  MAY:
-    ✓ R005 optimization
-    ✓ R009 parallel-execution
-
-Agents:
-  orchestrator/
-    ✓ secretary (internal)
-
-  manager/
-    ✓ mgr-creator (internal)
-    ✓ mgr-updater (internal)
-    ✓ mgr-supplier (internal)
-
-  sw-engineer/
-    ✓ lang-golang-expert (internal)
-    ✓ lang-python-expert (internal)
-    ✓ lang-rust-expert (internal)
-    ✓ lang-kotlin-expert (internal)
-    ✓ lang-typescript-expert (internal)
-    ✓ fe-vercel-agent (external v1.0.0)
-
-  sw-engineer/backend/
-    ✓ be-fastapi-expert (internal)
-    ✓ be-springboot-expert (internal)
-    ✓ be-go-backend-expert (internal)
-
-  infra-engineer/
-    ✓ infra-docker-expert (internal)
-    ✓ infra-aws-expert (internal)
-
-Skills:
-  development/
-    ✓ go-best-practices
-    ✓ python-best-practices
-    ✓ rust-best-practices
-    ✓ kotlin-best-practices
-    ✓ typescript-best-practices
-    ✓ react-best-practices
-    ✓ web-design-guidelines
-    ✓ vercel-deploy
-
-  backend/
-    ✓ fastapi-best-practices
-    ✓ springboot-best-practices
-    ✓ go-backend-best-practices
-
-  infrastructure/
-    ✓ docker-best-practices
-    ✓ aws-best-practices
-
-Guides:
-  ✓ claude-code, web-design
-  ✓ golang, python, rust, kotlin, typescript
-  ✓ fastapi, springboot, go-backend
-  ✓ docker, aws
-
-Commands:
-  system:    lists, status, help
-  manager:   create-agent, update-docs, update-external, audit-agents, fix-refs
-  dev:       dev-review, dev-refactor
-
-All systems operational.
-```
-
-### Health Check
-```
-status --health
-
-Health Checks:
-
-Agents:
-  ✓ 15/15 agents valid
-  ✓ All agent files exist in .codex/agents/
-
-Dependencies:
-  ✓ All skill references valid
-  ✓ All guide references valid
-
-External Sources:
-  ✓ fe-vercel-agent (github: reachable)
-
-Documentation:
-  ✓ AGENTS.md in sync
-  ✓ All .codex/agents/*.md files valid
-  ✓ All .codex/skills/*/SKILL.md files valid
-
-Result: HEALTHY
-```