القائمة
Use when a card or request includes a persona emoji (for example `🎯`, `🔒`, or `🚨`) and you need role-specific execution behavior with minimal token overhead.
التثبيت باستخدام 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 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 bop stage needs external library/framework documentation lookup.
Use for desktop UI validation in bop QA stage when the target app is Electron.
| name | persona-emoji |
| description | Use when a card or request includes a persona emoji (for example `🎯`, `🔒`, or `🚨`) and you need role-specific execution behavior with minimal token overhead. |
Route one emoji to one persona skill and execute that role's mandate, deliverables, guardrails, and escalation rule.
<emoji>-<slug>.bopmeta.labels includes kind=persona and persona=<emoji>rg "^<emoji>\t" ../emoji-index/references/emoji_skill_index.tsvskill_path and follow that skill only.meta.id stable and independent from emoji prefix.rg "^<emoji>\t" references/personas.tsv<emoji> <role>: <mission>.Plan: concrete next actions.Checks: validation and acceptance checks.Handoff: what next role/persona needs.Handoff, do not blend mandates.references/personas.tsv