agent-identifier
Use when creating or configuring Claude Code agents and their frontmatter.
Use only when creating new registrable ML components that require Factory or Registry patterns.
$ npx -y skills add Galaxy-Dawn/claude-scholar --skill architecture-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/architecture-designContext preview
The summary Claude sees to decide when to auto-load this skill.
Use only when creating new registrable ML components that require Factory or Registry patterns.
name: architecture-design description: Use only when creating new registrable ML components that require Factory or Registry patterns. version: 1.2.0
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.
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.
Use this skill when:
Do not use this skill when:
Key indicator: if the task does not require a `@register_*` decorator or a Factory pattern, skip this skill.
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 datasetFor detailed guidance, refer to `references/factory_pattern.md`.
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 = dataFor detailed guidance, refer to `references/registry_pattern.md`.
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`.
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`.
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]**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.cfgSemi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.
Repo: Galaxy-Dawn/claude-scholar
Use when creating or configuring Claude Code agents and their frontmatter.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem",…
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how…
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or…
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command…
Use for everyday coding tasks that involve writing or modifying source code.