Skills

Design and build data presentations — slide decks, board and investor decks, QBRs, analytics readouts, launch and sales decks, conference talks, and interactive web decks — that hold up in a room, in an inbox, and on a phone. Use whenever the user wants slides or a presentation: "make a deck", "turn this into slides", "board deck", "pitch deck", "QBR", "readout", "all-hands", "present these results", "PowerPoint", "pptx", "Google Slides", "keynote", "talk", "webinar", "speaker notes", "slidedoc", "reveal.js", or an interactive/HTML deck — even if they only say "put this in slides" or "we're presenting this Thursday". Covers storyline, slide layout and type specs, staged chart reveals, presenter mechanics, accessibility, and the build path (self-contained HTML, .pptx, Google Slides, or a spec). Composes with dreambase-data-stories, dreambase-visualization-design, dreambase-echarts, and any brand guide, design.md, or .potx the user supplies.

Design best-in-class data-story artifacts — reports, executive summaries, slide decks, one-pagers, infographics, and scrollytelling pieces — that blend accurate charts, illustration, great typography, and narrative structure into easy-to-consume stories. Use whenever the user wants to present, summarize, or communicate analytics or data to an audience: "make a report", "exec summary", "board deck", "slides", "one-pager", "data story", "writeup of these results", or "make this presentable" — even if they don't mention design. Always apply dreambase-visualization-design for the charts themselves; use dreambase-echarts when charts will actually render.

Author Apache ECharts option (EChartsOption) JSON configs for the Dreambase renderer. Use whenever the user wants a chart, graph, plot, dashboard, or any data visualization — line, bar, pie, scatter, heatmap, sankey, treemap, sunburst, gauge, candlestick, boxplot, funnel, radar, graph/network, map, or calendar — or asks to visualize, plot, or chart data, even if they never say "ECharts". Also use when editing, debugging, or validating an existing ECharts config.

Create dark, cinematic technical-schematic illustrations and UI components in the cinematic industrial / HUD style used by AI product marketing sites like Linear and Vercel — orbital process rings with radial tick marks and glowing nodes, monospace uppercase micro-labels, cel-shaded exploded machinery (lenses, turbines, engines), holographic 2D/3D wireframe mesh charts (extruded donut/pie data-objects with free x/y/z camera rotation and wire/translucent/cel fills), monochromatic hue themes (phosphor terminal green, ember, mono white, or any brand hue), tick-strip rulers/sliders, and dial/gauge components. Use when the user asks for schematic, technical, blueprint, HUD, sci-fi, hologram, wireframe, terminal-green, or "engineering diagram" style visuals; a dark hero graphic or diagram for a landing page; an exploded view of a product/system rendered as machinery; a process-loop or lifecycle ring; "that Linear look"; or components (sliders, dials, tickers) in this aesthetic — even if they can't name the style.

Use Dreambase workspaces, dashboards, datasets, connected Supabase/API/MCP sources, dataset planning, connector setup, metric snapshots, database health reports, and workspace Skills. Use whenever a Dreambase MCP tool is available or the user asks to inspect, analyze, create, connect, or report on Dreambase data. Routes existing-data questions through query_dataset and new data needs through connection discovery and plan_datasets, with explicit persistence, retry, and untrusted-content boundaries.

Design graphics in the micrographics style — the aesthetic that borrows the visual language of regulatory compliance labelling (rating plates, garment care tags, spec sheets, technical drawings) and uses it as intentional design. Hairline rules, boxed compartments, tick scales, registration marks, corner brackets, LABEL: value pairs, invented telemetry and seals, barcodes, batch codes, mono micro-type against huge display type, line-screen and halftone texture. Use when the user asks for a spec-sheet, technical-label, rating-plate, care-tag, "utilitarian", "technical graphics", "micro design", or FUI look; wants a compliance-label pastiche; wants apparel, poster, zine, packaging, credential-badge or identity work in a technical/industrial idiom; asks for graphics that "look engineered" or "like a spec sheet"; or wants tick marks, crosshairs, callout leaders, or micro-typography as a design system — even if they can't name the style. Covers the certification-mark legal guardrail.

Create disclosure-safe public reports, data stories, dashboards, infographics, and static artifacts that are informed by real or sensitive data without publishing the underlying values. Use whenever analytics will be shared publicly, externally, on a marketing site, in a public report, or with an audience that must see honest trends but not confidential numbers. Apply this alongside dreambase-data-stories, dreambase-visualization-design, and dreambase-echarts; it governs redaction, transformed chart data, constructive tone, and approval for visible percentages, rates, deltas, ratios, or indexes.

Create, improve, and evaluate Dreambase agent skills in the DreambaseAI/skills repo. Use this whenever the user wants to build a new skill, edit or optimize an existing skill, add a skill to this repo, run skill evals, or asks about skill conventions, naming, structure, or the SKILL.md format. Trigger even if they just say "add a skill for X" or "make Claude able to do X" without mentioning skills explicitly.

Design, critique, and improve charts, dashboards, infographics, analytical displays, and data stories using evidence-based visualization, perceptual, statistical, accessibility, and dashboard principles. Use when selecting chart types, reviewing or laying out dashboards, designing KPIs or infographics, writing visualization specs, reducing clutter, checking whether a chart misleads, or making any "which chart / how should this look" decision — even if the user only says "make this look better" or "review my dashboard". For authoring the actual ECharts option JSON, use dreambase-echarts after the design decisions here.