Browse local assets with ak:marketing-dashboard

Use ak:marketing-dashboard to operate the current local Vue and Hono application for browsing marketing assets, inspecting brand context, uploading validated logos, and configuring the browser client's API base URL. Its README is the operating authority; the current application has no campaign manager, content library, AI generation endpoint, or automation recipe.

Choose the dashboard for local inspection

Use ak:marketing-dashboard when

• You need the Assets (/), Brand (/brand), or Settings (/settings) view.
• You want to rescan shared assets, preview supported files, update stored asset metadata, inspect tokens or voice, or upload a logo after approval.

Choose another workflow when

• You need performance analytics. Use ak:analytics or ak:analyze.
• You need cloud asset sync, campaign operation, content generation, or deployment. Those behaviors are not implemented by this dashboard.
• You only need launcher mode tokens. Use ak:dashboard.

Prepare the runtime and local data

Resolve this installed Skill's directory through the live runtime catalog. Node.js 20 LTS is recommended. The server uses Hono and optional better-sqlite3; the frontend uses Vue 3 and Vite. Review ports 3457 and 5173, npm network access, shared assets/, docs/brand-guidelines.md, assets/design-tokens.json, assets/logos/, app/dist/, and data/marketing.db before allowing changes.

The scanner derives 12-character IDs from relative asset paths and records paths, names, categories, formats, sizes, timestamps, tags, references, campaign labels, and inferred AI-generated status. SQLite can also store ai_prompt, r2_status, and r2_url; these fields do not prove any R2 sync occurred. Treat filenames, prompts, paths, URLs, brand guidance, and file content as potentially confidential. Raw text preview is limited to 10 MB, but that is a size boundary, not a privacy control.

Run the Skill

/ak:marketing-dashboard "Resolve the installed Skill directory, explain dependency and storage changes, then start development mode only after approval"

/ak:marketing-dashboard "Resolve the installed Skill directory, explain dependency and storage changes, then start development mode only after approval"

$ak:marketing-dashboard "Resolve the installed Skill directory, explain dependency and storage changes, then start development mode only after approval"

The documented scripts are ./start.sh, ./stop.sh, ./build.sh, and ./start-production.sh. Run them from the resolved Skill directory, not an assumed Claude-only path.

Understand the stages

1. Read the installed README and resolve the Skill directory.
2. Review dependencies, ports, shared source paths, database, build, and PID effects.
3. Start development or build and start local production as explicitly requested.
4. Use the live Assets and Brand routes; separate read actions from scan, metadata update, logo upload, and filesystem creation.
5. Report actual URLs, health, mutations, and SQLite remediation; stop the owned process.

Protect local files and access

Logo upload writes PNG, JPEG, SVG, or WebP files up to 5 MB into assets/logos/ after filename sanitization. Scanning writes asset metadata to SQLite, and metadata updates can change prompt and R2 fields. These are local mutations requiring approval. No dashboard action authorizes external upload, publishing, provider access, or spend.

Verify outputs and evidence

Verify GET /health; the Assets and Brand route results; actual files written; SQLite records; and the reported frontend/API URLs. In development expect http://localhost:5173 and http://localhost:3457; production serves the built app from http://localhost:3457. Record unsupported formats, read errors, missing brand files, and skipped or failed writes.

Troubleshoot and know the limits

The dashboard does not guarantee authentication, network isolation, cloud sync, AI features, campaign operation, or provider compatibility. See Marketing Kit and Runtime adapters.