Julius Brussee
- 38 skills
- 0 followers
- 2 weeks ago last updated
- ▌ Caveman Compress 2 · juliusbrusseeUltra-compressed communication mode (lite / full / ultra) that cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Use when the user requests "caveman mode", "less tokens", "be brief", or when output budget is tight.
- ▌ Loop Factory 2 · juliusbrusseeUse when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work, generating implementation prompts, or deciding next loop state.
- ▌ Review And Archive 2 · juliusbrusseeUse when reviewing active Loop Factory specs against the working tree, checking verification evidence, deciding ACCEPTED or CHANGES_REQUESTED, and archiving accepted specs.
- ▌ Backpropagate Specs 2 · juliusbrusseeUse when code changes should be scanned and reflected back into living specs, docs, or architecture notes without changing product intent.
- ▌ Caveman Browse · juliusbrusseeDrive web pages through the caveman-browse MCP tools (browser_snapshot, browser_act, browser_eval, browser_recover). Use whenever interacting with a web page, dashboard, or form through caveman-browse — it teaches the snapshot→act→verify loop, query-first discipline on large pages, and when to recover exact bytes.
- ▌ Plugin Creator · juliusbrusseeScaffold a complete cave plugin bundle — generates .cave-plugin/plugin.json manifest and the standard directory structure (commands/, skills/, agents/, themes/, hooks/). Use when a user wants to create, publish, or package a cave plugin for the marketplace. Triggered by "create a plugin", "scaffold a plugin", "/plugin create", or "new cave plugin".
- ▌ Cavekit Revision · juliusbrusseeTrace bugs and manual fixes back to kits and prompts; fix at the source so the iteration loop can reproduce the fix autonomously. Six-step revision process plus the single-failure backpropagation protocol. Use when a manual hot-fix has been applied, when convergence stalls, or when the same class of bug keeps reappearing.
- ▌ Cavekit Methodology · juliusbrusseeCavekit specification-driven development methodology — the Hunt lifecycle (Draft → Architect → Build → Inspect → Monitor) and how to apply it. Use when starting a Cavekit project, structuring an existing codebase as kits/plans, or routing between sub-skills.
- ▌ Cavekit Design System · juliusbrusseeHow to write and maintain DESIGN.md as the visual specification layer for Cavekit projects. Nine-section format, design tokens, accessibility, integration with kits/plans. Use when defining or revising visual identity, importing a third-party design system, or auditing UI code against design tokens.
- ▌ Cavekit Validation First · juliusbrusseeValidation-first design for Cavekit — every kit requirement must be automatically verifiable. Six-gate validation pipeline, phase gates, merge protocol, completion signals, acceptance criteria patterns. Use when designing acceptance criteria, wiring CI gates, or debugging why an agent is producing output that nobody can verify.
- ▌ Loop Factory · juliusbrusseeUse when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work to Codex or Claude agents, generating implementation prompts, or deciding next loop state.
- ▌ Review And Archive · juliusbrusseeUse when reviewing active Loop Factory specs against the working tree, checking verification evidence, deciding ACCEPTED or CHANGES_REQUESTED, and archiving accepted specs.
- ▌ Backpropagate Specs · juliusbrusseeUse when code changes should be scanned and reflected back into living specs, docs, or architecture notes without changing product intent.
- ▌ Deslopify · juliusbrussee bundleDe-slop pass for any text. Scans for the statistical fingerprints of AI writing (negative parallelism / "not X but Y", em-dash density, rule-of-three, false ranges, puffery vocabulary, uniform cadence, hedged both-sidesing), rewrites by meaning, then re-scans until the text is clean and sits in the right register for its genre: academic article, tweet, reddit post, email, blog, docs, marketing. Use when the user says "deslopify", "deslop", "de-slop this", "remove the AI tells", "humanize this", "make this not sound like AI", or invokes /deslopify. Also use before publishing any agent-drafted prose.
- ▌ Grill · juliusbrusseeCalibrated interrogation of a fuzzy idea before it becomes a spec. Asks one question at a time, recommends an answer, and lands each answer in §G (goal) or §C (constraints) — unknowns parked as `?` items, never guessed. The cheapest place to kill a bad idea is before §T exists. Triggers when the user has a vague idea, says "grill me", "stress-test this", "challenge my plan", "interview me before I spec", or invokes /ck:grill. Defers the actual write to the spec skill.
- ▌ Deepen · juliusbrusseeOptional design-improvement pass for when you have spare usage to drain. Finds the shallowest modules in the code the spec touches, researches a deeper design, and proposes refactors that shrink interfaces and hide decisions — behavior held constant, tests green before and after. Proposes §I/§V/§T edits, never silent rewrites. Triggers when the user says "deepen this", "improve the design", "this module feels shallow", "pull complexity down", "use spare budget on the codebase", or invokes /ck:deepen. Leans on the codebase-design skill's deep-module vocabulary when present.
- ▌ Review · juliusbrusseeAdversarial senior review of the spec before any code is written. Constructs a skeptical reviewer whose authority comes from the codebase, §R research, and live best-practice — then tries to REFUTE the spec, not rubber-stamp it. Every finding cites evidence (file:line or source); unverifiable ones are flagged. Survivors harden §V; the run ends in an explicit go / no-go gate. Triggers before building anything high-blast-radius, when the user says "review the spec", "red-team this", "is this plan sound", "senior review", or invokes /ck:review.
- ▌ Research · juliusbrusseeGather external knowledge the spec needs and distill it into §R — the durable research log — so build grounds in facts instead of hallucinating library behavior. Each finding cites a source; unsourced claims are flagged, never written as fact. Triggers when a spec decision hinges on a library/API/best practice the agent is unsure of, when the user says "research this", "what's the best lib for…", "check current best practice", or invokes /ck:research. Defers the §R write to the spec skill.
- ▌ Caveman Evidence Review · juliusbrusseeRead-only review of Caveman Cloud evidence: cost, Cave Score, workflows, traces, latency, errors, routing, savings. Use when asked what Caveman found or where LLM spend goes.
- ▌ Investigate First · juliusbrussee bundleDiagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.
- ▌ Caveman Discover · juliusbrusseeFind and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.
- ▌ Caveman Optimize · juliusbrusseeTurn a Caveman optimization observation into an operator-chosen candidate with a paired baseline evaluation. Use when asked to inspect or evaluate a Caveman optimization report. Needs explicit approval.
- ▌ Caveman Explore · juliusbrussee bundleRead-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line citations only; its reads stay out of main context.
- ▌ Verify And Stop · juliusbrussee bundleProve existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.
- ▌ Caveman Manage · juliusbrusseeInspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.
- ▌ Surgical Patch · juliusbrussee bundleFix bugs and small behavior changes at the narrowest responsible layer. Use when regression proof, preserved surrounding behavior, and task-relevant tests matter.
- ▌ Caveman Learn · juliusbrussee bundleAct on a Caveman learn report - review the ranked token sinks, apply cost-lowering fixes with per-edit consent, and report what those fixes returned. Use when asked to lower an agent's token cost, what caveman has saved, to trim a heavy CLAUDE.md, or to offload re-pasted context into cavemem.
- ▌ Caveman Setup · juliusbrusseeWire a repository through the Caveman Cloud gateway so every LLM request is measured, with no behavior change. Use for "set up caveman" or adding LLM spend observability.
- ▌ Safe Refactor · juliusbrussee bundleRestructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.
- ▌ Lean Build · juliusbrussee bundleBuild feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.
- ▌ Migration · juliusbrussee bundleImplement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback and preservation proof.
- ▌ Caveman · juliusbrussee bundleCompresses AI agent output tokens by up to 65% using a terse, article-free communication style while preserving full technical accuracy. Supports multiple intensity levels and auto-disables for security warnings or ambiguous instructions.
- ▌ Cavecrew · juliusbrussee bundleDecides when to delegate to compressed-output subagents (investigator, builder, reviewer) instead of using vanilla agents, saving main-context tokens across long sessions.
- ▌ Caveman Help · juliusbrussee bundleDisplays a quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode.
- ▌ Caveman Stats · juliusbrussee bundleShows real token usage and estimated savings for the current Claude Code session by reading the session log.
- ▌ Caveman Commit · juliusbrussee bundleGenerates ultra-compressed commit messages in Conventional Commits format with a subject line ≤50 characters and a body only when the 'why' isn't obvious.
- ▌ Caveman Review · juliusbrussee bundleProduces ultra-compressed, one-line code review comments that cut noise while preserving actionable signal. Each comment includes location, problem, and fix.
- ▌ Caveman Compress · juliusbrussee bundleCompress natural language memory files (CLAUDE.md, todos, preferences) into a concise format to save input tokens while preserving technical substance, code, URLs, and structure.