personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint 1] feat: Create viz-platform plugin structure #177

New Issue
Closed
opened 2026-01-26 16:21:40 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-01-26 16:21:40 +00:00
Owner
Copy Link

Description

Create the plugin directory structure at plugins/viz-platform/ following marketplace conventions.

Acceptance Criteria

  • Create directory structure: 
    plugins/viz-platform/
├── .claude-plugin/
│   └── plugin.json
├── .mcp.json
├── mcp-servers/
│   └── viz-platform -> ../../../mcp-servers/viz-platform  # SYMLINK
├── commands/           # Created in separate issue
├── agents/             # Created in separate issue
├── hooks/
│   └── hooks.json
└── README.md           # Created in docs issue
  • Create plugin.json with proper metadata:
    • name, version, description, author, homepage, repository
    • commands, mcpServers references
    • keywords: dash, plotly, mantine, charts, dashboards, theming
  • Create .mcp.json pointing to viz-platform MCP server
  • Create symlink to mcp-servers/viz-platform
  • Create hooks/hooks.json with SessionStart hook for DMC version check
  • Verify plugin loads without errors

Technical Notes

Reference: plugins/data-platform/ structure

plugin.json example:

{
  "name": "viz-platform",
  "version": "1.0.0",
  "description": "Visualization tools with Dash Mantine Components validation and theming",
  "commands": ["./commands/"],
  "mcpServers": ["./.mcp.json"]
}

Dependencies

  • Depends on #170 (MCP server foundation must exist for symlink)
## Description Create the plugin directory structure at `plugins/viz-platform/` following marketplace conventions. ## Acceptance Criteria - [ ] Create directory structure: ``` plugins/viz-platform/ ├── .claude-plugin/ │ └── plugin.json ├── .mcp.json ├── mcp-servers/ │ └── viz-platform -> ../../../mcp-servers/viz-platform # SYMLINK ├── commands/ # Created in separate issue ├── agents/ # Created in separate issue ├── hooks/ │ └── hooks.json └── README.md # Created in docs issue ``` - [ ] Create `plugin.json` with proper metadata: - name, version, description, author, homepage, repository - commands, mcpServers references - keywords: dash, plotly, mantine, charts, dashboards, theming - [ ] Create `.mcp.json` pointing to viz-platform MCP server - [ ] Create symlink to `mcp-servers/viz-platform` - [ ] Create `hooks/hooks.json` with SessionStart hook for DMC version check - [ ] Verify plugin loads without errors ## Technical Notes Reference: `plugins/data-platform/` structure plugin.json example: ```json { "name": "viz-platform", "version": "1.0.0", "description": "Visualization tools with Dash Mantine Components validation and theming", "commands": ["./commands/"], "mcpServers": ["./.mcp.json"] } ``` ## Dependencies - Depends on #170 (MCP server foundation must exist for symlink)
lmiranda commented 2026-01-26 17:01:03 +00:00
Author
Owner
Copy Link

Completed: Plugin structure created.

Structure Created:

plugins/viz-platform/
├── .claude-plugin/
│   └── plugin.json
├── .mcp.json
├── mcp-servers/
│   └── viz-platform -> ../../../mcp-servers/viz-platform
├── commands/
├── agents/
└── hooks/
    └── hooks.json

Changes:

  • Added plugin to marketplace.json
  • Marketplace validation passes (11 plugins total)

Commit: 45b899b

Completed: Plugin structure created. **Structure Created:** ``` plugins/viz-platform/ ├── .claude-plugin/ │ └── plugin.json ├── .mcp.json ├── mcp-servers/ │ └── viz-platform -> ../../../mcp-servers/viz-platform ├── commands/ ├── agents/ └── hooks/ └── hooks.json ``` **Changes:** - Added plugin to marketplace.json - Marketplace validation passes (11 plugins total) **Commit:** 45b899b
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Component/Infra Complexity/Simple Effort/S Priority/High Type/Feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#177
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?