toverux

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Scan the session for compound-worthy learnings, then commit the working tree with a repo-appropriate, value-communicating message.

Garbage-collect the knowledge stores — audit docs/solutions/ and AGENTS.md against the current code.

Capture this session's durable learnings and route each to the right knowledge store, every write user-gated. Use at loop end when /commit's opening scan finds candidates, when /diagnosing-bugs closes out a fix, or when the user wants to capture, remember, or write down a learning, convention, gotcha, or preference.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to be grilled about a plan, wants a decision stress-tested, or when requirements are fuzzy before a spec is written.

Compact the conversation into a handoff document a fresh session can resume from.

Implement a spec or a single ticket, driving TDD at the seams agreed in the spec.

Drive and read Ionwake's `__ionwake*` window instrumentation hooks (`__ionwakeScene` on /play, `__ionwakeShipyard` on /shipyard, and the dev-only `__ionwake` debug flags) from outside the page via the Chrome DevTools MCP. Use to read live sim/scene/clock state, screenshot the running app, drive the shipyard, load ship models, inspect a ship schema, log the WebTransport wire, or keep a backgrounded tab stepping.

Compact the current conversation into a handoff document for another agent to pick up.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.

Interview the user relentlessly about a game design concept or design until reaching shared understanding, stress-testing the concept and resolving each branch of the decision tree.

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Implement a piece of work based on a PRD or set of issues.

How the game's UI engine (Coherent Gameface / Cohtml) differs from a real browser, and the workarounds this codebase already uses. Use when writing or debugging the HTML/CSS/JS UI under HallOfFame/UI/src, when a CSS property, HTML element, or Web API behaves unexpectedly in-game, or when the user mentions cohtml, gameface, or coherent.

Write and run the mod's C# unit tests off-engine (net48 + xUnit). Use when writing or running C# tests, when a test hits an engine-bound type (Unity native call, Colossal.Logging.ILog, HttpQueries) or throws TypeLoadException off-engine, or when deciding where to put logic so it stays testable (plain Services/, not ECS Systems/).

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Provides expert guidance on mise (mise-en-place) — a polyglot dev tool and environment orchestrator that manages runtimes, environment variables, and project tasks. This skill should be used when users ask about mise configuration (mise.toml), installing or switching tool versions (Node, Python, Go, .NET, etc.), the mise task runner, environment variable management, secrets with SOPS/fnox, backends (ubi, cargo, npm, aqua), Lua plugins, shell hooks, migrating from asdf/nvm/direnv, or debugging with mise doctor.

Write and run the mod's UI tests with bun (pure-logic tests and React component tests). Use when writing or running UI tests, when a component test must render against the real game bundle / cs2/* modules, when configuring value bindings or asserting outbound triggers in a test, or when the game bundle fails to load / react injection anchors drift after a game update.

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

Use when writing, editing, or reviewing TypeScript code to enforce strict typing, comment style, readonly usage, nullability, assertions, and string conventions.

Guide for using type-fest, the essential TypeScript utility types library by Sindre Sorhus (~84M weekly npm downloads). Use this skill whenever the user is working with TypeScript types and needs help with type transformations, deep object manipulation, string template types, JSON types, type guards, branded/tagged types, or asks about type-fest specifically. Also trigger when the user wants to make types readonly/writable deeply, merge object types, do case conversion at the type level, work with union/intersection transformations, validate forms with type constraints, normalize API responses, or needs stricter versions of built-in TypeScript utilities. If the user is writing complex TypeScript types by hand that type-fest already provides, suggest using type-fest instead.

Grill the user relentlessly about a plan, decision, or idea.