donaldfilimon/abi / .agents/skills/gpu
gpu
VerifiedPlan abi GPU/backend work — Metal on macOS, deterministic CPU fallback, and disclosed capability-only CUDA/Vulkan/ANE rows. Use when asked about GPU/backends, why accelerated=false, or when planning backend work. Routes to backend-diagnostics and abi-superpower-gpu and never promotes a compiled adapter to executed acceleration.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
SKILL.md
View on GitHub---
name: gpu
description: Plan abi GPU/backend work — Metal on macOS, deterministic CPU fallback, and disclosed capability-only CUDA/Vulkan/ANE rows. Use when asked about GPU/backends, why accelerated=false, or when planning backend work. Routes to backend-diagnostics and abi-superpower-gpu and never promotes a compiled adapter to executed acceleration.
---
# gpu
Entry point for abi's GPU/backend surface (`crates/abi-gpu/src/` + the four
honest-stub feature modules). Routes to specialists:
| You want to… | Use |
| --- | --- |
| Report GPU/accelerator/shader/MLIR status + compute matrix | `backend-diagnostics` |
| Deep-dive the GPU/Metal superpower | `abi-superpower-gpu` |
## Honest status (trust the source flags over any prose)
- **Metal DOT is real when initialized** through `crates/abi-gpu`; failed or
unavailable initialization degrades deterministically to CPU.
- **Capability-only rows** must report `initialized=false`, `executed=false`,
and `runtime_verified=false` until runtime evidence exists. CUDA/Vulkan remain
feature/target compile work, not local runtime proof on this Mac.
- **ANE/CoreML evidence is request plus successful inference**, not proof of ANE
residency. Keep that distinction in capability output and documentation.
## Hard rule
Do not claim native dispatch from compilation or availability alone. Require an
initialized, executed, runtime-verified state and preserve CPU oracle parity.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |