module-curationlisted

# Module Curation Use this skill for `modules/*.yaml` work and for project pages that describe module/pathway curation. The goal is a reusable, defensible biological module, not a flat list of annotations or a species-specific note disguised as a module. ## Workflow 1. Read the local context before editing: - `modules/README.md` - the target `modules/<module>.yaml` - any adjacent `<module>-deep-research-*.md` - related `projects/**` batch page(s), if the task is pathway-batch work - relevant gene reviews and UniProt/GOA files for concrete members 2. Decide the module boundary before filling YAML: - What biological process, complex, reaction chain, or reusable motif is the module? - Which genes/proteins are core members, and which are activation context, substrate supply, regulation, upstream/downstream biology, or separate modules? - Is this a concrete species/pathway instance or an abstract reusable motif? - Does the boundary have at least two substantive parts/roles/steps? If it collapses to one gene, one enzyme, or one reaction, do not create or retain a standalone `ModuleReview`; record it as pathway/gene curation and fold it into a broader module later. 3. Model the structure: - Put module-level process/complex/context terms on `module.concepts` and `module.context`. - Put molecular functions on leaf `annotons[].function`, not on a biological-process module just because the member protein has that MF.