Od tune collab
Skill nexu-io/open-design/plugins/_official/scenarios/od-tune-collab
🎨 The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes, landing pages, dashboards, slides, images & video — real files, HTML/PDF/PPTX/MP4 export. 🤖 Claude Code / Codex / Cursor / Gemini / OpenCode / Qwen & 20+ CLIs via BYOK.
npx -y skills add nexu-io/open-design --skill od-tune-collabAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Default reference pipeline for the tune-collab taskKind — pick a direction, patch-edit the existing artifact, critique, hand off.
SKILL.md
1.1 KB, as published. Nobody here has run it
od-tune-collab (scenario)
Spec §1 / §10.1 / §21.5 / §23.3.3: the canonical "iterate on an
existing artifact" flow. Inherits parentArtifactId from the
project metadata so the produced artifact's
ArtifactManifest.parentArtifactId is set automatically — the
artifact lineage chain stays intact across multi-turn tune cycles.
Default pipeline
{
"stages": [
{ "id": "direction", "atoms": ["direction-picker"] },
{ "id": "patch", "atoms": ["patch-edit"] },
{
"id": "critique",
"atoms": ["critique-theater"],
"repeat": true,
"until": "critique.score>=4 || iterations>=3"
},
{ "id": "handoff", "atoms": ["handoff"] }
]
}
The handoff stage records handoffKind: 'patch' (or
'deployable-app' when the user opted in via
od plugin run --target deployable-app AND build-test ran
successfully somewhere upstream in the project's history).