executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
layers-and-modelsUse FLA layer, module, and Transformers model APIs for attention replacement, model construction, generation, training, and evaluation workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about constructing or smoke-checking Flash Linear Attention (FLA) layers, fused modules, or Transformers-compatible causal language models.
fla.layers, such as GatedLinearAttention or KimiDeltaAttention.transformers.AutoModelForCausalLM.from_config(...) and config classes from fla.models.attn field.RMSNorm or FusedLinearCrossEntropyLoss in model/loss code.references/api-reference.md for import surfaces, verified signatures, config knobs, return shapes, and known constraints.references/model-workflows.md for attention replacement, tiny AutoModelForCausalLM.from_config construction, hybrid attention plans, fused losses, generation, training, and evaluation recipes.references/troubleshooting.md before changing code.python scripts/smoke_layer_model.py --help
python scripts/smoke_layer_model.py --device cpu
Use --device cuda --require-cuda only when CUDA is intentionally part of the check.
Import config classes from fla.models, not from top-level fla:
from fla.models import GLAConfig, KDAConfig
from transformers import AutoModelForCausalLM
model = AutoModelForCausalLM.from_config(GLAConfig())
Top-level fla exports many layer/model classes when optional imports succeed, but it deliberately omits names ending in Config.