Agent skill · product strategy · nexu-io

od-default

Hidden fallback scenario for free-form Home prompts. Infer the task type and ask only when routing is materially ambiguous.

Why this skill is useful

Adds a structured fallback mechanism for ambiguous user prompts, improving task routing accuracy.

What it needs

About 2k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.

What this skill does

od-default (hidden scenario) This plugin runs only when the user types a free-form Home prompt without choosing one of the visible category chips. It is the design-engine fallback, not a visible catalog entry. Route first; clarify only when needed Infer the task type from the user's brief and known conversation context. When one route is reasonably clear, bind it and continue directly to that OpenDesign flow. A free-form Home prompt, a first turn, or the presence of a discovery stage does not by itself require a question form. Emit the form below only when two or more routes remain materially plausible and choosing the wrong one would change the delivery format. Localize every user-facing string to the user's chat language, but keep ids, types, option values, and the ordered taskType options stable. Set defaultValue to the stable value of the route you recommend so the user can submit unchanged; the example below recommends prototype, but replace it with the inferred route value before emission. You may add at most two other unanswered questions, and only when their answers are also required before useful work can begin; never restore a fixed discovery checklist. After the answer When the user replies with [form answers — task-type], bind the chosen task type as authoritative, match the stable [value: ...] token rather than the localized label, and continue: prototype (Prototype): run the normal new-generation prototype flow. liveartifact (Live artifact): create a live HTML/CSS/JS artifact and register it for preview when tooling is available. slidedeck (Slide deck): follow the deck workflow and framework rules. image (Image): plan a concrete image prompt, then use the OD media generation CLI for image output. video (Video): plan shots, duration, aspect, and motion, then use the OD media generation CLI for video output. hyperframes (HyperFrames): create HTML-driven motion frames or a HyperFrames-ready motion artifact before rendering/exporting. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills nexu-io/od-default

View the source on GitHub

Browse the @skills marketplace