Guide safe inline assembly usage in UMRS Rust projects.
npx skills add https://github.com/jamieadams-nerd/umrs-project --skill asm-guidance
Please help me install this Agent Skill. Skill: asm-guidance Source: https://github.com/jamieadams-nerd/umrs-project/tree/main/.claude/jamies_brain/archive/asm Command: npx skills add https://github.com/jamieadams-nerd/umrs-project --skill asm-guidance
Provides detailed guidance on when and how to write inline assembly in Rust for UMRS projects. Use this skill to prevent unsafe ASM usage and to ensure safe, verifiable integration with core::arch intrinsics.
Review the core::arch alternatives, verify CPU features, and then only use raw asm! with full safety documentation.
High-intent search queries and answers about installing and using this skill.
Inline assembly in Rust is needed when you require low-level CPU control that core::arch intrinsics cannot provide. You should use it only after verifying that no portable intrinsic alternative exists for your specific hardware operation.
To safely use asm! blocks in Rust, apply safety gating by checking core::arch first, verifying CPU feature availability, and documenting your raw assembly blocks with provided templates before committing.
You should use core::arch intrinsics in Rust whenever possible because they provide safe, verifiable access to CPU features. Raw asm! blocks are a last resort when no intrinsic covers your specific instruction set requirement.
Selecting the right options() for Rust inline assembly involves using a dedicated selection guide to configure compiler constraints. This ensures your asm! block interacts safely with the compiler's register and memory allocation.
global_asm! in Rust bypasses many compiler safety checks and requires strict safety gating. You must verify CPU feature availability and document the block fully before introducing raw global assembly into your project.
You cannot safely use Rust inline assembly without verifying CPU feature availability. Checking target CPU support is a required step to prevent runtime crashes and ensure your core::arch intrinsics or asm! blocks execute correctly.
lywa1998Analyze unsafe Rust blocks and FFI interfaces for safety invariants.
yumazakDetect unsafe Rust patterns and enforce safety invariants across codebases.
ahravAudit Rust unsafe code for safety invariants, performance evidence, and test coverage.
qualcommConvert ARM64 NEON inline assembly to C/C++ intrinsics with verification.
