Menu
Reference code folder conventions — storing external code and documentation for AI-assisted development context
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Git operations: branching, commit message format, pre-commit hook handling, and push policy
Full workflow: environment setup, running experiments, reusing and implementing new components (models, datasets, plmodules, callbacks), and testing
How to load a checkpoint and run evaluation (inference only, no training)
Coding style guidelines and common pitfalls for this project
Hydra configuration file structure and conventions for models, datasets, callbacks, and training
Data format conventions for datasets and plmodules
Based on SOC occupation classification
| name | reference |
| description | Reference code folder conventions — storing external code and documentation for AI-assisted development context |
docs/reference/ stores reference external code and documentation. These files serve as helpful context for AI-assisted code generation and development — you can attach them to your conversation so the AI can draw on external codebases.
check-added-large-files pre-commit hook is disabled in this folder, so large files can be committed freely.README.md entry in docs/reference/ to document each file:- file-name.txt
- Source: name of external source
- Content: brief description of what this contains