oh-my-customcode 0.1.4 → 0.2.0

package/templates/skills/development/rust-best-practices/SKILL.md

@@ -1,266 +0,0 @@
-# Rust Best Practices Skill
-
-> **Category**: Development
-> **Source**: Internal (based on Rust API Guidelines and The Book)
-
-## Purpose
-
-Apply idiomatic Rust patterns and best practices from official documentation.
-
-## Core Principles
-
-```
-Safety without garbage collection
-Zero-cost abstractions
-Fearless concurrency
-Ownership as a feature
-```
-
-## Rules
-
-### 1. Naming Conventions
-
-```yaml
-crates:
-  style: snake_case or kebab-case
-  example: my_crate, my-crate
-
-modules:
-  style: snake_case
-  example: my_module
-
-types:
-  style: UpperCamelCase
-  example: MyStruct, MyEnum
-
-traits:
-  style: UpperCamelCase
-  example: Iterator, Display
-
-functions_methods:
-  style: snake_case
-  example: my_function, get_value
-
-constants:
-  style: SCREAMING_SNAKE_CASE
-  example: MAX_SIZE
-
-type_parameters:
-  style: single uppercase or CamelCase
-  example: T, E, Item
-
-lifetimes:
-  style: short lowercase
-  example: 'a, 'b, 'static
-
-macros:
-  style: snake_case!
-  example: vec!, println!
-```
-
-### 2. Ownership and Borrowing
-
-```yaml
-principles:
-  - Each value has exactly one owner
-  - References cannot outlive the data they reference
-  - Either one mutable reference OR many immutable references
-
-prefer:
-  - "&T over T" when not needing ownership
-  - "&mut T over T" when modifying without consuming
-  - "T over Box<T>" when size is known at compile time
-
-avoid:
-  - Clone when borrowing suffices
-  - RefCell unless interior mutability is needed
-  - Unsafe unless absolutely necessary
-```
-
-### 3. Error Handling
-
-```yaml
-result_type:
-  - Return Result<T, E> for recoverable errors
-  - Use ? operator for propagation
-  - Define custom error types for libraries
-
-option_type:
-  - Use Option<T> for nullable values
-  - Prefer map/and_then over match when appropriate
-  - Use unwrap_or, unwrap_or_else, unwrap_or_default
-
-panic:
-  - Only for unrecoverable errors
-  - Use in tests with assert!, assert_eq!
-  - Avoid in library code
-
-patterns: |
-  // Propagation with ?
-  fn read_file() -> Result<String, io::Error> {
-      let mut file = File::open("file.txt")?;
-      let mut contents = String::new();
-      file.read_to_string(&mut contents)?;
-      Ok(contents)
-  }
-
-  // Custom error type
-  #[derive(Debug)]
-  enum MyError {
-      Io(io::Error),
-      Parse(ParseIntError),
-  }
-```
-
-### 4. Traits and Generics
-
-```yaml
-trait_design:
-  - Keep traits focused and small
-  - Use associated types for output types
-  - Implement standard traits: Debug, Clone, Default, PartialEq
-
-standard_traits:
-  - Debug: for debugging output
-  - Clone: explicit duplication
-  - Default: default value construction
-  - PartialEq, Eq: equality comparison
-  - PartialOrd, Ord: ordering
-  - Hash: for HashMap keys
-  - Display: user-facing output
-  - From/Into: type conversion
-
-generics:
-  - Use trait bounds to specify requirements
-  - Prefer impl Trait in argument position
-  - Use where clauses for complex bounds
-```
-
-### 5. Memory Management
-
-```yaml
-stack_vs_heap:
-  - Stack: fixed-size, Copy types
-  - Heap: dynamic-size, Box, Vec, String
-
-smart_pointers:
-  - Box<T>: heap allocation with single owner
-  - Rc<T>: reference counting (single-threaded)
-  - Arc<T>: atomic reference counting (multi-threaded)
-  - RefCell<T>: interior mutability
-
-avoid_leaks:
-  - Drop trait for cleanup
-  - RAII pattern for resources
-  - Weak references to break cycles
-```
-
-### 6. Concurrency
-
-```yaml
-send_sync:
-  - Send: safe to transfer between threads
-  - Sync: safe to share references between threads
-
-primitives:
-  - Mutex<T>: mutual exclusion
-  - RwLock<T>: multiple readers or one writer
-  - Arc<T>: thread-safe reference counting
-  - mpsc: channels for message passing
-
-patterns: |
-  // Shared state with Arc and Mutex
-  let counter = Arc::new(Mutex::new(0));
-  let counter_clone = Arc::clone(&counter);
-
-  thread::spawn(move || {
-      let mut num = counter_clone.lock().unwrap();
-      *num += 1;
-  });
-
-  // Message passing
-  let (tx, rx) = mpsc::channel();
-  thread::spawn(move || {
-      tx.send(value).unwrap();
-  });
-  let received = rx.recv().unwrap();
-```
-
-### 7. API Design
-
-```yaml
-guidelines:
-  - Accept borrowed data when possible
-  - Return owned data when the caller needs it
-  - Use Into/AsRef for flexible parameters
-  - Implement standard conversion traits
-
-constructors:
-  - new() for primary constructor
-  - with_* for alternative constructors
-  - Builder pattern for many parameters
-
-methods:
-  - is_* for boolean queries
-  - as_* for cheap conversions (borrows)
-  - to_* for expensive conversions (copies)
-  - into_* for ownership transfers
-```
-
-### 8. Documentation
-
-```yaml
-rules:
-  - Document all public items
-  - Include examples in doc comments
-  - Use # Examples section
-  - Document panics, errors, safety
-
-format: |
-  /// Brief description.
-  ///
-  /// More detailed explanation if needed.
-  ///
-  /// # Examples
-  ///
-  /// ```
-  /// let result = my_function(42);
-  /// assert_eq!(result, 84);
-  /// ```
-  ///
-  /// # Panics
-  ///
-  /// Panics if the input is zero.
-  pub fn my_function(x: i32) -> i32 {
-      x * 2
-  }
-```
-
-### 9. Project Structure
-
-```yaml
-layout:
-  - src/lib.rs or src/main.rs: crate root
-  - src/bin/: additional binaries
-  - tests/: integration tests
-  - benches/: benchmarks
-  - examples/: example programs
-
-modules:
-  - One module per file
-  - mod.rs or filename.rs for module
-  - pub use for re-exports
-```
-
-## Application
-
-When writing or reviewing Rust code:
-
-1. **Always** handle ownership correctly
-2. **Always** handle errors with Result/Option
-3. **Prefer** borrowing over cloning
-4. **Prefer** zero-cost abstractions
-5. **Implement** standard traits (Debug, Clone, etc.)
-6. **Document** public APIs with examples
-7. **Avoid** unsafe unless necessary
-8. **Use** clippy for linting

package/templates/skills/development/rust-best-practices/index.yaml

@@ -1,26 +0,0 @@
-# Rust Best Practices Skill
-
-metadata:
-  name: rust-best-practices
-  category: development
-  description: Idiomatic Rust patterns from official guidelines
-
-source:
-  type: internal
-  reference:
-    - https://doc.rust-lang.org/book/
-    - https://rust-lang.github.io/api-guidelines/
-    - https://doc.rust-lang.org/nightly/style-guide/
-
-provides:
-  - Rust naming conventions
-  - Ownership and borrowing patterns
-  - Error handling patterns
-  - Trait and generic design
-  - Memory management guidelines
-  - Concurrency patterns
-  - API design guidelines
-  - Documentation standards
-
-used_by:
-  - rust-expert

package/templates/skills/development/typescript-best-practices/index.yaml

@@ -1,28 +0,0 @@
-# TypeScript Best Practices Skill
-
-metadata:
-  name: typescript-best-practices
-  category: development
-  description: Type-safe TypeScript patterns from industry standards
-
-source:
-  type: internal
-  reference:
-    - https://www.typescriptlang.org/docs/handbook/
-    - https://google.github.io/styleguide/tsguide.html
-    - https://basarat.gitbook.io/typescript/
-
-provides:
-  - TypeScript type system patterns
-  - Interface and type design
-  - Generic usage guidelines
-  - Variable and constant rules
-  - Function design patterns
-  - Class structure guidelines
-  - Naming conventions
-  - Control flow patterns
-  - Error handling patterns
-  - Import/export organization
-
-used_by:
-  - typescript-expert

package/templates/skills/development/vercel-deploy/SKILL.md

@@ -1,73 +0,0 @@
-# Vercel Deploy
-
-> **Source**: vercel-labs/agent-skills
-> **Capability**: Instant deployment to Vercel
-
-## When to Use
-
-- Deploy application to Vercel
-- Create preview deployments
-- Generate shareable URLs
-
-## Features
-
-### Framework Detection
-```
-Auto-detects 40+ frameworks from package.json:
-- Next.js
-- React
-- Vue
-- Nuxt
-- Svelte
-- Astro
-- and more...
-```
-
-### Auto Exclusions
-```
-Automatically excludes:
-- node_modules/
-- .git/
-- .env files
-```
-
-### Output
-```
-On successful deployment:
-1. Preview URL (view deployment)
-2. Claim URL (transfer ownership)
-```
-
-## Execution Flow
-
-```
-1. Detect project framework
-2. Prepare deployment bundle
-3. Upload to Vercel
-4. Return URLs
-```
-
-## Output Format
-
-```
-[Deploy Success]
-Preview: https://project-xxx.vercel.app
-Claim: https://vercel.com/claim/xxx
-```
-
-## Scripts
-
-See `scripts/deploy.sh` for deployment automation.
-
-## Requirements
-
-- Valid project structure
-- package.json present
-- Vercel CLI or API token (for authenticated deploys)
-
-## Limitations
-
-- Claimable deploys are anonymous
-- Preview URLs are temporary
-- Full features require Vercel account
-```

