Load BIDS (Brain Imaging Data Structure) conventions into context. Auto-invoke when the user is working with neuroimaging files, asks about BIDS naming or structure, mentions entities like sub/ses/task/run, asks about JSON sidecars for MRI/fMRI/DWI/EEG/MEG/PET, or references a bids/ dataset directory. Use when validating filenames, suggesting sidecar fields, or organizing data.
Load and apply Brain Imaging Data Structure (BIDS) conventions when working with neuroimaging datasets. Use the reference files below to answer questions, validate filenames, suggest sidecar metadata, and guide dataset organization.
${CLAUDE_PLUGIN_ROOT}/references/entities.md${CLAUDE_PLUGIN_ROOT}/references/datatypes.md${CLAUDE_PLUGIN_ROOT}/references/sidecars.mdLoad the relevant reference(s) before answering. Load all three when the question spans multiple aspects of the spec.
bash ${CLAUDE_PLUGIN_ROOT}/scripts/validate.sh <dataset-path>BIDS_SCHEMA=/path/to/schema.json bash ${CLAUDE_PLUGIN_ROOT}/scripts/validate.sh <dataset-path>bash ${CLAUDE_PLUGIN_ROOT}/scripts/validate.sh <dataset-path> --schema <path-or-url>pip install bids-validator-denosub always; task for func/beh/eeg/meg).IntendedFor is present and paths are
relative to the subject directory.dataset_description.json, README, participants.tsv) exist or should exist.
Note that scans.tsv (per-subject scan log) is recommended for flagging bad scans.
6b. If a func datatype is present or described, check for corresponding _events.tsv
files (one per task run). These are required for all functional task data and follow
the same entity pattern as the BOLD file but with the _events.tsv suffix.derivatives/<pipeline>/ outside the raw BIDS root, and use desc and
space entities to distinguish processed variants.