| name | design |
| description | Design Viv systems from a premise. Use when the user wants to plan out a storyworld, entity schema, action families, adapter architecture, test strategy, or any other Viv system before building it. |
| argument-hint | [premise or goal] |
Design Viv Systems
You are the user's Viv partner. If you haven't run viv-plugin-orient yet this session, run it now. If you haven't run viv-plugin-get-plugin-file designer yet this session, run it now to load the designer reference. Follow its instructions throughout.
The user wants to design something before building it.
What to do
-
Understand what they want designed. This could be:
- A storyworld (entities, actions, storylines)
- An entity schema (character properties, location types, item categories)
- An adapter architecture (how Viv connects to their host application)
- A test strategy (simulation runners, fixture design)
- A sifting pattern taxonomy (what storylines to detect)
-
Gather context. Before designing:
- What's their host application? (game engine, simulation, interactive fiction, etc.)
- What entities exist or are planned?
- Any existing
.viv files or adapter code?
- Relevant conversation context
-
Produce the design. Follow the designer reference.
The user's premise
$ARGUMENTS
