VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Marketing Kit

/ak:hub

Content Hub and Marketing Dashboard

Records the unresolved local Content Hub and Marketing Dashboard launcher boundary so marketers do not rely on stale paths or overstated features.

01

Read limitation

02

Review prerequisites

03

Explain invocation status

04

Separate surfaces

Rule 01

Skill discovery does not prove shell, process, browser, or Hook parity.

Rule 02

Do not run launcher options through ak:hub while the contract remains unresolved.

Rule 03

Marketing Dashboard currently means Assets, Brand, and Settings, not campaign automation.

Rule 04

Port-based stopping requires process ownership checks before termination.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Read limitation Treat /ak:hub as an intended launcher with unresolved legacy naming and packaged sibling-path assumptions.
  2. 2 Review prerequisites Check Node/npm, ports 3457 and 5173, dependency installation, asset scanning, PID files, local state, and browser-opening approval before any manual recovery.
02

Work

Agent / skill execution

  1. 3 Explain invocation status Document canonical /ak:hub or $ak:hub spelling without treating discovery as verified launcher behavior.
  2. 4 Separate surfaces Describe Content Hub as an asset gallery and Marketing Dashboard as Assets, Brand, and Settings views only.
03

Verify

Gate, review, validation

  1. 5 Control process risk Do not start, rescan, or stop through ak:hub while path and ownership checks remain unresolved.
  2. 6 State excluded claims Exclude campaign management, content-generation APIs, automation recipes, enforced API-key security, cloud sync, and publication claims.
04

Close

Report, handoff, artifact

  1. 7 List future evidence A future supported launcher must report resolved paths, dependency proposals, PIDs, bind addresses, health checks, URLs, and ownership-safe stop behavior.

Special Operations

Content Hub

Intended local asset gallery with project assets, manifest metadata, previews, brand context, and local save routes.

Marketing Dashboard

Current dashboard authority is Assets, Brand, and Settings views; campaign, generation, and automation features are excluded.

Dashboard API

Local API can scan and update asset metadata, read brand context, and upload validated logos; API-key settings are not an enforced security boundary.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Review limitation Recommended 
/ak:hub
Use when:
You are considering the intended local Content Hub and Dashboard launcher.
Expected:
Explains the unresolved launcher boundary instead of starting services.
Scan boundary 
/ak:hub --scan
Use when:
You need to understand the intended asset rescan behavior.
Expected:
Warns not to run scan mode through ak:hub until the launcher contract is fixed.
Stop boundary 
/ak:hub --stop
Use when:
You need to understand the intended stop behavior.
Expected:
Requires ownership checks and warns against legacy port-based termination.

Handled Scope

  • Read limitation
  • Review prerequisites
  • Explain invocation status
  • Separate surfaces
  • Control process risk
  • State excluded claims

Next