菜单
Use when designing or refactoring bop runtime/storage paths to maximize APFS COW/compression and prefer standard Rust crates over custom infrastructure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when agents must write to .bop bundles safely and consistently without corruption.
Use when bop execution needs Auto-Claude MCP-style progress/status/discovery tracking.
Use when you need to map Auto-Claude MCP server logic to bop stages, workflows, and commands.
Use when a card or request includes a persona emoji (for example `🎯`, `🔒`, or `🚨`) and you need role-specific execution behavior with minimal token overhead.
Use when a bop stage needs external library/framework documentation lookup.
Use for desktop UI validation in bop QA stage when the target app is Electron.
| name | bop-apfs-tahoe |
| description | Use when designing or refactoring bop runtime/storage paths to maximize APFS COW/compression and prefer standard Rust crates over custom infrastructure. |
Keep bop as a filesystem-native workflow engine (not a database), while using proven libraries for common runtime concerns.
Target platform: macOS Tahoe and other APFS systems.
Treat the system as three primitives:
<id>.bop/) with spec + metadata.events.jsonl / OpenLineage payloads).Resolve library choices via references/rust_runtime_crates.tsv.
fs4 (or fs2 if already in tree)backofftracing + tracing-subscribertabled or comfy-tablesysinfoRule: do not implement a bespoke subsystem if a listed crate already covers it.
Resolve filesystem operations via references/apfs_ops.tsv.
ditto --clonecp -c on macOSdone|failed|merged):
ditto --hfsCompressioncp -R/cp -r for card copy paths on macOS.job, run, event, or ui.rust_runtime_crates.tsv before writing code.apfs_ops.tsv.renamecargo build./target/debug/bop doctor./target/debug/bop policy check --stagedjob/run/event/ui).