dapih Guide the user through the Visualkan Controls, one step at a time, then start the run. Use this skill only when the user names it. A plain request to visualize something belongs to the visualkan skill.
Why this skill exists
The visualkan skill takes a flag for every Control, and several more besides. A user who does not know them has to read the documentation before every run. This skill replaces that reading with a short sequence of choices.
Step 1: Read the Control Catalog
Read references/controls.md from this skill's own directory. Resolve that relative path against the directory this skill was loaded from, not against the current working directory, and write it with forward slashes:
<this skill's own directory>/references/controls.md
The output lists every Control, every legal value, and the default.
Never write the value lists into this file, and never recite them from memory. The Control Catalog is generated directly from the code constants, so it cannot be out of date.
Step 2: Ask for the Controls
Ask one question at a time. Present the values as a numbered list. Mark the default. Accept a number or a name.
Offer this escape on every question: "Accept the remaining defaults." If the user takes it, stop asking and go to Step 3.
Ask in this order:
- Style. Show all seven, each with the one-line description from Step 1.
- Device. Ask this only if the user chose
mockup. Skip it otherwise. - Draw Level. Show the three values with their descriptions.
- Complexity. Show the three values with their Section counts.
Do not ask about the native Backend. When the user names no Backend, Step 1 of the visualkan skill detects the platform's own image generation tool and prefers it, at no cost, before this question ever matters. The confirmation block states which Backend won, so the user can still redirect it there.
Do not ask about Mode. Multi-frame runs call the image API three to five times, and a user who needs this skill cannot judge that cost. A user who wants multi-frame can pass --mode multi-frame to the visualkan skill.
Do not ask about --size, --output, or --prefix. The defaults are correct for almost every run.
Step 3: Ask for the Content
Ask what the user wants to explain. Accept any of these:
- A topic, in the user's own words
- A path to a file to read
- A Mermaid diagram, inline or as a
.mmdpath
Do not judge the answer here. The next skill tests whether the Content can fill the Sections that the chosen Complexity needs.
Step 4: Hand the run to the visualkan skill
Read the sibling skill file at ../visualkan/SKILL.md, which sits beside this one. Resolve that relative path against the directory this skill was loaded from, not against the current working directory, and write it with forward slashes:
<this skill's own directory>/../visualkan/SKILL.md
If that file does not exist, the visualkan skill was not installed beside this one. Stop and tell the user to install both skills with npx skills add dapih/visualkan.
Follow that file from Step 1b: Detect and parse Mermaid input, with the Controls and the Content that this wizard collected. Step 1b passes straight through when the Content is not Mermaid, and Step 2 follows it.
Start at Step 1b, not at Step 2, because Step 3 above accepts a Mermaid diagram. A handoff that starts at Step 2 carries that diagram into the analysis unparsed, and the nodes and edges never become Sections and Relationships.
Skip only the Content check at the top of Step 1, because this wizard already collected the Content. Still choose the route that Step 1 describes, because Step 4 and Step 7 both need it.
Then print this line, exactly as written, on a line of its own:
VISUALKAN-WIZARD-RUN
That token is the Handoff Token. Step 4 of the visualkan skill body requires it before it will confirm the plan. Print the token itself, not a description of it, and never omit it.
Do not construct the Image Prompt here. Do not call the image API here. The visualkan skill reads its own Style Template from its references/ directory, and one copy of that step is the point.
What this skill never does
- It never reads
OPENAI_API_KEY,GEMINI_API_KEY, orOPENROUTER_API_KEY. The confirmation block in the visualkan skill handles Backend detection. - It never generates an image before the user approves the plan. The approval step lives in the visualkan skill.
- It never copies the Control values or the Style Templates into this file. Two copies drift apart.