package/templates/skills/development/vercel-deploy/index.yaml

@@ -1,30 +0,0 @@
-# Vercel Deploy Skill
-
-metadata:
-  name: vercel-deploy
-  category: development
-  description: Deploy applications to Vercel with auto-detection and preview URLs
-
-source:
-  type: external
-  origin: github
-  url: https://github.com/vercel-labs/agent-skills
-  path: skills/vercel-deploy-claimable
-  version: "1.0.0"
-  last_updated: "2025-01-22"
-
-triggers:
-  - "deploy to Vercel"
-  - "create preview"
-  - "publish site"
-  - "Vercel deployment"
-
-capabilities:
-  - Auto-detect 40+ frameworks
-  - Generate preview URLs
-  - Ownership transfer links
-  - Exclude node_modules, .git automatically
-
-requirements:
-  - Vercel CLI or API access
-  - Project with package.json

package/templates/skills/development/web-design-guidelines/SKILL.md

@@ -1,117 +0,0 @@
-# Web Design Guidelines
-
-> **Source**: vercel-labs/agent-skills
-> **Rules**: 100+ rules across 11 categories
-
-## When to Use
-
-- UI code review
-- Accessibility audit
-- Design consistency check
-- UX best practices verification
-
-## Command Triggers
-
-- "Review UI"
-- "Check accessibility"
-- "Design audit"
-- "Verify best practices"
-
-## Categories
-
-### ARIA Labels
-```
-- All interactive elements have labels
-- Proper role attributes
-- aria-live for dynamic content
-- Descriptive aria-describedby
-```
-
-### Focus States
-```
-- Visible focus indicators
-- Logical focus order
-- Focus trapping in modals
-- Skip links for navigation
-```
-
-### Form Validation
-```
-- Inline error messages
-- Accessible error announcements
-- Clear input requirements
-- Proper label associations
-```
-
-### Animations
-```
-- Respect prefers-reduced-motion
-- Meaningful animations only
-- Performance-optimized transforms
-- No animation on load
-```
-
-### Typography
-```
-- Readable font sizes (16px min)
-- Proper line height (1.5+)
-- Sufficient color contrast
-- Responsive text scaling
-```
-
-### Images
-```
-- Alt text for all images
-- Decorative images marked
-- Responsive images
-- Lazy loading implemented
-```
-
-### Performance
-```
-- Minimize layout shifts
-- Optimize largest contentful paint
-- Reduce time to interactive
-- Efficient CSS selectors
-```
-
-### Navigation
-```
-- Keyboard accessible
-- Clear current state
-- Consistent patterns
-- Breadcrumbs where needed
-```
-
-### Dark Mode
-```
-- System preference detection
-- Smooth transitions
-- Consistent color tokens
-- Image adjustments
-```
-
-### Touch Interaction
-```
-- Minimum 44px touch targets
-- Appropriate spacing
-- Gesture alternatives
-- Haptic feedback consideration
-```
-
-### i18n
-```
-- RTL support
-- Text expansion room
-- Locale-aware formatting
-- Translation-ready strings
-```
-
-## Execution Flow
-
-```
-1. Scan UI components
-2. Check against category rules
-3. Report violations
-4. Suggest fixes
-```

