[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-dashboards-and-real-time-visualization":3,"mdc-1czz8l-key":39,"related-repo-openai-dashboards-and-real-time-visualization":758,"related-org-openai-dashboards-and-real-time-visualization":877},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":28,"repoUrl":29,"updatedAt":30,"license":31,"forks":32,"topics":33,"repo":34,"sourceUrl":37,"mdContent":38},"dashboards-and-real-time-visualization","design dashboards and live visualization systems","Design dashboards and live visualization systems. Use when the user needs monitoring views, streaming charts, coordinated interactions, downsampling, or performance-aware operational visualization.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19,22,25],{"name":13,"slug":14,"type":15},"Performance","performance","tag",{"name":17,"slug":18,"type":15},"Dashboards","dashboards",{"name":20,"slug":21,"type":15},"Data Visualization","data-visualization",{"name":23,"slug":24,"type":15},"Monitoring","monitoring",{"name":26,"slug":27,"type":15},"Analytics","analytics",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-06-30T19:00:57.102",null,465,[],{"repoUrl":29,"stars":28,"forks":32,"topics":35,"description":36},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fbuild-web-data-visualization\u002Fskills\u002Fdashboards-and-real-time-visualization","---\nname: dashboards-and-real-time-visualization\ndescription: Design dashboards and live visualization systems. Use when the user needs monitoring views, streaming charts, coordinated interactions, downsampling, or performance-aware operational visualization.\n---\n\n# Dashboards and Real-Time Visualization\n\n## Overview\n\nUse this skill when the visualization is a system, not a screenshot. That means update cadence, latency, interaction design, observability, and rendering budgets matter as much as chart choice.\n\nIf the main request is about how to test a live dashboard, freeze streams, mock refresh behavior, or cover alerting and stale states end to end, route first to `..\u002Ftesting-data-visualizations\u002FSKILL.md`.\n\nMobile operational use is default unless explicitly excluded. Use `..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md` to plan the mobile portrait dashboard, optional landscape mode, touch interaction, on-screen keyboard behavior, spotty connection handling, and alerting or vibration strategy.\n\nThis skill covers three tightly related problems:\n\n- real-time streaming and refresh behavior\n- layout hierarchy and scan-first dashboard composition\n- interaction patterns and coordinated views\n- performance and scale\n\n## Default Questions\n\n1. What is the update model?\n   - append-only stream\n   - periodic polling\n   - event bursts\n   - full snapshot replacement\n2. What latency matters?\n   - sub-second monitoring\n   - near-real-time operational review\n   - asynchronous reporting\n3. What must the user do?\n   - notice anomalies\n   - compare current versus historical\n   - inspect causes\n   - filter and drill down\n4. What are the hard limits?\n   - frame budget\n   - memory budget\n   - network budget\n   - exportability\n   - mobile bandwidth, battery, and thermal budget\n5. How many visualization instances can be visible at once?\n   - single focal chart\n   - a few coordinated panels\n   - many repeated tiles or sparklines\n6. What mobile state must work under interruption?\n   - spotty or offline connection\n   - app backgrounding or tab visibility changes\n   - one-handed use\n   - alert acknowledgment\n   - on-screen keyboard for filters or notes\n\n## Real-Time Design Rules\n\n- Show time windows clearly.\n- Distinguish live data from historical context.\n- Handle missing, late, and out-of-order events explicitly.\n- Keep the last known good visualization visible during reconnects, with stale, delayed, partial, offline, and error states distinct from normal live data.\n- Show last updated time and update cadence near the evidence.\n- Use aggregation, downsampling, or rollups before raw point dumping.\n- Provide alert thresholds, annotations, and state transitions, not just moving lines.\n- Use vibration, system notifications, or push-style alerts only for user-requested and meaningful state changes; always provide an in-app visual and accessible alert path.\n- Keep the most important metric stable in position and encoding.\n- Keep keys with their charts: direct labels or chart-adjacent keys beat a shared legend parked elsewhere on the screen.\n- Use sparklines and other microcharts when compact trend context helps scanning, but rely on nearby labels and values to carry meaning.\n- Design dashboards around situation awareness, not around maximum tile count.\n- Prefer self-explanatory panels and concise labels over instructional paragraphs scattered across the UI.\n\n## Layout and Scanning Defaults\n\n- Give the screen a clear focal path: current state first, then supporting context, then controls and secondary diagnostics.\n- Avoid grids where every tile has equal visual weight unless the user truly needs uniform scanning across peers.\n- Keep filters and toggles near the views they change instead of collecting everything in a distant control rail.\n- Reserve callouts and narrative copy for anomalies, caveats, or actions. The normal state should be legible without tutorial text.\n- Collapse or defer low-value controls so the live state stays visually dominant.\n- On mobile, do not stack the filter rail or diagnostic controls before the live state. Use bottom sheets, drawers, tabs, or inline controls that return the user to the affected visualization after Apply, Cancel, Reset, or close.\n- Use mobile landscape for monitoring views when a wide timeline, map, field, route, dense table, or multi-series trace is meaningfully clearer in a handheld wide orientation, but still provide a portrait summary.\n\n## Interaction Patterns\n\n- overview first, filter or focus, then details on demand\n- overview plus detail\n- focus plus context\n- brush and link\n- hover for preview, click for commitment\n- tap\u002Ffocus for preview, tap again or explicit action for commitment on touch devices\n- drill-down and drill-through\n- persistent selections that survive updates\n- explicit reset and undo paths\n\nInteractivity should reduce cognitive load, not hide essential context behind constant mouse movement.\n\nFor mobile dashboards, add step-through controls, search, or nearest-item selection for dense marks; do not rely on hover, pixel-perfect taps, or one-finger chart panning that traps page scroll.\n\n## Performance Defaults\n\n1. Budget for 16 ms frames only when truly needed.\n2. Reduce work before optimizing code:\n   - fewer marks\n   - smarter aggregation\n   - smaller repaint regions\n   - lower-frequency updates where appropriate\n3. Choose the renderer intentionally:\n   - SVG for semantics and annotation\n   - Canvas2D for dense 2D raster workloads\n   - WebGL, deck.gl, PixiJS, Sigma.js, or Three.js for GPU-scale marks, maps, particles, graph rendering, or true 3D\n4. Use ring buffers, viewport culling, and multi-resolution summaries for long-running live views.\n5. Separate interaction state from render state so updates remain predictable.\n6. Use particles or glow in dashboards only for active flow, alert state, focus, or recency. Avoid ambient motion that competes with monitoring.\n\n## Output Expectations\n\n- Describe the update model and failure modes.\n- Describe mobile reconnect, stale-data, offline\u002Fpartial-data, and low-bandwidth behavior.\n- Explain what a user should understand at first scan before touching any controls.\n- Explain what the mobile user sees first and how the main visualization remains visible around controls and keyboard input.\n- Define the interaction contract before building widgets.\n- State how the system degrades when data rate or mark count rises.\n- Include a technical design section for new work covering simultaneous chart count, per-instance and page-level budgets, and maintenance implications of the chosen rendering strategy.\n- Keep accessibility and export strategy visible.\n\n## References\n\n- Shared theory:\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fstorytelling-annotation-and-critique.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Flayout-hierarchy-and-self-explanatory-ux.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Finteraction-models-and-progressive-disclosure.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fimplementation-design-and-tradeoffs.md`\n- Skill references:\n  - `.\u002Freferences\u002Fmonitoring-vs-analysis.md`\n  - `.\u002Freferences\u002Fstreaming-data-pipelines.md`\n  - `.\u002Freferences\u002Finteraction-patterns.md`\n  - `.\u002Freferences\u002Fperformance-and-degradation.md`\n  - `..\u002Ftesting-data-visualizations\u002FSKILL.md`\n\n## Representative Prompts\n\n- \"Build a real-time operations dashboard from a WebSocket feed.\"\n- \"Keep this live chart smooth with 100 updates per second.\"\n- \"Design brushing, cross-filtering, and annotations for this monitoring UI.\"\n- \"Tell me if this should be a dashboard or a report.\"\n- \"Critique this monitoring screen using operational dashboard principles.\"\n",{"data":40,"body":41},{"name":4,"description":6},{"type":42,"children":43},"root",[44,52,59,65,79,92,97,122,128,300,306,374,380,418,424,472,477,482,488,562,568,611,617,724,730],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":51},"text","Dashboards and Real-Time Visualization",{"type":45,"tag":53,"props":54,"children":56},"h2",{"id":55},"overview",[57],{"type":50,"value":58},"Overview",{"type":45,"tag":60,"props":61,"children":62},"p",{},[63],{"type":50,"value":64},"Use this skill when the visualization is a system, not a screenshot. That means update cadence, latency, interaction design, observability, and rendering budgets matter as much as chart choice.",{"type":45,"tag":60,"props":66,"children":67},{},[68,70,77],{"type":50,"value":69},"If the main request is about how to test a live dashboard, freeze streams, mock refresh behavior, or cover alerting and stale states end to end, route first to ",{"type":45,"tag":71,"props":72,"children":74},"code",{"className":73},[],[75],{"type":50,"value":76},"..\u002Ftesting-data-visualizations\u002FSKILL.md",{"type":50,"value":78},".",{"type":45,"tag":60,"props":80,"children":81},{},[82,84,90],{"type":50,"value":83},"Mobile operational use is default unless explicitly excluded. Use ",{"type":45,"tag":71,"props":85,"children":87},{"className":86},[],[88],{"type":50,"value":89},"..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md",{"type":50,"value":91}," to plan the mobile portrait dashboard, optional landscape mode, touch interaction, on-screen keyboard behavior, spotty connection handling, and alerting or vibration strategy.",{"type":45,"tag":60,"props":93,"children":94},{},[95],{"type":50,"value":96},"This skill covers three tightly related problems:",{"type":45,"tag":98,"props":99,"children":100},"ul",{},[101,107,112,117],{"type":45,"tag":102,"props":103,"children":104},"li",{},[105],{"type":50,"value":106},"real-time streaming and refresh behavior",{"type":45,"tag":102,"props":108,"children":109},{},[110],{"type":50,"value":111},"layout hierarchy and scan-first dashboard composition",{"type":45,"tag":102,"props":113,"children":114},{},[115],{"type":50,"value":116},"interaction patterns and coordinated views",{"type":45,"tag":102,"props":118,"children":119},{},[120],{"type":50,"value":121},"performance and scale",{"type":45,"tag":53,"props":123,"children":125},{"id":124},"default-questions",[126],{"type":50,"value":127},"Default Questions",{"type":45,"tag":129,"props":130,"children":131},"ol",{},[132,160,183,211,244,267],{"type":45,"tag":102,"props":133,"children":134},{},[135,137],{"type":50,"value":136},"What is the update model?\n",{"type":45,"tag":98,"props":138,"children":139},{},[140,145,150,155],{"type":45,"tag":102,"props":141,"children":142},{},[143],{"type":50,"value":144},"append-only stream",{"type":45,"tag":102,"props":146,"children":147},{},[148],{"type":50,"value":149},"periodic polling",{"type":45,"tag":102,"props":151,"children":152},{},[153],{"type":50,"value":154},"event bursts",{"type":45,"tag":102,"props":156,"children":157},{},[158],{"type":50,"value":159},"full snapshot replacement",{"type":45,"tag":102,"props":161,"children":162},{},[163,165],{"type":50,"value":164},"What latency matters?\n",{"type":45,"tag":98,"props":166,"children":167},{},[168,173,178],{"type":45,"tag":102,"props":169,"children":170},{},[171],{"type":50,"value":172},"sub-second monitoring",{"type":45,"tag":102,"props":174,"children":175},{},[176],{"type":50,"value":177},"near-real-time operational review",{"type":45,"tag":102,"props":179,"children":180},{},[181],{"type":50,"value":182},"asynchronous reporting",{"type":45,"tag":102,"props":184,"children":185},{},[186,188],{"type":50,"value":187},"What must the user do?\n",{"type":45,"tag":98,"props":189,"children":190},{},[191,196,201,206],{"type":45,"tag":102,"props":192,"children":193},{},[194],{"type":50,"value":195},"notice anomalies",{"type":45,"tag":102,"props":197,"children":198},{},[199],{"type":50,"value":200},"compare current versus historical",{"type":45,"tag":102,"props":202,"children":203},{},[204],{"type":50,"value":205},"inspect causes",{"type":45,"tag":102,"props":207,"children":208},{},[209],{"type":50,"value":210},"filter and drill down",{"type":45,"tag":102,"props":212,"children":213},{},[214,216],{"type":50,"value":215},"What are the hard limits?\n",{"type":45,"tag":98,"props":217,"children":218},{},[219,224,229,234,239],{"type":45,"tag":102,"props":220,"children":221},{},[222],{"type":50,"value":223},"frame budget",{"type":45,"tag":102,"props":225,"children":226},{},[227],{"type":50,"value":228},"memory budget",{"type":45,"tag":102,"props":230,"children":231},{},[232],{"type":50,"value":233},"network budget",{"type":45,"tag":102,"props":235,"children":236},{},[237],{"type":50,"value":238},"exportability",{"type":45,"tag":102,"props":240,"children":241},{},[242],{"type":50,"value":243},"mobile bandwidth, battery, and thermal budget",{"type":45,"tag":102,"props":245,"children":246},{},[247,249],{"type":50,"value":248},"How many visualization instances can be visible at once?\n",{"type":45,"tag":98,"props":250,"children":251},{},[252,257,262],{"type":45,"tag":102,"props":253,"children":254},{},[255],{"type":50,"value":256},"single focal chart",{"type":45,"tag":102,"props":258,"children":259},{},[260],{"type":50,"value":261},"a few coordinated panels",{"type":45,"tag":102,"props":263,"children":264},{},[265],{"type":50,"value":266},"many repeated tiles or sparklines",{"type":45,"tag":102,"props":268,"children":269},{},[270,272],{"type":50,"value":271},"What mobile state must work under interruption?\n",{"type":45,"tag":98,"props":273,"children":274},{},[275,280,285,290,295],{"type":45,"tag":102,"props":276,"children":277},{},[278],{"type":50,"value":279},"spotty or offline connection",{"type":45,"tag":102,"props":281,"children":282},{},[283],{"type":50,"value":284},"app backgrounding or tab visibility changes",{"type":45,"tag":102,"props":286,"children":287},{},[288],{"type":50,"value":289},"one-handed use",{"type":45,"tag":102,"props":291,"children":292},{},[293],{"type":50,"value":294},"alert acknowledgment",{"type":45,"tag":102,"props":296,"children":297},{},[298],{"type":50,"value":299},"on-screen keyboard for filters or notes",{"type":45,"tag":53,"props":301,"children":303},{"id":302},"real-time-design-rules",[304],{"type":50,"value":305},"Real-Time Design Rules",{"type":45,"tag":98,"props":307,"children":308},{},[309,314,319,324,329,334,339,344,349,354,359,364,369],{"type":45,"tag":102,"props":310,"children":311},{},[312],{"type":50,"value":313},"Show time windows clearly.",{"type":45,"tag":102,"props":315,"children":316},{},[317],{"type":50,"value":318},"Distinguish live data from historical context.",{"type":45,"tag":102,"props":320,"children":321},{},[322],{"type":50,"value":323},"Handle missing, late, and out-of-order events explicitly.",{"type":45,"tag":102,"props":325,"children":326},{},[327],{"type":50,"value":328},"Keep the last known good visualization visible during reconnects, with stale, delayed, partial, offline, and error states distinct from normal live data.",{"type":45,"tag":102,"props":330,"children":331},{},[332],{"type":50,"value":333},"Show last updated time and update cadence near the evidence.",{"type":45,"tag":102,"props":335,"children":336},{},[337],{"type":50,"value":338},"Use aggregation, downsampling, or rollups before raw point dumping.",{"type":45,"tag":102,"props":340,"children":341},{},[342],{"type":50,"value":343},"Provide alert thresholds, annotations, and state transitions, not just moving lines.",{"type":45,"tag":102,"props":345,"children":346},{},[347],{"type":50,"value":348},"Use vibration, system notifications, or push-style alerts only for user-requested and meaningful state changes; always provide an in-app visual and accessible alert path.",{"type":45,"tag":102,"props":350,"children":351},{},[352],{"type":50,"value":353},"Keep the most important metric stable in position and encoding.",{"type":45,"tag":102,"props":355,"children":356},{},[357],{"type":50,"value":358},"Keep keys with their charts: direct labels or chart-adjacent keys beat a shared legend parked elsewhere on the screen.",{"type":45,"tag":102,"props":360,"children":361},{},[362],{"type":50,"value":363},"Use sparklines and other microcharts when compact trend context helps scanning, but rely on nearby labels and values to carry meaning.",{"type":45,"tag":102,"props":365,"children":366},{},[367],{"type":50,"value":368},"Design dashboards around situation awareness, not around maximum tile count.",{"type":45,"tag":102,"props":370,"children":371},{},[372],{"type":50,"value":373},"Prefer self-explanatory panels and concise labels over instructional paragraphs scattered across the UI.",{"type":45,"tag":53,"props":375,"children":377},{"id":376},"layout-and-scanning-defaults",[378],{"type":50,"value":379},"Layout and Scanning Defaults",{"type":45,"tag":98,"props":381,"children":382},{},[383,388,393,398,403,408,413],{"type":45,"tag":102,"props":384,"children":385},{},[386],{"type":50,"value":387},"Give the screen a clear focal path: current state first, then supporting context, then controls and secondary diagnostics.",{"type":45,"tag":102,"props":389,"children":390},{},[391],{"type":50,"value":392},"Avoid grids where every tile has equal visual weight unless the user truly needs uniform scanning across peers.",{"type":45,"tag":102,"props":394,"children":395},{},[396],{"type":50,"value":397},"Keep filters and toggles near the views they change instead of collecting everything in a distant control rail.",{"type":45,"tag":102,"props":399,"children":400},{},[401],{"type":50,"value":402},"Reserve callouts and narrative copy for anomalies, caveats, or actions. The normal state should be legible without tutorial text.",{"type":45,"tag":102,"props":404,"children":405},{},[406],{"type":50,"value":407},"Collapse or defer low-value controls so the live state stays visually dominant.",{"type":45,"tag":102,"props":409,"children":410},{},[411],{"type":50,"value":412},"On mobile, do not stack the filter rail or diagnostic controls before the live state. Use bottom sheets, drawers, tabs, or inline controls that return the user to the affected visualization after Apply, Cancel, Reset, or close.",{"type":45,"tag":102,"props":414,"children":415},{},[416],{"type":50,"value":417},"Use mobile landscape for monitoring views when a wide timeline, map, field, route, dense table, or multi-series trace is meaningfully clearer in a handheld wide orientation, but still provide a portrait summary.",{"type":45,"tag":53,"props":419,"children":421},{"id":420},"interaction-patterns",[422],{"type":50,"value":423},"Interaction Patterns",{"type":45,"tag":98,"props":425,"children":426},{},[427,432,437,442,447,452,457,462,467],{"type":45,"tag":102,"props":428,"children":429},{},[430],{"type":50,"value":431},"overview first, filter or focus, then details on demand",{"type":45,"tag":102,"props":433,"children":434},{},[435],{"type":50,"value":436},"overview plus detail",{"type":45,"tag":102,"props":438,"children":439},{},[440],{"type":50,"value":441},"focus plus context",{"type":45,"tag":102,"props":443,"children":444},{},[445],{"type":50,"value":446},"brush and link",{"type":45,"tag":102,"props":448,"children":449},{},[450],{"type":50,"value":451},"hover for preview, click for commitment",{"type":45,"tag":102,"props":453,"children":454},{},[455],{"type":50,"value":456},"tap\u002Ffocus for preview, tap again or explicit action for commitment on touch devices",{"type":45,"tag":102,"props":458,"children":459},{},[460],{"type":50,"value":461},"drill-down and drill-through",{"type":45,"tag":102,"props":463,"children":464},{},[465],{"type":50,"value":466},"persistent selections that survive updates",{"type":45,"tag":102,"props":468,"children":469},{},[470],{"type":50,"value":471},"explicit reset and undo paths",{"type":45,"tag":60,"props":473,"children":474},{},[475],{"type":50,"value":476},"Interactivity should reduce cognitive load, not hide essential context behind constant mouse movement.",{"type":45,"tag":60,"props":478,"children":479},{},[480],{"type":50,"value":481},"For mobile dashboards, add step-through controls, search, or nearest-item selection for dense marks; do not rely on hover, pixel-perfect taps, or one-finger chart panning that traps page scroll.",{"type":45,"tag":53,"props":483,"children":485},{"id":484},"performance-defaults",[486],{"type":50,"value":487},"Performance Defaults",{"type":45,"tag":129,"props":489,"children":490},{},[491,496,524,547,552,557],{"type":45,"tag":102,"props":492,"children":493},{},[494],{"type":50,"value":495},"Budget for 16 ms frames only when truly needed.",{"type":45,"tag":102,"props":497,"children":498},{},[499,501],{"type":50,"value":500},"Reduce work before optimizing code:\n",{"type":45,"tag":98,"props":502,"children":503},{},[504,509,514,519],{"type":45,"tag":102,"props":505,"children":506},{},[507],{"type":50,"value":508},"fewer marks",{"type":45,"tag":102,"props":510,"children":511},{},[512],{"type":50,"value":513},"smarter aggregation",{"type":45,"tag":102,"props":515,"children":516},{},[517],{"type":50,"value":518},"smaller repaint regions",{"type":45,"tag":102,"props":520,"children":521},{},[522],{"type":50,"value":523},"lower-frequency updates where appropriate",{"type":45,"tag":102,"props":525,"children":526},{},[527,529],{"type":50,"value":528},"Choose the renderer intentionally:\n",{"type":45,"tag":98,"props":530,"children":531},{},[532,537,542],{"type":45,"tag":102,"props":533,"children":534},{},[535],{"type":50,"value":536},"SVG for semantics and annotation",{"type":45,"tag":102,"props":538,"children":539},{},[540],{"type":50,"value":541},"Canvas2D for dense 2D raster workloads",{"type":45,"tag":102,"props":543,"children":544},{},[545],{"type":50,"value":546},"WebGL, deck.gl, PixiJS, Sigma.js, or Three.js for GPU-scale marks, maps, particles, graph rendering, or true 3D",{"type":45,"tag":102,"props":548,"children":549},{},[550],{"type":50,"value":551},"Use ring buffers, viewport culling, and multi-resolution summaries for long-running live views.",{"type":45,"tag":102,"props":553,"children":554},{},[555],{"type":50,"value":556},"Separate interaction state from render state so updates remain predictable.",{"type":45,"tag":102,"props":558,"children":559},{},[560],{"type":50,"value":561},"Use particles or glow in dashboards only for active flow, alert state, focus, or recency. Avoid ambient motion that competes with monitoring.",{"type":45,"tag":53,"props":563,"children":565},{"id":564},"output-expectations",[566],{"type":50,"value":567},"Output Expectations",{"type":45,"tag":98,"props":569,"children":570},{},[571,576,581,586,591,596,601,606],{"type":45,"tag":102,"props":572,"children":573},{},[574],{"type":50,"value":575},"Describe the update model and failure modes.",{"type":45,"tag":102,"props":577,"children":578},{},[579],{"type":50,"value":580},"Describe mobile reconnect, stale-data, offline\u002Fpartial-data, and low-bandwidth behavior.",{"type":45,"tag":102,"props":582,"children":583},{},[584],{"type":50,"value":585},"Explain what a user should understand at first scan before touching any controls.",{"type":45,"tag":102,"props":587,"children":588},{},[589],{"type":50,"value":590},"Explain what the mobile user sees first and how the main visualization remains visible around controls and keyboard input.",{"type":45,"tag":102,"props":592,"children":593},{},[594],{"type":50,"value":595},"Define the interaction contract before building widgets.",{"type":45,"tag":102,"props":597,"children":598},{},[599],{"type":50,"value":600},"State how the system degrades when data rate or mark count rises.",{"type":45,"tag":102,"props":602,"children":603},{},[604],{"type":50,"value":605},"Include a technical design section for new work covering simultaneous chart count, per-instance and page-level budgets, and maintenance implications of the chosen rendering strategy.",{"type":45,"tag":102,"props":607,"children":608},{},[609],{"type":50,"value":610},"Keep accessibility and export strategy visible.",{"type":45,"tag":53,"props":612,"children":614},{"id":613},"references",[615],{"type":50,"value":616},"References",{"type":45,"tag":98,"props":618,"children":619},{},[620,672],{"type":45,"tag":102,"props":621,"children":622},{},[623,625],{"type":50,"value":624},"Shared theory:\n",{"type":45,"tag":98,"props":626,"children":627},{},[628,637,646,655,663],{"type":45,"tag":102,"props":629,"children":630},{},[631],{"type":45,"tag":71,"props":632,"children":634},{"className":633},[],[635],{"type":50,"value":636},"..\u002F..\u002Freferences\u002Ffoundations\u002Fstorytelling-annotation-and-critique.md",{"type":45,"tag":102,"props":638,"children":639},{},[640],{"type":45,"tag":71,"props":641,"children":643},{"className":642},[],[644],{"type":50,"value":645},"..\u002F..\u002Freferences\u002Ffoundations\u002Flayout-hierarchy-and-self-explanatory-ux.md",{"type":45,"tag":102,"props":647,"children":648},{},[649],{"type":45,"tag":71,"props":650,"children":652},{"className":651},[],[653],{"type":50,"value":654},"..\u002F..\u002Freferences\u002Ffoundations\u002Finteraction-models-and-progressive-disclosure.md",{"type":45,"tag":102,"props":656,"children":657},{},[658],{"type":45,"tag":71,"props":659,"children":661},{"className":660},[],[662],{"type":50,"value":89},{"type":45,"tag":102,"props":664,"children":665},{},[666],{"type":45,"tag":71,"props":667,"children":669},{"className":668},[],[670],{"type":50,"value":671},"..\u002F..\u002Freferences\u002Ffoundations\u002Fimplementation-design-and-tradeoffs.md",{"type":45,"tag":102,"props":673,"children":674},{},[675,677],{"type":50,"value":676},"Skill references:\n",{"type":45,"tag":98,"props":678,"children":679},{},[680,689,698,707,716],{"type":45,"tag":102,"props":681,"children":682},{},[683],{"type":45,"tag":71,"props":684,"children":686},{"className":685},[],[687],{"type":50,"value":688},".\u002Freferences\u002Fmonitoring-vs-analysis.md",{"type":45,"tag":102,"props":690,"children":691},{},[692],{"type":45,"tag":71,"props":693,"children":695},{"className":694},[],[696],{"type":50,"value":697},".\u002Freferences\u002Fstreaming-data-pipelines.md",{"type":45,"tag":102,"props":699,"children":700},{},[701],{"type":45,"tag":71,"props":702,"children":704},{"className":703},[],[705],{"type":50,"value":706},".\u002Freferences\u002Finteraction-patterns.md",{"type":45,"tag":102,"props":708,"children":709},{},[710],{"type":45,"tag":71,"props":711,"children":713},{"className":712},[],[714],{"type":50,"value":715},".\u002Freferences\u002Fperformance-and-degradation.md",{"type":45,"tag":102,"props":717,"children":718},{},[719],{"type":45,"tag":71,"props":720,"children":722},{"className":721},[],[723],{"type":50,"value":76},{"type":45,"tag":53,"props":725,"children":727},{"id":726},"representative-prompts",[728],{"type":50,"value":729},"Representative Prompts",{"type":45,"tag":98,"props":731,"children":732},{},[733,738,743,748,753],{"type":45,"tag":102,"props":734,"children":735},{},[736],{"type":50,"value":737},"\"Build a real-time operations dashboard from a WebSocket feed.\"",{"type":45,"tag":102,"props":739,"children":740},{},[741],{"type":50,"value":742},"\"Keep this live chart smooth with 100 updates per second.\"",{"type":45,"tag":102,"props":744,"children":745},{},[746],{"type":50,"value":747},"\"Design brushing, cross-filtering, and annotations for this monitoring UI.\"",{"type":45,"tag":102,"props":749,"children":750},{},[751],{"type":50,"value":752},"\"Tell me if this should be a dashboard or a report.\"",{"type":45,"tag":102,"props":754,"children":755},{},[756],{"type":50,"value":757},"\"Critique this monitoring screen using operational dashboard principles.\"",{"items":759,"total":876},[760,776,792,804,824,846,864],{"slug":761,"name":761,"fn":762,"description":763,"org":764,"tags":765,"stars":28,"repoUrl":29,"updatedAt":30},"accessibility-and-inclusive-visualization","make data visualizations accessible","Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[766,769,772,773],{"name":767,"slug":768,"type":15},"Accessibility","accessibility",{"name":770,"slug":771,"type":15},"Charts","charts",{"name":20,"slug":21,"type":15},{"name":774,"slug":775,"type":15},"Design","design",{"slug":777,"name":777,"fn":778,"description":779,"org":780,"tags":781,"stars":28,"repoUrl":29,"updatedAt":791},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[782,785,788],{"name":783,"slug":784,"type":15},"Agents","agents",{"name":786,"slug":787,"type":15},"Browser Automation","browser-automation",{"name":789,"slug":790,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":793,"name":793,"fn":794,"description":795,"org":796,"tags":797,"stars":28,"repoUrl":29,"updatedAt":803},"agent-browser-verify","verify dev server output with automated browser","Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass\u002Ffail before continuing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[798,799,802],{"name":786,"slug":787,"type":15},{"name":800,"slug":801,"type":15},"Local Development","local-development",{"name":789,"slug":790,"type":15},"2026-04-06T18:41:17.526867",{"slug":805,"name":805,"fn":806,"description":807,"org":808,"tags":809,"stars":28,"repoUrl":29,"updatedAt":823},"agents-sdk","build AI agents on Cloudflare Workers","Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[810,811,814,817,820],{"name":783,"slug":784,"type":15},{"name":812,"slug":813,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":815,"slug":816,"type":15},"SDK","sdk",{"name":818,"slug":819,"type":15},"Serverless","serverless",{"name":821,"slug":822,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":825,"name":825,"fn":826,"description":827,"org":828,"tags":829,"stars":28,"repoUrl":29,"updatedAt":845},"ai-elements","build chat UIs with AI Elements","AI Elements component library guidance — pre-built React components for AI interfaces built on shadcn\u002Fui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[830,833,836,839,842],{"name":831,"slug":832,"type":15},"Frontend","frontend",{"name":834,"slug":835,"type":15},"React","react",{"name":837,"slug":838,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":840,"slug":841,"type":15},"UI Components","ui-components",{"name":843,"slug":844,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":847,"name":847,"fn":848,"description":849,"org":850,"tags":851,"stars":28,"repoUrl":29,"updatedAt":863},"ai-gateway","configure Vercel AI Gateway","Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[852,855,858,861,862],{"name":853,"slug":854,"type":15},"AI Infrastructure","ai-infrastructure",{"name":856,"slug":857,"type":15},"Cost Optimization","cost-optimization",{"name":859,"slug":860,"type":15},"LLM","llm",{"name":13,"slug":14,"type":15},{"name":843,"slug":844,"type":15},"2026-04-06T18:40:44.377464",{"slug":865,"name":865,"fn":866,"description":867,"org":868,"tags":869,"stars":28,"repoUrl":29,"updatedAt":875},"ai-generation-persistence","implement persistence patterns for AI generations","AI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[870,871,874],{"name":856,"slug":857,"type":15},{"name":872,"slug":873,"type":15},"Database","database",{"name":859,"slug":860,"type":15},"2026-04-06T18:41:08.513425",600,{"items":878,"total":1075},[879,900,923,940,956,973,992,1004,1018,1032,1044,1059],{"slug":880,"name":880,"fn":881,"description":882,"org":883,"tags":884,"stars":897,"repoUrl":898,"updatedAt":899},"prior-auth-packet-builder","build healthcare prior authorization packets","Build a concise prior authorization packet from local case files and payer policy docs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[885,888,891,894],{"name":886,"slug":887,"type":15},"Documents","documents",{"name":889,"slug":890,"type":15},"Healthcare","healthcare",{"name":892,"slug":893,"type":15},"Insurance","insurance",{"name":895,"slug":896,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":901,"name":901,"fn":902,"description":903,"org":904,"tags":905,"stars":920,"repoUrl":921,"updatedAt":922},"aspnet-core","build ASP.NET Core web applications","Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[906,909,911,914,917],{"name":907,"slug":908,"type":15},".NET","dotnet",{"name":910,"slug":901,"type":15},"ASP.NET Core",{"name":912,"slug":913,"type":15},"Blazor","blazor",{"name":915,"slug":916,"type":15},"C#","csharp",{"name":918,"slug":919,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":924,"name":924,"fn":925,"description":926,"org":927,"tags":928,"stars":920,"repoUrl":921,"updatedAt":939},"chatgpt-apps","build ChatGPT Apps SDK applications","Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[929,932,935,938],{"name":930,"slug":931,"type":15},"Apps SDK","apps-sdk",{"name":933,"slug":934,"type":15},"ChatGPT","chatgpt",{"name":936,"slug":937,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":941,"name":941,"fn":942,"description":943,"org":944,"tags":945,"stars":920,"repoUrl":921,"updatedAt":955},"cli-creator","build CLIs from API docs","Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[946,949,952],{"name":947,"slug":948,"type":15},"API Development","api-development",{"name":950,"slug":951,"type":15},"CLI","cli",{"name":953,"slug":954,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":957,"name":957,"fn":958,"description":959,"org":960,"tags":961,"stars":920,"repoUrl":921,"updatedAt":972},"cloudflare-deploy","deploy projects to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[962,965,968,969],{"name":963,"slug":964,"type":15},"Cloudflare","cloudflare",{"name":966,"slug":967,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":812,"slug":813,"type":15},{"name":970,"slug":971,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":974,"name":974,"fn":975,"description":976,"org":977,"tags":978,"stars":920,"repoUrl":921,"updatedAt":991},"define-goal","define and set measurable project goals","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[979,982,985,988],{"name":980,"slug":981,"type":15},"Productivity","productivity",{"name":983,"slug":984,"type":15},"Project Management","project-management",{"name":986,"slug":987,"type":15},"Strategy","strategy",{"name":989,"slug":990,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":993,"name":993,"fn":994,"description":995,"org":996,"tags":997,"stars":920,"repoUrl":921,"updatedAt":1003},"figma","translate Figma designs into code","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[998,999,1001,1002],{"name":774,"slug":775,"type":15},{"name":1000,"slug":993,"type":15},"Figma",{"name":831,"slug":832,"type":15},{"name":936,"slug":937,"type":15},"2026-04-12T05:06:47.939943",{"slug":1005,"name":1005,"fn":1006,"description":1007,"org":1008,"tags":1009,"stars":920,"repoUrl":921,"updatedAt":1017},"figma-code-connect-components","connect Figma designs to code components","Connects Figma design components to code components using Code Connect mapping tools. Use when user says \"code connect\", \"connect this component to code\", \"map this component\", \"link component to code\", \"create code connect mapping\", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1010,1011,1014,1015,1016],{"name":774,"slug":775,"type":15},{"name":1012,"slug":1013,"type":15},"Design System","design-system",{"name":1000,"slug":993,"type":15},{"name":831,"slug":832,"type":15},{"name":840,"slug":841,"type":15},"2026-05-10T05:59:52.971881",{"slug":1019,"name":1019,"fn":1020,"description":1021,"org":1022,"tags":1023,"stars":920,"repoUrl":921,"updatedAt":1031},"figma-create-design-system-rules","generate design system rules from Figma","Generates custom design system rules for the user's codebase. Use when user says \"create design system rules\", \"generate rules for my project\", \"set up design rules\", \"customize design system guidelines\", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1024,1025,1026,1029,1030],{"name":774,"slug":775,"type":15},{"name":1012,"slug":1013,"type":15},{"name":1027,"slug":1028,"type":15},"Documentation","documentation",{"name":1000,"slug":993,"type":15},{"name":831,"slug":832,"type":15},"2026-05-16T06:07:47.821474",{"slug":1033,"name":1033,"fn":1034,"description":1035,"org":1036,"tags":1037,"stars":920,"repoUrl":921,"updatedAt":1043},"figma-implement-design","translate Figma designs into application code","Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions \"implement design\", \"generate code\", \"implement component\", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1038,1039,1040,1041,1042],{"name":774,"slug":775,"type":15},{"name":1000,"slug":993,"type":15},{"name":831,"slug":832,"type":15},{"name":840,"slug":841,"type":15},{"name":918,"slug":919,"type":15},"2026-05-16T06:07:40.583615",{"slug":1045,"name":1045,"fn":1046,"description":1047,"org":1048,"tags":1049,"stars":920,"repoUrl":921,"updatedAt":1058},"hatch-pet","create animated pets for Codex","Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1050,1053,1054,1057],{"name":1051,"slug":1052,"type":15},"Animation","animation",{"name":953,"slug":954,"type":15},{"name":1055,"slug":1056,"type":15},"Creative","creative",{"name":774,"slug":775,"type":15},"2026-05-02T05:31:48.48485",{"slug":1060,"name":1060,"fn":1061,"description":1062,"org":1063,"tags":1064,"stars":920,"repoUrl":921,"updatedAt":1074},"imagegen","generate and edit raster images","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1065,1066,1067,1070,1073],{"name":1055,"slug":1056,"type":15},{"name":774,"slug":775,"type":15},{"name":1068,"slug":1069,"type":15},"Image Generation","image-generation",{"name":1071,"slug":1072,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]