← ClaudeAtlas

assembly-referencelisted

Use when reviewing assembly for known anti-patterns, weighing contested questions (hand-written asm vs compilers, CISC vs RISC, fixed-width SIMD vs scalable vectors, AVX-512's design, whether and which ISA to learn first), checking whether an ISA or microarchitecture claim is still current (snapshot verified August 2026), finding the authoritative vendor manuals, performance references, books, and people, or needing the quick-reference numbers, first moves, and hand-written-assembly review checklist. Companion to the other assembly-programming skills.
adammatthewsteinberger/vibey-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill adammatthewsteinberger/vibey-skills
# Assembly Programming: Anti-Patterns, Contested Questions, Currency, and Canon > **Part 4 of 4** of the *Assembly Programming* reference (plugin `assembly-programming`), covering §15–§20. Sibling skills: `assembly-fundamentals-and-isas` (§0–§5), `assembly-toolchain-performance-and-simd` (§6–§10), `assembly-systems-crypto-and-inline` (§11–§14). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill. > > **Currency:** Verified August 2026. See §17 below for the currency snapshot and what goes stale first. > **How to read this.** Reference, not tutorial. Sections are independent. Three markers: > - **[DURABLE]** — machine organization, algorithms, or a lesson that has held since the > 1970s. Does not expire. > - **[ISA]** — specific to x86-64, AArch64, RISC-V, or a particular microarchitecture. > Verify against the vendor's current manual. > - **[CONTESTED]** — practitioners genuinely disagree, usually about how much hand-written > assembly is justified. > > **⚠️ GOTCHA** boxes mark the mistakes that produce silent corruption, ABI violations, > or code that is slower than the C you replaced. > > **The three framings that organize everything below:** > 1. **The instruction set is an interface, not the machine.** The CPU you're actually > programming is out-of-order, superscalar, speculative, and cached. Your instructions > are decoded into µops, reordered, and executed in parallel. Reasoning about assembly >