Write or edit EastGuard design and architecture documentation — roadmaps, phase design docs (like D1–D6 in docs/), mental-model explainers, subsystem walkthroughs — in the project's concept-focused house style. Use this skill whenever creating, updating, or reviewing any design / architecture / conceptual doc for this project, even when the user just says "write the D5 doc", "document this subsystem", "update the roadmap", "explain how X works in a doc", or "make a diagram doc for Y". The style: describe concepts and the *why*, grounded in the real implementation, without leaking exact code identifiers (struct / enum / method / field / variable names) unless the name is shared domain vocabulary that aids understanding. This does NOT apply to .claude/rules/ invariant specs, which intentionally name exact types and methods because they are code contracts.
How to build a new actor following EastGuard's architecture pattern. Use this skill whenever creating a new component, service, or subsystem that needs to process events asynchronously. Also use when the task involves designing a new state machine, wiring up channels between components, integrating with the timer system, or adding a new actor to the startup sequence. Even if the user just says "add a new component for X" or "we need a service that does Y", this skill has the full construction workflow. Covers the sync-first design, actor boundary, flush protocol, ticker integration, and startup wiring.
How to define Rust enum command/event types using the tuple-variant + named-struct pattern with `impl_from_variant!`. Use this skill whenever defining new enums for commands, events, messages, or any dispatch-style enum where variants carry structured data. Also use when refactoring existing inline-field enum variants into this pattern.
Code review guidelines. Use when reviewing a PR, performing code review, or checking code quality
Enforces using `gh api` REST endpoints instead of `gh` CLI subcommands for ALL GitHub interactions (reads and writes) in the east-guard repo. Use this skill whenever you're about to run any `gh pr`, `gh issue`, `gh release`, `gh repo`, or `gh label` command — even for listing or viewing. Also use when the user asks you to check PRs, create issues, update labels, post comments, or any other GitHub operation. This applies to the f-rustrated/EastGuard repository specifically.