メニュー
Fast Rust compilation check. Use during active coding for quick type-check feedback without full codegen. Prefer over `cargo build` when you only need to verify types, borrows, and syntax.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cargo-check |
| description | Fast Rust compilation check. Use during active coding for quick type-check feedback without full codegen. Prefer over `cargo build` when you only need to verify types, borrows, and syntax. |
cargo check
cargo check --workspace
cargo check -p <package>
cargo check --release
--workspace checks all packages; --all is deprecated — always use --workspace.cargo build (skips codegen) but does not verify linking.cargo build before claiming done.--all-targets includes tests, benches, and examples.Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Create software architecture diagrams using the C4 model (Context, Containers, Components, Code). Applies Simon Brown's diagramming principles: titles, legends, directional arrows, explicit text, abstractions-first. Use when user asks for architecture diagrams, system diagrams, C4 diagrams, or wants to document software structure.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Query the cerebro cortex knowledge base for project context, journal entries, intent/goals, TODOs, and statistics. Use when the user asks about their projects, wants to read journal entries, check goals/intentions, search for TODOs across repos, or get an overview of their activity data. Also use when browsing what the user has been working on across their side projects.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.