본문으로 건너뛰기
cccskills
무료GitHub에 공개

architecture-design

Add datasets, models, and other components to machine learning projects using consistent registration and creation patterns. The skill guides file placement, configuration, and automatic module loading so new components fit the project's established architecture.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Use only when creating new registrable ML components that require Factory or Registry patterns.

설치 방법 보기

이럴 때 유용합니다

  • Adding a registered Dataset class
  • Creating a model driven by configuration
  • Wiring registration and creation logic in a new module
  • Setting up an ML project with registrable components

포함된 파일(11)

  • SKILL.md9.0 KB
  • examples/augmentation_example.py3.1 KB
  • examples/config_example.yaml2.3 KB
  • examples/custom_dataset.py1.5 KB
  • examples/custom_model.py6.1 KB
  • examples/pipeline_example.sh5.0 KB
  • references/auto_import.md3.4 KB
  • references/code_style.md5.2 KB
  • references/factory_pattern.md1.4 KB
  • references/registry_pattern.md2.5 KB
  • references/structure.md4.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Architecture Design - ML Project Template

This skill defines the standard code architecture for machine learning projects based on the template structure. When modifying or extending code, follow these patterns to maintain consistency.

Overview

The project follows a modular, extensible architecture with clear separation of concerns. Each module (data, model, trainer, analysis) is independently organized using factory and registry patterns for maximum flexibility.

When to Use

Use this skill when:

  • Creating a new Dataset class that needs @register_dataset
  • Creating a new Model class that needs @register_model
  • Creating a new module directory with __init__.py factory wiring
  • Initializing a new ML project structure from scratch
  • Adding new component types such as Augmentation, CollateFunction, or Metrics

When Not to Use

Do not use this skill when:

  • Modifying existing functions or methods
  • Fixing bugs in existing code
  • Adding helper functions or utilities
  • Refactoring without adding new registrable components
  • Making simple code changes to a single file
  • Modifying configuration files
  • Reading or understanding existing code

Key indicator: if the task does not require a @register_* decorator or a Factory pattern, skip this skill.

Core Design Patterns

Factory Pattern

Each module uses a factory to create instances dynamically:

# Example from data_module/dataset/__init__.py
DATASET_FACTORY: Dict = {}

def DatasetFactory(data_name: str):
    dataset = DATASET_FACTORY.get(data_name, None)
    if dataset is None:
        print(f"{data_name} dataset is not implementation, use simple dataset")
        dataset = DATASET_FACTORY.get('simple')
    return dataset

For detailed guidance, refer to references/factory_pattern.md.

Registry Pattern

Components register themselves via decorators:

# Example from data_module/dataset/simple_dataset.py
@register_dataset("simple")
class SimpleDataset(Dataset):
    def __init__(self, data):
        self.data = data

For detailed guidance, refer to references/registry_pattern.md.

Auto-Import Pattern

Modules automatically discover and import submodules:

# Example from data_module/dataset/__init__.py
models_dir = os.path.dirname(__file__)
import_modules(models_dir, "src.data_module.dataset")

For detailed guidance, refer to references/auto_import.md.

Directory Structure

project/
├── run/
│   ├── pipeline/            # Main workflow scripts
│   │   ├── training/        # Training pipelines
│   │   ├── prepare_data/    # Data preparation pipelines
│   │   └── analysis/        # Analysis pipelines
│   └── conf/                # Hydra configuration files
│       ├── training/        # Training configs
│       ├── dataset/         # Dataset configs
│       ├── model/           # Model configs
│       ├── prepare_data/    # Data prep configs
│       └── analysis/        # Analysis configs
│
├── src/
│   ├── data_module/         # Data processing module
│   │   ├── dataset/         # Dataset implementations
│   │   ├── augmentation/    # Data augmentation
│   │   ├── collate_fn/      # Collate functions
│   │   ├── compute_metrics/ # Metrics computation
│   │   ├── prepare_data/    # Data preparation logic
│   │   ├── data_func/       # Data utility functions
│   │   └── utils.py         # Module-specific utilities
│   │
│   ├── model_module/        # Model implementations
│   │   ├── brain_decoder/   # Brain decoder models
│   │   └── model/           # Alternative model location
│   │
│   ├── trainer_module/      # Training logic
│   ├── analysis_module/     # Analysis and evaluation
│   ├── llm/                 # LLM-related code
│   └── utils/               # Shared utilities
│
├── data/
│   ├── raw/                 # Original, immutable data
│   ├── processed/           # Cleaned, transformed data
│   └── external/            # Third-party data
│
├── outputs/
│   ├── logs/                # Training and evaluation logs
│   ├── checkpoints/         # Model checkpoints
│   ├── tables/              # Result tables
│   └── figures/             # Plots and visualizations
│
├── pyproject.toml           # Project configuration
├── uv.lock                  # Dependency lock file
├── TODO.md                  # Task tracking
├── README.md                # Project documentation
└── .gitignore               # Git ignore rules

For detailed directory structure with file descriptions, refer to references/structure.md.

Module Organization

Creating a New Dataset

When adding a new dataset:

  1. Create file in src/data_module/dataset/
  2. Use @register_dataset("name") decorator
  3. Inherit from torch.utils.data.Dataset
  4. Implement __init__, __len__, __getitem__
from torch.utils.data import Dataset
from typing import Dict
import torch
from src.data_module.dataset import register_dataset

