Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Cadet by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Cadet primitives. Handles single-source and multi-source migrations with a unified, deduplicated inventory.
Alias for /development-lifecycle. Full frontend workflow: understand -> plan -> grill -> implement (TDD) -> /go (verify -> ship). Use when doing any React/TypeScript/UI development task.
Spectral theory framework for analyzing population density dynamics of spiking neurons with refractoriness. Provides rigorous operator-theoretic methods for studying neuronal population dynamics, spectral characterization of Fokker-Planck operators, and transfer function derivation for networks with absolute refractory periods. Use when analyzing spiking neural network stability, oscillatory modes, or refractory effects on population dynamics.
Layered architecture with dependency inversion. Domain/Application/Presentation/
Infrastructure separation. For complex business logic, long-term maintainability,
testability. AVOID for simple CRUD apps or MVPs. Foundational pattern.
Use whenever you need to understand how this theme works — adding pages, managing content, configuring the site, using partials/components/modules, project architecture, scripts, or styling/theming (Tailwind v4, Bootstrap 5, or a hybrid — verify which). Use for ANY question about the structure, usage, or customization of the template or theme.
screenshot to new UI code. Primary owner: new UI reconstruction. Do not use for: locating existing source. Use when this role is selected by the Agent-Vorcl-Flow router.
Judge whether something actually produces value in a concrete scenario. Value is a beneficial relational property between subject and object, conditioned on the states of both sides, that only holds in a specific scenario. Typical uses: judging whether a value proposition holds, mapping a capability to a concrete use scenario, diagnosing why no one uses it or why they don't stick, clarifying how to position or state the value, assessing whether something is worth investing in, or judging whether you can borrow someone else's approach (e.g. "is this idea sound?", "does anyone actually want this?", "why did we roll it out and no one uses it?", "why do people try it once and never come back?", "can we copy what someone else did?"). When the thing being judged has a decision-maker (who pays / signs off) that is not the same as the actual end user (enterprise software, internal platforms, etc.), first state which side you're analyzing for and split the two value relationships to run separately.
Investigate sudden drops in organic traffic or rankings and run a structured forensic SEO incident response with triage, root-cause analysis and recovery plan.
Manage canonical task state through the task-ledger MCP server. Use when creating, reading, updating, or transitioning tasks, adding notes or artifact links, or querying task history. The MCP ledger is the authoritative task state system; repo markdown files are derived or legacy surfaces only.
Index and search code repositories, documentation, research papers, HuggingFace datasets, local folders, Slack workspaces, Google Drive, X (Twitter), and packages with Nia AI. Includes auth bootstrapping, Oracle autonomous research, GitHub live search, Tracer agent, dependency analysis, context sharing, code advisor, document agent, data extraction, filesystem operations, and generic connectors.
Resume any open PR — started by `om-auto-create-pr` or opened outside the pipeline. Claims it, resumes in an isolated worktree from the first unchecked step of its execution plan; a PR with no plan is adopted — the goal is reconstructed from its description, comments, review feedback, linked issues and diff, then executed. Usage - /om-auto-continue-pr <PR-number>
Use when refactoring code, reorganizing modules, renaming types, deleting old paths, or migrating architecture. MUST read before any structural code change. Prevents incomplete refactoring that silently breaks downstream consumers.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this,"...