القائمة
End-to-end project execution wrapper for Data Visualization Kit. Use when the user types `$dv-cook` or wants to continue a project after `$dv-plan` with the context, dataset, and goals already locked.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build and refresh visualization layers for Data Visualization Kit projects. Use when the task is dashboard construction, chart refresh, visualization-path selection, dashboard QA, or project-scoped visualization delivery that must follow the kit visualization workflow and resolve to one selected tool path.
Start a new Data Visualization Kit project with structured intake and planning. Use when the user types `$dv-plan`, starts a new project, has a dataset but unclear scope, needs framework mapping, or needs one canonical project plan file before any downstream `$dv-*` workflow runs.
Publish wrapper for Data Visualization Kit. Use when the user types `$dv-publish` or needs to make a project git-ready, deployment-ready, and aligned with the kit's publish rules.
Use when working with Power BI Project files, PBIP structure, PBIR report JSON, TMDL semantic model files, definition.pbir bindings, report folders, model folders, or validation after Power BI file edits.
Use when a Data Visualization Kit project chooses Power BI as the visualization path, or when the user asks to build, review, publish, or operate Power BI reports, dashboards, semantic models, PBIP/PBIR assets, DAX, Power BI Desktop, or Microsoft Fabric-backed report workflows.
Maintain and evolve existing Apache Superset analytics stacks (v6.x). Use for SQL Lab, datasets, charts, dashboards, RBAC, RLS, embedding via guest token API, REST API integration, Celery async, caching, Docker/Helm deployment, and migration planning toward Metabase or Grafana. Prefer only for legacy projects that already selected Superset. Requires 4GB+ RAM.
| name | dv-cook |
| description | End-to-end project execution wrapper for Data Visualization Kit. Use when the user types `$dv-cook` or wants to continue a project after `$dv-plan` with the context, dataset, and goals already locked. |
Treat $dv-cook as the canonical post-intake execution wrapper.
./.codex/workflows/cook-workflow.md as the source of truth.$dv-plan has already created the project workspace and captured the full intake.$dv-data-preparation$dv-data-visualize$dv-document-management$dv-publishprojects/<slug>/docs/.$dv-plan:
docs/validation.md for proof matrix statusdocs/stories/ for story-sized workdocs/decisions/ for inherited workflow decisionsdocs/assets/harness/traces.jsonl for workflow trace historydocs/drift-audit.md for stale or contradictory project-state checksThe final dashboard MUST be a live, interactive UI — not a static HTML export.
npm run dev inside projects/<slug>/evidence/ — the dev server is the live interactive UINever deliver a flat HTML file or screenshot as the final dashboard. The user must be able to interact with it in a browser.
After $dv-data-visualize completes, determine which tool was selected from projects/<slug>/docs/visualization.md and start it locally:
| Tool | Local start command | Default URL |
|---|---|---|
| Evidence | cd projects/<slug>/evidence && npm install && npm run dev | http://localhost:3000 |
| Metabase | docker compose up -d from projects/<slug>/ (requires docker-compose.yml) | http://localhost:3000 |
| Grafana | docker compose up -d from projects/<slug>/ (requires docker-compose.yml) | http://localhost:3000 |
During the validation stage, perform tool-aware checks:
test skill or project validator)docs/visualization.md:
npm run dev starts and http://localhost:3000 is reachabledocs/validation.md, docs/assets/harness/traces.jsonl, and docs/drift-audit.md for stale or contradictory state.