Curate shared components

Read the components section of .agents/STANDARDS.md. Preserve the flat model layout: components are reusable implementation units, never model categories.

Qualify candidates

Inventory current components before changing code:

uv run tsf component list
uv run tsf component match <operation-and-contract-terms> --json
uv run tsf component show <candidate>

Search model-local implementations for repeated defining operations. For each candidate, compare equations, tensor axes and shapes, normalization and residual order, masking, initialization, state, dtype/device behavior, outputs, and error conditions. Record a decision of reuse-existing, extract-new, keep-model-local; lexical or structural similarity is not enough.

For an explicitly requested repository-wide pass, use exact/normalized AST matches and recent model additions only to build a shortlist, then apply the same semantic review. First migrate duplicates to an already cataloged equivalent; create a new component only when no existing contract fits and at least two real consumers remain. A no-change pass is valid and preferable to a speculative abstraction.

Extract safely

Define the smallest paper-neutral API that preserves every consumer's behavior. Add or update its ComponentSpec, focused unit tests, and explicit model imports. Migrate consumers in reviewable groups without flag-driven branches that hide material variants. Keep attribution and explanatory comments when moving code. Regenerate src/models/_components/<name>/README.md with uv run python scripts/generate_resource_cards.py; do not hand-maintain a second component description outside the catalog contract and implementation docstrings.

Before deleting local copies, compare affected models on deterministic inputs and verify parameters, buffers, outputs, gradients, and serialization where relevant. If equivalence cannot be demonstrated, leave the variants local and document the reason instead of forcing an abstraction.

Finish with affected tests plus:

uv run tsf repo doctor --strict --models <Name...>
uv run tsf component audit
uv run tsf repo audit

Success requires a cataloged component with a current readable card, focused tests, unchanged consumer contracts, and no peer-model implementation imports. Report the inspected scope, decisions, affected consumers, and next candidates so a later explicit pass can resume without rescanning settled mismatches. This skill does not schedule or start background monitoring.