dotfiles

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.

Google Drive CLI for listing, searching, uploading, downloading, and sharing files and folders.

Create git commits. Use when committing changes, creating PRs, or preparing code for review.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Grilling session that challenges your plan against the existing domain model in CONTEXT.md and decisions in docs/adr/. Sharpens terminology and updates documentation inline as decisions crystallise. Use when stress-testing a plan against the project's established language and recorded decisions, not for general design grilling.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

Expert Ratatui 0.30+ TUI development patterns, idioms, and best practices. Use when building terminal UIs, working with Crossterm, creating components, handling events, or rendering widgets in Rust.

Audit existing Agent Skills for spec compliance, best-practice adherence, and description quality. Use when reviewing skills for correctness, identifying improvements, or validating skills before shipping. Always ground yourself in the official agentskills.io docs first — the standard is early and volatile.

Create well-formed Agent Skills following the agentskills.io specification and best practices. Use when creating new skills, refactoring existing skills, or extracting reusable patterns from completed tasks into portable skill directories.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants test-first development, or asks to follow a TDD workflow.

Speech-to-text transcription using Groq Whisper API. Supports m4a, mp3, wav, ogg, flac, webm.

Triage issues through a state machine driven by triage roles. Use when the user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

Fetch transcripts from YouTube videos for summarization and analysis.

Teach the user a new skill or concept, within this workspace.

Build Rust projects. Use when the user asks to build, or as a final validation gate before claiming a Rust task is complete. Run `cargo build` and `cargo test` before declaring any Rust code change done.

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.

Lint Rust code with clippy. Use before committing, reviewing, or when checking code quality. Catches style issues, common mistakes, and suboptimal patterns beyond what the compiler finds.

Run Rust tests. Use when testing, or as a validation gate before claiming a Rust task is complete. Run `cargo build` and `cargo test` before declaring any Rust code change done.

Google Calendar CLI for listing calendars, viewing/creating/updating events, and checking availability.

Gmail CLI for searching emails, reading threads, sending messages, managing drafts, and handling labels/attachments.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Turn the current conversation context into a Product Requirements Document and publish it to the project issue tracker. Use when the user wants to formalize a feature plan, create a PRD, or document requirements from a discussion.

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.