aperivue/architecture-zoo
> Choose a model architecture for a medical-imaging research question before scaffolding. Maps the task (classification, segmentation, detection, transfer), modality and dimensionality, labelled-data scale, and class imbalance to a shortlist of architectures, each grounded in its source paper with a when-to-use, a medical-imaging use, a reference implementation, the typical validation setup, and the matching model-scaffold template. Covers the foundational curriculum (ResNet, DenseNet, EfficientNet, ViT, Swin; U-Net, 3-D U-Net, Attention/Residual U-Net, nnU-Net (+ ResEnc/MedNeXt/STU-Net), Mask R-CNN; SAM/MedSAM, nnInteractive/VISTA3D interactive-3D, TotalSegmentator, BiomedCLIP, DINO/MAE/SimCLR; and graph neural nets — GCN/GraphSAGE/GAT/GIN/BrainGNN — for brain connectomes). It teaches archetypes and the task-to-architecture logic (including the "scale the CNN, new≠better" rigour caveat), not a live SOTA leaderboard.
npx skills add https://github.com/Aperivue/medsci-skills --skill architecture-zoo
This skill turns a medical-imaging research question into a paper-grounded architecture choice —
so the build starts from the right archetype (and a known validation setup) rather than from whatever is
fashionable, and the choice carries its source citation into the Methods. It is the front end of the
model-engineering lane: architecture-zoo (choose) → /model-scaffold (build) → `/model-validation
(validate)`.
It is advisory (Layer D): it writes a short decision note, never code or weights. The actual repo is
/model-scaffold. It describes archetypes and the task → family → constraint logic, not a live SOTA
leaderboard (SOTA churns; the logic does not).
transfer-learning question and want it grounded in the literature with a sensible default.
/model-scaffold./model-validation./model-evaluation + /analyze-stats./design-study; AI-vs-expert benchmark → /design-ai-benchmarking./mllm-eval.State the task (classification / segmentation / detection / transfer), the **modality +
dimensionality (2-D vs 3-D volume), the labelled-data scale** (events / structures, not just
images), label availability (lots / few / unlabelled pool), and constraints (class imbalance,
small structures, interpretability, deployment compute).
Open ${CLAUDE_SKILL_DIR}/references/index.md and follow task → constraints → default pick. It routes to
a family card.
${CLAUDE_SKILL_DIR}/references/classification.md — ResNet / DenseNet / EfficientNet / Inception /ViT / Swin / DeiT.
${CLAUDE_SKILL_DIR}/references/segmentation.md — U-Net / 3-D U-Net / V-Net / Attention & ResidualU-Net / nnU-Net / SegResNet / Swin-UNETR / Mask R-CNN.
${CLAUDE_SKILL_DIR}/references/detection.md — R-CNN family / Faster R-CNN + FPN / Mask R-CNN /RetinaNet / YOLO / DETR.
${CLAUDE_SKILL_DIR}/references/synthesis.md — Pix2Pix / CycleGAN / SPADE / diffusion (DDPM, latent) /VAE / fastMRI reconstruction.
${CLAUDE_SKILL_DIR}/references/foundation_models.md — SAM / MedSAM / MedSAM2 / TotalSegmentator /SegVol / BiomedCLIP / DINO / MAE / SimCLR / MoCo.
${CLAUDE_SKILL_DIR}/references/graph.md — GCN / GraphSAGE / GAT / GIN / BrainGNN for brainconnectomes & population graphs (integrate PyTorch Geometric / DGL; not scaffolded by model-scaffold).
Each card gives the paper, core idea, when-to-use, medical-imaging use, reference implementation, and the
typical validation/experiment setup for that architecture class.
Record decisions/architecture_choice.md: the task, the chosen architecture, its **source
paper, the reason against the constraints, the runner-up + why not**, and the matching
/model-scaffold template. Naming the source paper is mandatory; cite, never invent, any benchmark
number.
Carry the decision note to /model-scaffold (instantiate the template), then /model-validation
(split / validation design), /model-evaluation + /analyze-stats (metrics), and /write-paper
(the Methods cite the architecture's source paper).
decision note must carry that citation.
/search-lit); if uncertain, write [VERIFY] and ask.
ViT on a few hundred images, or 2-D slices for a volumetric structure) — the constraints in the
decision tree exist to prevent exactly that.
recommendation is the latest best.
architecture-zoo (this skill: choose, paper-grounded)
└─ model-scaffold (build the reproducible repo from the chosen template)
└─ model-validation -> model-evaluation -> write-paper (cite the source paper)
It does not build, train, evaluate, or rank live SOTA — it maps the research question to a defensible,
paper-grounded archetype and hands the choice to /model-scaffold.
Take aperivue/architecture-zoo from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.