vega-lite-authoring
Vega-Lite Authoring
Guide for authoring and debugging Vega-Lite specifications.
Use when
- The task is general Vega-Lite authoring, chart design, encoding choice, transform design, or multi-view composition.
- You need params, selections, conditional encodings, or invalid-data handling in a Vega-Lite-first chart.
- The chart should stay high-level and declarative unless a lower-level grammar is clearly required.
Do not use when
- The real task is Deneb or Power BI host work;
deneb-authoringshould lead and apply Vega-Lite after host constraints are locked. - The requirement depends on lower-level signals, event streams, or scenegraph control that Vega-Lite cannot express cleanly.
- The user only needs raw Vega structure or debugging.
Precedence / handoff
- If the host is Deneb or Power BI, let
deneb-authoringlead and keep this skill focused on the Vega-Lite grammar portion.
More from mylesmcook/mcook-skills
adversarial-review
Use this skill when you need a serious code review, diff review, or implementation-plan review from independent reviewers. In Codex hosts, prefer a fresh Codex subagent for the Codex reviewer; otherwise use the Codex, Claude Code, and Gemini reviewer paths when available. Return a PASS, CONTESTED, or REJECT verdict.
13subagent-driven-development
Use after an implementation plan is approved to execute mostly independent tasks through fresh subagents with scoped context, harness-aware model routing, proportional review gates, and mandatory controller verification.
10brainerd
>
10simple-code
Reduce incidental complexity in code and design. Use when shaping APIs, module boundaries, refactors, tests, naming, and architecture tradeoffs with a bias toward concrete, local, reversible solutions.
7git-it-out
Use this skill when the user explicitly wants final end-of-session closeout and no more branch or PR limbo: proper verification, proper commits, main/mainline landing, push, repo-native merge/release/deploy/publish steps, tracker updates, Entire/checkpoint handling when configured, and a concise handoff. Reach for it on prompts like 'git it out', 'get it out', 'ship this', 'I'm done', 'I'm going to bed', 'take this off my plate', 'finish the session', or 'get this into production'. Do not use it for greenfield implementation, open-ended debugging, broad refactors, or inventing a release process from scratch.
7laws-of-taste
>-
6