@register_dataset("custom")
class CustomDataset(Dataset):
    def __init__(self, data):
        self.data = data

    def __len__(self):
        return len(self.data)

    def __getitem__(self, i: int) -> Dict[str, torch.Tensor]:
        return self.data[i]

Creating a New Model

CRITICAL: Models use config-driven pattern

When adding a new model:

  1. Create file in src/model_module/model/ or appropriate module subdirectory
  2. Use @register_model('ModelName') decorator
  3. __init__ accepts ONLY cfg parameter - all hyperparameters come from config
  4. forward() returns dict: {"loss": loss, "labels": labels, "logits": logits}
  5. Handle training vs inference modes using self.training
from src.model_module.brain_decoder import register_model

@register_model('MyModel')
class MyModel(nn.Module):
    def __init__(self, cfg):
        super().__init__()
        self.cfg = cfg
        self.task = cfg.dataset.task

        # ALL parameters from cfg
        self.hidden_dim = cfg.model.hidden_dim
        self.output_dim = cfg.dataset.target_size[cfg.dataset.task]

    def forward(self, x, labels=None, **kwargs):
        if self.training:
            # Training logic
            pass
        else:
            # Inference logic
            pass

        return {"loss": loss, "labels": labels, "logits": logits}

Adding Data Augmentation

When adding augmentation:

  1. Create file in src/data_module/augmentation/
  2. Implement transformation function
  3. Register with factory if needed

Code Style Guidelines

For comprehensive style guidelines, refer to references/code_style.md.

Key principles:

  • Always use type hints for function signatures
  • Follow import order: standard library → third-party → local
  • Module __init__.py files contain factory/registry logic
  • Model classes must be config-driven

Configuration Management

The project uses Hydra for configuration management:

  • Config files in run/conf/ organize by module
  • Each stage (training, analysis) has its own config structure
  • Use YAML files for all configuration

When Working on This Project

Before Modifying Code

  1. Read the relevant module's factory/registry pattern
  2. Check existing implementations for consistency
  3. Follow the established directory structure
  4. Use registration decorators for new components

Adding New Features

  1. Determine which module the feature belongs to
  2. Check if similar functionality exists
  3. Follow factory/registry pattern if creating new component types
  4. Add configuration files if needed
  5. Update documentation

Code Review Checklist

  • Uses factory/registry pattern appropriately
  • Follows module directory structure
  • Has proper type annotations
  • Imports are correctly ordered
  • Registration decorator is used
  • Configuration files are added if needed

Additional Resources

Reference Files

For detailed information, consult:

  • references/structure.md - Detailed directory structure with file descriptions
  • references/factory_pattern.md - Factory pattern in-depth explanation
  • references/registry_pattern.md - Registry pattern in-depth explanation
  • references/auto_import.md - Auto-import pattern in-depth explanation
  • references/code_style.md - Comprehensive code style guidelines

Example Files

Working examples in examples/:

  • examples/custom_dataset.py - Custom dataset implementation
  • examples/custom_model.py - Custom model implementation
  • examples/augmentation_example.py - Data augmentation example
  • examples/config_example.yaml - Configuration file example
  • examples/pipeline_example.sh - Pipeline script example

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Create and configure Claude Code agents using Markdown files with YAML configuration headers. Define when each agent should run, write its responsibilities and workflow, choose models and tools, and check configuration and triggering behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Create a Claude Code subagent
  • Define triggering conditions with concrete examples
  • Configure an agent's model, color, and tools
Galaxy-Dawn/claude-scholar5.9천2026년 10월 19일 업데이트

Investigate code errors through a structured process using reproduction steps, logs, and testable explanations. The workflow guides fault isolation, fixes, and follow-up checks, with common error patterns for Python, JavaScript/TypeScript, and Bash/Zsh.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigating an error using logs and reproduction steps
  • Finding why code broke after a recent change
  • Troubleshooting common shell script errors
Galaxy-Dawn/claude-scholar5.9천2026년 10월 19일 업데이트

Check academic references for existence, accurate publication details, and support for the claims being cited. This guide explains how to verify sources, obtain bibliography entries, and flag references that cannot be confirmed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking references suggested by AI
  • Verifying authors, titles, and publication years
  • Checking whether a paper supports a cited claim
Galaxy-Dawn/claude-scholar5.9천2026년 10월 19일 업데이트

Review code changes and pull requests for correctness, security, performance, and test quality. The skill helps prioritize issues, write specific and constructive feedback, and create shared review checklists and standards for a development team.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing code changes and pull requests
  • Writing review comments with clear priorities and fixes
  • Creating shared review checklists for a team
Galaxy-Dawn/claude-scholar5.9천2026년 10월 19일 업데이트

Create reusable slash commands, prompts invoked by typing a slash, for Claude Code. The skill explains Markdown structure, arguments, file references, tool permissions, and plugin integration so recurring tasks can follow a defined workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Turning recurring prompts into slash commands
  • Creating review commands with arguments and file references
  • Sharing project-specific commands with a team
Galaxy-Dawn/claude-scholar5.9천2026년 10월 19일 업데이트

Apply a short quality checklist to everyday code changes. Read existing code first, keep edits focused, check types and common security risks, verify execution, remove debugging leftovers, and summarize what changed and its impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking quality during routine feature work
  • Reviewing type safety in Python and TypeScript
  • Checking input handling and common security risks
Galaxy-Dawn/claude-scholar5.9천2026년 10월 19일 업데이트

Galaxy-Dawn의 스킬 모두 보기

이 스킬의 문제 신고