odin-create-advanced

Use when the user wants to classify abstractions as useful, bad, or busy and keep one shallow level. Classifies each by whether its cooked form is easier than its raw form, and selects one shallow level. Don't use for tasks that require source or remote-system changes.

Use when a user wants to enumerate plausible designs, configurations, scenarios, and paths and diagram the field before choosing. Produces an exhaustive enumerated field and a diagram before any choice. Don't use for remote, credential, publish, deploy, or irreversible changes.

Use when a user wants adversarial stress-testing of a proposed architecture, structure, or shape. The agent attacks while the human defends, or the agent proposes while the human attacks, until the shape survives or breaks. Records the surviving shape as a decision. Not for tasks that require source or remote-system changes.

Use when the user wants a cybernetic flow design document for an interactive system. Specifies sensors, actuators, feedback paths, delays, and oscillation risk, and writes the design to a named local file. Not for implementing or deploying the system.

Use when a user wants a looser conceptual graph for exploratory work. Generates a freeform conceptual graph that the user can explore. Not for remote, credential, publish, deploy, or irreversible changes.

Use when asked to render documentation as an interactive, navigable HTML canvas. Fetches files, directories, or URLs, extracts headings and sources, and produces a self-contained HTML artifact with a table of contents. Not for writing or restructuring docs.

Use when a user wants to define failure states, recovery actions, bypasses, and degraded modes for a component during design. Produces a failure-state design document mapping every bounded failure state to its recovery, bypass, or degraded mode. Not for runtime recovery.

Use when a user wants to rebuild a design, organization, or API from primitives. Produces a first-principles rebuild spec naming primitives, structure, and open assumptions. Not for a perspective take — use from-*-perspective seats. Writes one local spec; no remote mutation.

Use when the user wants to replace a greenfield attempt with a clean pad carrying only verified requirements. Preserves the old attempt in VCS history. Not for rebuilding from primitives — use from-first-principle. Requires a committed, VCS-recoverable current attempt.

Use when asked to render a PR review in Cursor Canvas. Produces a local canvas artifact with risky hunks foregrounded. Not for standalone HTML rendering — use pr-review-canvas-html.

Use when asked to render a GitHub PR as a standalone review HTML page. Fetches PR data via gh API, renders diffs with move detection, and serves the artifact on a local port. Not for Cursor Canvas output — use pr-review-canvas.

Use when asked to create a presentation, pitch deck, or web deck from a topic and audience. Originates the narrative spine, slide content, and speaker notes, then applies design and runs an editorial QA pass. Not for formatting existing content into slides.

Use when asked to draft launch or promotion copy for a shipped feature across channels via /release-promotion. Returns every drafted channel as a labeled copy-pasteable block with a revision offer. Not for posting, publishing, scheduling, or committing — drafts only.

Use when the user says "give this rhythm", "vary the structure", or "the sections all read the same". Derives a rhythm constraint from the document's own sections or from a disclosed seed with random inputs. Not for judging an artifact's overall taste — use taste.

Use when a course needs numbered problem, solution, and explainer scaffolds. Creates type-specific files with non-colliding names, populates them, and validates with the course linter. Not for a CLI or Next.js project scaffold — use scaffold-cli or scaffold-nextjs.

Use when an explicit request asks to create a Sentry presentation, build slides, or make a deck. Scaffolds one self-contained, keyboard-navigable HTML file with real-data charts and Sentry branding. For general HTML artifacts use html; for PowerPoint use pptx.

Use when the user explicitly names snipgrapher and wants code rendered to a polished PNG, SVG, or WebP at an explicit local path. Probes the installed CLI for supported flags and writes only the named image file. Not for other renderers, publishing, or remote actions.

Use when a user wants to design an abstraction boundary that collapses a complex implementation into a simpler interface without leaking internal state. Produces a specification with the boundary, leak surface, escape hatches, and usage constraints. Stops before implementation.

Use when a trainer wants a training session documented as a compte rendu. Runs a structured interview, iterates a Markdown draft under user lead, then generates a .docx once after explicit content confirmation via python-docx. Not for remote, credential, publish, deploy, or irreversible changes.

Use when the user explicitly requests a slide deck by command, flag, or natural language. Generates a self-contained HTML deck in the diagrams directory with embedded CSS, JavaScript, keyboard navigation, and a progress indicator. Not for PowerPoint files; use pptx.

Use when asked to create an interactive HTML concept explainer with controls and live state, returned in a visualizer fence for sandboxed rendering. Validates controls via a local DOM trace, not a mental trace. Not for tasks that require source or remote-system changes.

Use when a user wants to lock greenfield architecture and interfaces early for coherent parallel execution. Produces a locked architecture document with module inventory, interface contracts, cross-cutting ownership, and open questions, distributed to execution teams as the coordination contract.