Stream Deck integration assistant for VSCode. Create, manage, and organize Stream Deck profiles, buttons, snippets, and scripts. Helps build productivity workflows for developers using Stream Deck with Claude Code and TAC (Tactical Agentic Coding) patterns.
/plugin marketplace add evolv3-ai/vibe-skills/plugin install evolv3-ai-vibe-skills@evolv3-ai/vibe-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
DeckMate helps you create and manage Stream Deck integrations for VSCode and Claude Code workflows. It understands both the native Stream Deck profile format AND provides tooling for developer workflow integrations.
Use this skill when:
Stream Deck profiles are .streamDeckProfile files, which are ZIP archives containing:
ProfileName.streamDeckProfile (ZIP)
└── {UUID}.sdProfile/
├── manifest.json # Profile metadata
└── Profiles/
└── {PAGE_ID}/
├── manifest.json # Button/action configuration
└── Images/
└── *.png # Button icons (72x72 or 144x144)
{UUID}.sdProfile/manifest.json:
{
"Device": {
"Model": "20GBD9901",
"UUID": ""
},
"Name": "Profile Name",
"Pages": {
"Current": "page-uuid-here",
"Pages": ["page-uuid-here", "another-page-uuid"]
},
"Version": "2.0"
}
Device Models:
20GBD9901 - Stream Deck (15 keys)20GAT9901 - Stream Deck Mini (6 keys)20GAV9901 - Stream Deck XL (32 keys)20GBA9901 - Stream Deck + (8 keys + 4 dials)20GAA9901 - Stream Deck MobileProfiles/{PAGE_ID}/manifest.json:
{
"Controllers": [
{
"Type": "Keypad",
"Actions": {
"0,0": { /* Action at row 0, col 0 */ },
"0,1": { /* Action at row 0, col 1 */ },
"1,0": { /* Action at row 1, col 0 */ }
}
},
{
"Type": "Encoder",
"Actions": {
"0,0": { /* Dial 1 */ },
"1,0": { /* Dial 2 */ }
}
}
]
}
Each action in the Actions object:
{
"ActionID": "unique-uuid-here",
"LinkedTitle": false,
"Name": "Display Name",
"Settings": {
/* Action-specific settings */
},
"State": 0,
"States": [
{
"Image": "Images/filename.png",
"Title": "Button Label",
"FontFamily": "",
"FontSize": 12,
"FontStyle": "",
"FontUnderline": false,
"ShowTitle": true,
"TitleAlignment": "bottom",
"TitleColor": "#ffffff",
"OutlineThickness": 2
}
],
"UUID": "com.elgato.streamdeck.system.hotkey"
}
| UUID | Name | Description |
|---|---|---|
com.elgato.streamdeck.system.hotkey | Hotkey | Send keyboard shortcut |
com.elgato.streamdeck.system.hotkeyswitch | Hotkey Switch | Toggle between two hotkeys |
com.elgato.streamdeck.system.open | Open | Open file/folder/URL |
com.elgato.streamdeck.system.website | Website | Open URL in browser |
com.elgato.streamdeck.system.text | Text | Type text string |
com.elgato.streamdeck.system.multimedia | Multimedia | Media controls |
com.elgato.streamdeck.profile.backtoparent | Back | Navigate to parent folder |
com.elgato.streamdeck.profile.openchild | Open Folder | Navigate to subfolder |
{
"Settings": {
"Coalesce": true,
"Hotkeys": [
{
"KeyCmd": false,
"KeyCtrl": true,
"KeyModifiers": 2,
"KeyOption": false,
"KeyShift": false,
"NativeCode": 67,
"QTKeyCode": 67,
"VKeyCode": 67
}
]
}
}
KeyModifiers Bitmask:
Common VKeyCodes:
{
"Settings": {
"openInBrowser": false,
"path": "/path/to/file/or/folder"
}
}
{
"Settings": {
"text": "Text to type"
}
}
{
"Settings": {
"openInBrowser": true,
"url": "https://example.com"
}
}
For complex developer workflows, DeckMate uses Integration Definition files (JSON) that serve as blueprints. These are NOT native Stream Deck profiles but documentation/configuration that can be used to:
streamdeck/
├── profiles/ # Integration blueprints (NOT native profiles)
│ └── tac-lesson4-integrations.json
├── snippets/ # Text content for Text actions
│ └── piter-framework.md
├── scripts/ # Shell scripts for hotkey-triggered terminals
│ └── adw-plan-build.sh
└── vscode/
└── snippets.code-snippets # VSCode autocomplete snippets
{
"name": "Integration Set Name",
"description": "What this set provides",
"version": "1.0.0",
"source_lesson": "lessons/lesson-N.md",
"buttons": [
{
"position": 0,
"name": "Button Name",
"icon": "emoji-hint",
"type": "hotkey|text|open|website|script",
"action": {
/* Type-specific configuration */
},
"leverage_point": "TAC LP reference",
"priority": "high|medium|low"
}
],
"snippets": [
{
"name": "Snippet Name",
"file": "snippets/filename.ext",
"trigger": "vscode-prefix"
}
]
}
streamdeck/scripts/:#!/bin/bash
# my-command.sh
claude "/chore $1"
Create a keyboard shortcut in your terminal app to run the script
Configure Stream Deck hotkey to trigger that shortcut
Use the com.elgato.streamdeck.system.text action:
{
"UUID": "com.elgato.streamdeck.system.text",
"Settings": {
"text": "## PITER Framework\n\n### P - Prompt Input\n..."
}
}
Use the com.elgato.streamdeck.system.open action:
{
"UUID": "com.elgato.streamdeck.system.open",
"Settings": {
"openInBrowser": false,
"path": "/path/to/project/specs"
}
}
Option 1: Using Open action with terminal app
{
"UUID": "com.elgato.streamdeck.system.open",
"Settings": {
"path": "/usr/bin/wt",
"arguments": "-w 0 nt claude"
}
}
Option 2: Multi-action with hotkey sequence
When creating integrations, tag them appropriately:
| LP | Name | Stream Deck Use Case |
|---|---|---|
| 1 | Context | Open ai_docs/, load context files |
| 2 | Model | - |
| 3 | Prompt | Text injection of prompts |
| 4 | Tools | Launch Claude, terminal commands |
| 5 | Standard Out | Status posting scripts |
| 6 | Types | Open type definition files |
| 7 | Documentation | Open docs folders |
| 8 | Tests | Run test scripts |
| 9 | Architecture | Navigate project structure |
| 10 | Plans | Open specs/, create plans |
| 11 | Templates | Inject slash commands |
| 12 | ADWs | Launch ADW workflows |
{
"UUID": "com.elgato.streamdeck.system.open",
"Name": "Claude",
"Settings": {
"path": "/path/to/terminal",
"arguments": "claude"
}
}
{
"UUID": "com.elgato.streamdeck.system.text",
"Name": "/chore",
"Settings": {
"text": "/chore "
}
}
{
"UUID": "com.elgato.streamdeck.system.open",
"Name": "Specs",
"Settings": {
"path": "/home/user/project/specs"
}
}
Use Stream Deck's Multi-Action to chain:
git add -A && git commit -m ""import json
import zipfile
import uuid
import os
def create_profile(name: str, buttons: list, device_model: str = "20GBD9901"):
"""Create a .streamDeckProfile file."""
profile_uuid = str(uuid.uuid4()).upper()
page_uuid = str(uuid.uuid4())
# Root manifest
root_manifest = {
"Device": {"Model": device_model, "UUID": ""},
"Name": name,
"Pages": {"Current": page_uuid, "Pages": [page_uuid]},
"Version": "2.0"
}
# Build actions from buttons
actions = {}
for btn in buttons:
pos = f"{btn['row']},{btn['col']}"
actions[pos] = {
"ActionID": str(uuid.uuid4()),
"LinkedTitle": False,
"Name": btn["name"],
"Settings": btn.get("settings", {}),
"State": 0,
"States": [{
"Title": btn["name"],
"ShowTitle": True,
"TitleAlignment": "bottom",
"TitleColor": "#ffffff"
}],
"UUID": btn["uuid"]
}
# Page manifest
page_manifest = {
"Controllers": [{"Type": "Keypad", "Actions": actions}]
}
# Create ZIP
with zipfile.ZipFile(f"{name}.streamDeckProfile", "w") as zf:
sd_dir = f"{profile_uuid}.sdProfile"
zf.writestr(f"{sd_dir}/manifest.json", json.dumps(root_manifest))
zf.writestr(f"{sd_dir}/Profiles/{page_uuid}/manifest.json", json.dumps(page_manifest))
return f"{name}.streamDeckProfile"
buttons = [
{
"row": 0, "col": 0,
"name": "Claude",
"uuid": "com.elgato.streamdeck.system.open",
"settings": {"path": "/usr/bin/claude"}
},
{
"row": 0, "col": 1,
"name": "/chore",
"uuid": "com.elgato.streamdeck.system.text",
"settings": {"text": "/chore "}
}
]
create_profile("TAC Developer", buttons)
profiles/*.json (blueprint).streamDeckProfileRow 0: [High Priority Actions - Most Used]
Row 1: [Medium Priority - Regular Use]
Row 2: [Low Priority / Navigation]
kebab-case.sh (e.g., run-tests.sh)piter-framework.md)manifest.json syntaxchmod +x scripts/my-script.sh
DeckMate responds to these requests:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.