القائمة
Use when agents must write to .bop bundles safely and consistently without corruption.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when designing or refactoring bop runtime/storage paths to maximize APFS COW/compression and prefer standard Rust crates over custom infrastructure.
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-bop-integrity |
| description | Use when agents must write to .bop bundles safely and consistently without corruption. |
Guarantee .bop writes are deterministic, atomic, and schema-safe.
meta.json.running/.bop commands over manual filesystem mutation.references/write_protocol.md.bop meta set <id> --workflow-mode <mode> --step-index <n>, not ad-hoc edits.pending/ as quarantine-enforced: invalid meta.json is moved to failed/ by dispatcher.links.md, Logs.webloc, and Session.webloc as system-managed card UI artifacts.ditto --clone or cp -c); do not add plain cp -R/-r fallback for card paths.ditto --hfsCompression (transparent, idempotent, no adapters/converters).Use only stage-allowed files from references/allowed_writes.tsv.
bop inspect <id> must parse and show valid stage/meta.jq . <meta.json> must succeed.bop meta set ... is the canonical mutation path for workflow routing metadata.bop policy check --staged before merge/integration.