메뉴
Create and edit Obsidian JSON Canvas (.canvas) files — visual node/edge graphs for spatial note organization. Use when working with .canvas files or when the user asks to create a visual map, diagram, or canvas in Obsidian.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Mine architecture decision records (ADRs), gotcha files, runbooks, and docs/archive for cross-project lessons that warrant ai-playbook canonical specs. Use when a project lacks a populated retros/ directory but has equivalent material in other forms.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Orchestrate the canonical task↔PR↔release flow end-to-end. Two modes — `/dev-flow start <description>` scaffolds an OpenSpec change + branch + (optional) worktree + git hook ready for commits; `/dev-flow ship` validates the current branch + pushes + opens PR + monitors CI. Use whenever you start any non-trivial change in a playbook-consuming project. LLM-agnostic — works for Claude Code, Cursor, Antigravity, Gemini CLI, OpenCode, and humans.
Implement an OpenSpec change in parallel using multiple subagents (one per disjoint task group inside the same slice). Use when the slice's tasks.md has ≥2 task groups with disjoint write-paths AND >30 min of parallelisable work. For sequential implementation use openspec-apply-change instead.
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
| name | json-canvas |
| description | Create and edit Obsidian JSON Canvas (.canvas) files — visual node/edge graphs for spatial note organization. Use when working with .canvas files or when the user asks to create a visual map, diagram, or canvas in Obsidian. |
| model | haiku |
| allowed-tools | Read, Edit, Write |
Extension: .canvas — JSON structure with nodes, edges, and groups.
{
"nodes": [],
"edges": []
}
{
"id": "unique-id",
"type": "text",
"text": "# Heading\n\nMarkdown content here",
"x": 0,
"y": 0,
"width": 400,
"height": 200,
"color": "1"
}
{
"id": "unique-id",
"type": "file",
"file": "folder/Note Name.md",
"x": 500,
"y": 0,
"width": 400,
"height": 300
}
{
"id": "unique-id",
"type": "link",
"url": "https://example.com",
"x": 0,
"y": 300,
"width": 400,
"height": 200
}
{
"id": "group-id",
"type": "group",
"label": "Group Title",
"x": -50,
"y": -50,
"width": 600,
"height": 400,
"color": "6"
}
{
"id": "edge-id",
"fromNode": "node-id-1",
"fromSide": "right",
"toNode": "node-id-2",
"toSide": "left",
"label": "Optional label",
"color": "2"
}
fromSide / toSide: "top", "right", "bottom", "left"
Predefined: "1" red, "2" orange, "3" yellow, "4" green, "5" cyan, "6" purple
Custom: "#ff0000" (hex)
Use short unique strings: "node-1", "concept-auth", "group-backend".
IDs must be unique within the file.