This skill enables Claude Code to create and edit valid JSON Canvas files (.canvas) used in Obsidian and other applications.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionjson-canvasExecute the skills CLI command in your project's root directory to begin installation:
Fetches json-canvas from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate json-canvas. Access via /json-canvas in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
This skill enables Claude Code to create and edit valid JSON Canvas files (.canvas) used in Obsidian and other applications.
JSON Canvas is an open file format for infinite canvas data. Canvas files use the .canvas extension and contain valid JSON following the JSON Canvas Spec 1.0.
A canvas file contains two top-level arrays:
{
"nodes": [],
"edges": []
}
nodes (optional): Array of node objectsedges (optional): Array of edge objects connecting nodesNodes are objects placed on the canvas. There are four node types:
text - Text content with Markdownfile - Reference to files/attachmentslink - External URLgroup - Visual container for other nodesNodes are ordered by z-index in the array:
All nodes share these attributes:
| Attribute | Required | Type | Description |
|---|---|---|---|
id |
Yes | string | Unique identifier for the node |
type |
Yes | string | Node type: text, file, link, or group |
x |
Yes | integer | X position in pixels |
y |
Yes | integer | Y position in pixels |
width |
Yes | integer | Width in pixels |
height |
Yes | integer | Height in pixels |
color |
No | canvasColor | Node color (see Color section) |
Text nodes contain Markdown content.
{
"id": "6f0ad84f44ce9c17",
"type": "text",
"x": 0,
"y": 0,
"width": 400,
"height": 200,
"text": "# Hello World\n\nThis is **Markdown** content."
}
| Attribute | Required | Type | Description |
|---|---|---|---|
text |
Yes | string | Plain text with Markdown syntax |
File nodes reference files or attachments (images, videos, PDFs, notes, etc.).
{
"id": "a1b2c3d4e5f67890",
"type": "file",
"x": 500,
"y": 0,
"width": 400,
"height": 300,
"file": "Attachments/diagram.png"
}
{
"id": "b2c3d4e5f6789012",
"type": "file",
"x": 500,
"y": 400,
"width": 400,
"height": 300,
"file": "Notes/Project Overview.md",
"subpath": "#Implementation"
}
| Attribute | Required | Type | Description |
|---|---|---|---|
file |
Yes | string | Path to file within the system |
subpath |
No | string | Link to heading or block (starts with #) |
Link nodes display external URLs.
{
"id": "c3d4e5f678901234",
"type": "link",
"x": 1000,
"y": 0,
"width": 400,
"height": 200,
"url": "https://obsidian.md"
}
| Attribute | Required | Type | Description |
|---|---|---|---|
url |
Yes | string | External URL |
Group nodes are visual containers for organizing other nodes.
{
"id": "d4e5f6789012345a",
"type": "group",
"x": -50,
"y": -50,
"width": 1000,
"height": 600,
"label": "Project Overview",
"color": "4"
}
{
"id": "e5f67890123456ab",
"type": "group",
"x": 0,
"y": 700,
"width": 800,
"height": 500,
"label": "Resources",
"background": "Attachments/background.png",
"backgroundStyle": "cover"
}
| Attribute | Required | Type | Description |
|---|---|---|---|
label |
No | string | Text label for the group |
background |
No | string | Path to background image |
backgroundStyle |
No | string | Background rendering style |
| Value | Description |
|---|---|
cover |
Fills entire width and height of node |
ratio |
Maintains aspect ratio of background image |
repeat |
Repeats image as pattern in both directions |
Edges are lines connecting nodes.
{
"id": "f67890123456789a",
"fromNode": "6f0ad84f44ce9c17",
"toNode": "a1b2c3d4e5f67890"
}
{
"id": "0123456789abcdef",
"fromNode": "6f0ad84f44ce9c17",
"fromSide": "right",
"fromEnd": "none",
"toNode": "b2c3d4e5f6789012",
"toSide": "left",
"toEnd": "arrow",
"color": "1",
"label": "leads to"
}
| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
id |
Yes | string | - | Unique identifier for the edge |
fromNode |
Yes | string | - | Node ID where connection starts |
fromSide |
No | string | - | Side where edge starts |
fromEnd |
No | string | none |
Shape at edge start |
toNode |
Yes | string | - | Node ID where connection ends |
toSide |
No | string | - | Side where edge ends |
toEnd |
No | string | arrow |
Shape at edge end |
color |
No | canvasColor | - | Line color |
label |
No | string | - | Text label for the edge |
| Value | Description |
|---|---|
top |
Top edge of node |
right |
Right edge of node |
bottom |
Bottom edge of node |
left |
Left edge of node |
| Value | Description |
|---|---|
none |
No endpoint shape |
arrow |
Arrow endpoint |
The canvasColor type can be specified in two ways:
{
"color": "#FF0000"
}
{
"color": "1"
}
| Preset | Color |
|---|---|
"1" |
Red |
"2" |
Orange |
"3" |
Yellow |
"4" |
Green |
"5" |
Cyan |
"6" |
Purple |
Note: Specific color values for presets are intentionally undefined, allowing applications to use their own brand colors.
{
"nodes": [
{
"id": "8a9b0c1d2e3f4a5b",
"type": "text",
"x": 0,
"y": 0,
"width": 300,
"height": 150,
"text": "# Main Idea\n\nThis is the central concept."
},
{
"id": "1a2b3c4d5e6f7a8b",
"type": "text",
"x": 400,
"y": -100,
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
ml-paper-writing
75davila7/claude-code-templates
AI/MLsame repotext-to-lottie
93diffusionstudio/lottie
designtag: jsongrill-me
648mattpocock/skills
Productivitysame categorypremortem
214parcadei/continuous-claude-v3
Productivitysame categorydeslop
159cursor/plugins
Productivitysame categorytravel-planner
136ailabs-393/ai-labs-claude-skills
Productivitysame categoryReviews
4.5★★★★★48 reviews- AAmelia Choi★★★★★Dec 28, 2024
Keeps context tight: json-canvas is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ZZara Singh★★★★★Dec 8, 2024
json-canvas is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ZZara Anderson★★★★★Nov 27, 2024
json-canvas reduced setup friction for our internal harness; good balance of opinion and flexibility.
- DDaniel Malhotra★★★★★Nov 19, 2024
Registry listing for json-canvas matched our evaluation — installs cleanly and behaves as described in the markdown.
- AAdvait Li★★★★★Nov 3, 2024
json-canvas fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- AAmelia Tandon★★★★★Oct 22, 2024
We added json-canvas from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- XXiao Park★★★★★Oct 18, 2024
Registry listing for json-canvas matched our evaluation — installs cleanly and behaves as described in the markdown.
- CChen White★★★★★Oct 10, 2024
json-canvas reduced setup friction for our internal harness; good balance of opinion and flexibility.
- OOshnikdeep★★★★★Sep 9, 2024
We added json-canvas from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ZZara Perez★★★★★Sep 5, 2024
json-canvas reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 48
1 / 5Discussion
Comments — not star reviews- No comments yet — start the thread.