package/templates/skills/development/web-design-guidelines/index.yaml

@@ -1,34 +0,0 @@
-# Web Design Guidelines Skill
-
-metadata:
-  name: web-design-guidelines
-  category: development
-  description: UI code review with 100+ rules for accessibility, performance, and UX
-
-source:
-  type: external
-  origin: github
-  url: https://github.com/vercel-labs/agent-skills
-  path: skills/web-design-guidelines
-  version: "1.0.0"
-  last_updated: "2025-01-22"
-
-triggers:
-  - "UI review"
-  - "accessibility check"
-  - "design audit"
-  - "UX review"
-  - "a11y check"
-
-categories:
-  - aria-labels
-  - focus-states
-  - form-validation
-  - animations
-  - typography
-  - images
-  - performance
-  - navigation
-  - dark-mode
-  - touch-interaction
-  - i18n

package/templates/skills/index.yaml

@@ -1,129 +0,0 @@
-# Baekgom Agents - Skill Registry
-
-categories:
-  development:
-    description: Development related skills
-    skills:
-      - name: react-best-practices
-        path: ./development/react-best-practices/
-        description: React/Next.js performance optimization (40+ rules)
-        source:
-          type: external
-          origin: github
-          url: https://github.com/vercel-labs/agent-skills
-
-      - name: web-design-guidelines
-        path: ./development/web-design-guidelines/
-        description: UI code review for accessibility and UX (100+ rules)
-        source:
-          type: external
-          origin: github
-          url: https://github.com/vercel-labs/agent-skills
-
-      - name: vercel-deploy
-        path: ./development/vercel-deploy/
-        description: Deploy applications to Vercel
-        source:
-          type: external
-          origin: github
-          url: https://github.com/vercel-labs/agent-skills
-
-      - name: go-best-practices
-        path: ./development/go-best-practices/
-        description: Idiomatic Go patterns from Effective Go
-        source:
-          type: internal
-
-      - name: python-best-practices
-        path: ./development/python-best-practices/
-        description: Pythonic patterns from PEP 8 and PEP 20
-        source:
-          type: internal
-
-      - name: rust-best-practices
-        path: ./development/rust-best-practices/
-        description: Idiomatic Rust patterns from official guidelines
-        source:
-          type: internal
-
-      - name: kotlin-best-practices
-        path: ./development/kotlin-best-practices/
-        description: Idiomatic Kotlin patterns from JetBrains conventions
-        source:
-          type: internal
-
-      - name: typescript-best-practices
-        path: ./development/typescript-best-practices/
-        description: Type-safe TypeScript patterns from industry standards
-        source:
-          type: internal
-
-  backend:
-    description: Backend development skills
-    skills:
-      - name: fastapi-best-practices
-        path: ./backend/fastapi-best-practices/
-        description: FastAPI patterns for high-performance async APIs
-        source:
-          type: internal
-
-      - name: springboot-best-practices
-        path: ./backend/springboot-best-practices/
-        description: Spring Boot patterns for enterprise Java applications
-        source:
-          type: internal
-
-      - name: go-backend-best-practices
-        path: ./backend/go-backend-best-practices/
-        description: Go backend patterns from Uber style and standard layout
-        source:
-          type: internal
-
-  infrastructure:
-    description: Infrastructure and DevOps skills
-    skills:
-      - name: docker-best-practices
-        path: ./infrastructure/docker-best-practices/
-        description: Docker patterns for optimized containerization
-        source:
-          type: internal
-
-      - name: aws-best-practices
-        path: ./infrastructure/aws-best-practices/
-        description: AWS patterns from Well-Architected Framework
-        source:
-          type: internal
-
-  system:
-    description: System-level operation skills
-    skills:
-      - name: memory-management
-        path: ./system/memory-management/
-        description: Session memory persistence with claude-mem
-        source:
-          type: internal
-
-      - name: result-aggregation
-        path: ./system/result-aggregation/
-        description: Multi-agent result aggregation and formatting
-        source:
-          type: internal
-
-  orchestration:
-    description: Orchestration and workflow skills
-    skills:
-      - name: pipeline-execution
-        path: ./orchestration/pipeline-execution/
-        description: Sequential pipeline execution with step management
-        source:
-          type: internal
-
-      - name: intent-detection
-        path: ./orchestration/intent-detection/
-        description: User intent classification and agent routing
-        source:
-          type: internal
-
-  localsystem:
-    description: Local system operation skills
-    skills: []