菜单
Use when writing or revising HCP / Litany protocol RFCs (Litany Wire, Votive Frames, .hcplang, hcpbin) under protocol/rfcs/ — enforces the RFC structure, vocabulary, and cross-links. Trigger on "HCP", "Litany", "Votive Frame", ".hcplang", "hcpbin", "RFC", "wire protocol".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Use to drive an RFC, feature, or PR end-to-end (research → spec → scaffold → implement → test → integrate) by fanning out single-purpose subagents in dependency-ordered waves. The orchestrator decomposes, dispatches, gates, and merges; it never writes code itself. Trigger on "/subagent-driven-development", "SDD", "fan-out implement", "drive this RFC/PR e2e", "subagent fan-out".
CUC (Caveman Ultra Chinese) — ultra-compressed communication mode. Cuts token usage ~75% while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "cuc mode", "caveman mode", "use cuc", "less tokens", "be brief", or invokes /cuc. Also auto-triggers when token efficiency is requested.
Use when asked to export, scrub, share, or archive a transcript of the current chat/session as a clean reasoning conversation. Produces a PII-scrubbed, enriched USER:SYSTEM transcript reconstructed from conversation context (not from disk — the live session transcript is often not flushed locally). Trigger on "transcript", "scrub session", "session export", "cleaned conversation", "reasoning transcript", "share this chat".
vaked-optitron — a singularity-native crawler whose ONLY job is to surface ONE novel, proven, cross-checked, independently-confirmed compiler / allocator / Zig / Rust / Vaked optimization per run, or nothing. It abstains by default; only a finding that clears a strict gate (>=2 independent sources + repo/ledger novelty + a REPRODUCED micro-benchmark + a confidence threshold) is acted on, by opening an `agent`-labelled GitHub issue (the swe_af trigger) and announcing to Mastodon + Telegram. Runtime: tools/optitron/ (Go/Eino binary, OpenRouter). Trigger on "optitron", "find an optimization", "optimization crawl".
Compose and publish updates to the self-hosted Mastodon (social.crabcc.app) in the voice of "Carcin", the crabcc dev-feed persona. Use when the user says "toot", "post to mastodon", "share this", "post an update", or wants a fix/pattern/anecdote published. Drafts with google/gemma-4-31b-it, publishes via the social-post workflow.
| name | hcp-rfc-author |
| description | Use when writing or revising HCP / Litany protocol RFCs (Litany Wire, Votive Frames, .hcplang, hcpbin) under protocol/rfcs/ — enforces the RFC structure, vocabulary, and cross-links. Trigger on "HCP", "Litany", "Votive Frame", ".hcplang", "hcpbin", "RFC", "wire protocol". |
HCP is the harness control / IPC protocol; Litany is its reference implementation. RFCs are the normative source of truth — overview docs summarize, RFCs decide.
| Concern | Path |
|---|---|
| RFCs (normative) | protocol/rfcs/NNNN-*.md |
| Overview + vocabulary + roster | docs/protocol/README.md |
| Code subtree | protocol/ |
0001-hcp.md, 0002-…. One concept per
RFC once the surface grows; 0001 is the umbrella.docs/protocol/README.md; if you add a term, add it in both places..hcplang, hcpbin, and the daemons chapterd/preceptord/reliquaryd/
candled/petitiond/oraclefd, tools litanyctl/litanydump/litanyfmt/
litanyreplay. Don't coin synonyms.preceptord (authority) and hash-chained eventd
(tamper-evidence).docs/runtime/README.md) and, where transport
choices matter, the MirageOS unikernel note (vsock).docs/protocol/README.md if the RFC changed it.