Smart Connections Collection Pipeline

Use this skill when changing how Smart Connections collections, items, or actions normalize params, score and filter results, or preserve pinned and hidden-result semantics across the pipeline.

Critical

• Use this skill only for pipeline changes in src/collections/**, src/items/**, src/actions/**, and the supporting utilities in src/utils/**.
• Never change the order of the pipeline in src/items/connections_list.js: pre_process(params) → filter_and_score(params) → post_process(results, params) → merge_pinned_results(...).
• Preserve hidden-result filtering and frontmatter include/exclude behavior. Do not bypass src/utils/filter_hidden_results.js or src/utils/merge_pinned_results.js.
• Keep src/actions/connections-list/pre_process.js side-effect free except for mutating params with defaults.
• If settings are added or renamed, wire them through src/collections/connections_lists.js using the same key names the pipeline already reads. Do not create a separate settings surface unless the existing collection settings object already exposes it.

Instructions

1. Identify the pipeline stage that owns the requested behavior.

   • Use src/actions/connections-list/pre_process.js for default params and normalization.
   • Use src/items/connections_list.js for filtering, scoring, and result merging.
   • Use src/collections/connections_lists.js for collection-level settings.
   • Use src/utils/merge_pinned_results.js, src/utils/filter_hidden_results.js, and src/utils/connections_list_item_state.js when the behavior depends on pinned/hidden state.
   • Verify the change belongs to one of those stages before proceeding to Step 2.

2. Update src/actions/connections-list/pre_process.js first when the request adds or changes defaults.