菜单
Project rules for future agents working on conU. Use when editing conU architecture, Rust implementation, CLI behavior, daemon/runtime code, protocol design, relay behavior, privacy boundaries, agent gateway behavior, or phase planning.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use conU as an external agent communication tool. Read when an agent needs to install conU, register itself, send or receive local messages, use a hosted relay, inspect inbox/receipts, or operate within conU's payload privacy rules.
Build and maintain the conU Rust CLI, daemon, protocol, agent gateway, relay, SDK, and project documentation. Use when working inside the conU repository on architecture, implementation, planning, agent communication, privacy, CLI UX, networking, runtime behavior, or future-agent handoff.
Review conU privacy, security, trust, encryption, payload opacity, logging, telemetry, relay, IPC, SDK, CLI watch, and agent permission behavior. Use for security-sensitive implementation and before merging changes that affect communication, storage, identity, network transport, or observability.
Understand and maintain the conU repository structure, project memory, file organization, implementation boundaries, and future-agent onboarding. Use at the start of repository work, when adding folders/files, when reorganizing code or docs, or when a future agent needs to understand where things belong.
Project runtime and protocol memory for conU. Use when future agents need to understand the conU product shape, runtime flow, protocol layers, CLI goal, build order, and how agents should communicate through conU.
Review conU changes before pull request, branch merge, or merge to main. Use for pre-merge checks, PR readiness, code review, branch hygiene, validation, plan.md updates, privacy-safe output checks, and deciding whether changes are safe to merge.
| name | conu-rules |
| description | Project rules for future agents working on conU. Use when editing conU architecture, Rust implementation, CLI behavior, daemon/runtime code, protocol design, relay behavior, privacy boundaries, agent gateway behavior, or phase planning. |
Agents own the conversation.
conU owns the connection.
Never expose private payloads in:
The CLI may show metadata:
from, to, route, latency, stream id, byte count, packet count, delivery state
The CLI must not show:
message text, reasoning, memory, tool results, file contents
Every future agent must read architecture.md and plan.md before implementation, then update plan.md after completing a phase.
Before opening a PR or merging to main, use .agents/skills/conu-pr-guardian/SKILL.md.
For any protocol, networking, relay, storage, logging, telemetry, CLI watch, SDK, IPC, encryption, identity, permission, or trust change, also use .agents/skills/conu-security-guardian/SKILL.md.
Never recommend merge if private payloads can appear in CLI output, logs, telemetry, relay storage, or tests as real content.