Guided scenario for creating an OpenDesign plugin folder that can be installed into My plugins.
9881cffUse this scenario when the user wants to create their own OpenDesign plugin.
Produce a folder named generated-plugin/ in the active project workspace.
At minimum, the folder must contain:
SKILL.md with frontmatter and clear agent instructions.open-design.json with valid plugin metadata, od.kind, mode, task kind, capabilities, and inputs when needed.Add examples/, assets/, or other supporting files only when they help the plugin be used or reviewed.
docs/plugins-spec.md and the schema at docs/schemas/open-design.plugin.v1.json.SKILL.md as the canonical behavior description. open-design.json should describe how OpenDesign installs, applies, and presents that behavior.generated-plugin/
SKILL.md
open-design.json
examples/
assets/
The examples/ and assets/ directories are optional. Do not create empty directories just to match the sketch.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/od-plugin-authoring · pinned to the source commit
# Run from your project root
git clone https://github.com/nexu-io/open-design.git .skillboard-tmp
git -C .skillboard-tmp checkout 9881cff70e02be86c2a58130af512011ba23d4af
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/plugins/_official/scenarios/od-plugin-authoring" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/nexu-io/open-design.git .skillboard-tmp
git -C .skillboard-tmp checkout 9881cff70e02be86c2a58130af512011ba23d4af
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/plugins/_official/scenarios/od-plugin-authoring" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/od-plugin-authoring
Scanner static-checks@0.1.0 · commit 9881cff70e02. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.