菜单
Use when working anywhere in the SIMPLE repository and you need a high-level architectural map of the cryo-EM platform, including the relationship between production executables, the src core library, src/main subsystems, tests, scripts, docs, and the NICE layer.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when working in SIMPLE's src/main/nano subsystem, including nanoparticle and molecule data structures, graphene and time-series helpers, and the SINGLE-specific domain logic that supports liquid-cell and nanoparticle workflows.
Use when working on SIMPLE's abinitio2D workflow and its cluster2D stages, including 2D search strategies, probabilistic 2D sampling, class-average restoration, distributed partial class-average assembly, online matcher particle I/O, project updates, and streaming/rejection helpers.
Use when working on SIMPLE's model_cavgs_rejection application, simple_cavg_quality feature-space selector, class-average quality selection, quality_mode=analyze outputs, cavgs_quality feature/reference tables, chunk vs pool rejection tuning, or microchunk quality-vector integration.
Use when studying, explaining, or modifying SIMPLE's fractional-update and trailing-reconstruction workflow, including update_frac sampling, sampled/updatecnt bookkeeping, matcher reconstruction I/O, partial even/odd reconstruction handoff, rec3D/volassemble ownership, downsampling compatibility, obsfield mirrors, and stage-to-stage previous-reference contracts.
Use when working in SIMPLE's src/main/stream subsystem, including online/mini-stream orchestration, chunk and microchunk processing, staged pipeline steps, watchers, queue/message definitions, and streaming variants of preprocessing and cluster2D workflows.
Use when working on SIMPLE's streaming microchunk class-average rejection, simple_microchunked2D lifecycle sentinels, pass-1/pass-2/refchunk/match generation, skip_pass_2 behavior, simple_cluster2D_rejector criteria, or boundaries with model_cavgs_rejection.
| name | simple-architecture |
| description | Use when working anywhere in the SIMPLE repository and you need a high-level architectural map of the cryo-EM platform, including the relationship between production executables, the src core library, src/main subsystems, tests, scripts, docs, and the NICE layer. |
Use this skill first when the request spans multiple parts of SIMPLE.
SIMPLE is a scientific application platform, not a narrow library.
production/ contains thin executable entrypoints such as simple_exec, single_exec, simple_stream, simple_test_exec, and simple_private_exec.src/ builds one large static core library.src/main/ contains most application/domain logic.src/fileio/, src/utils/, and src/defs/ provide shared infrastructure.doc/ contains architecture and policy notes that are often more useful than comments in code.nice/ is the optional web/UI layer.Read these first for end-to-end flow:
production/simple_exec.f90src/main/apis/simple_exec_api.f90src/main/simple_cmdline.f90src/main/ui/simple_ui.f90src/main/params/simple_parameters.f90src/main/simple_builder.f90The common pattern is:
executable -> API aggregator -> UI/CLI lookup -> exec router -> commander -> strategies/domain objects -> file/project/image/reconstruction objects
CMakeLists.txt, src/CMakeLists.txt, production/CMakeLists.txtREADME.md, doc/code_overview/code_base_map.mddoc/policies/*.md, doc/refactoring_notes/*.mdsrc/main/exec as routing/orchestration.src/main/commanders as command objects and high-level workflow owners.src/main/strategies as algorithm/policy execution layers.src/main/image, project, ori, pftc, volume, nu_filt,
params, ctf, motion, and opt as core scientific subsystems.refine3D spans ui, exec, commanders, strategies, volume, project, pftc, and ori.cluster2D spans ui, exec, commanders, strategies, class, image, project, and stream.stream, project, motion, pick, ctf, and nice.