Skip to main content

attention-variants-from-papers

Implement paper-defined attention variants by extracting mechanism invariants, mapping tensor shapes, preserving module interfaces, validating numerical behavior, and integrating the custom attention into an existing transformer stack.

Informações da origem

Repositório
benchflow-ai/skillsbench
Última atividade na origem
30 de maio de 2026 às 04:55
Idioma detectado do SKILL.md
inglês
Estrelas
1.830
Forks
370

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
6 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
attention-variants-from-papers
description
Implement paper-defined attention variants by extracting mechanism invariants, mapping tensor shapes, preserving module interfaces, validating numerical behavior, and integrating the custom attention into an existing transformer stack.
# Attention Variants from Papers Use this skill when a paper changes how attention scores, branches, normalization, or head sharing work, but the module still needs to behave like a drop-in transformer attention block. ## Workflow 1. Read the paper for invariants, not names. Use [paper-to-implementation.md](references/paper-to-implementation.md) to extract the external contract, the changed computation, and the training-time constraints. 2. Build a shape ledger before coding. Use [shape-ledger.md](references/shape-ledger.md) to track projections, head grouping, branch count, and output width. 3. Choose the mechanism pattern. Use [mechanism-patterns.md](references/mechanism-patterns.md) for subtractive attention, branch mixing, learned gates, and extra normalization. 4. Preserve the module boundary. Keep the same input and output shape, mask semantics, positional encoding flow, and cache behavior unless the task explicitly changes them. 5. Validate in layers. Start with random-tensor smoke tests, then compare against a baseline attention path. Use [stability-and-validation.md](references/stability-and-validation.md). 6. Integrate into the stack last. Swap the new module into one transformer block, verify the residual path, then roll it through the full model. Use [transformer-integration.md](references/transformer-integration.md). ## Checklist - extract the paper's invariants before writing code - account for every reshape, branch, and repeat in a shape ledger - preserve output width at concatenation or output projection - apply masks and positional terms at the intended stage - confirm random smoke tests stay finite - compare unchanged behaviors against a baseline attention implementation ## Reference Map - [paper-to-implementation.md](references/paper-to-implementation.md): turn paper text into module invariants and coding decisions - [shape-ledger.md](references/shape-ledger.md): keep dimensions consistent while branch structure changes - [mechanism-patterns.md](references/mechanism-patterns.md): reusable patterns for nonstandard score composition and mixing - [stability-and-validation.md](references/stability-and-validation.md): numerical checks, smoke tests, and baseline comparisons - [transformer-integration.md](references/transformer-integration.md): wire the custom module into an existing transformer block
Ver no GitHub