theme-authoring

作者: microsoft

在Ontology Playground中添加新的颜色主题。当有人想要创建、编写或接入主题、调色板、配色方案、深色模式或浅色模式时使用。

npx skills add https://github.com/microsoft/ontology-playground --skill theme-authoring

Theme Authoring Skill

Goal

Plug a new color theme into the Playground so it appears in the header theme picker, is remembered across sessions, and themes every surface (main graph, designer preview, learn pages) — with no component or graph-rendering edits.

Read First

  1. docs/theme-authoring-guide.md — full architecture, token table, gotchas, worked example.
  2. src/store/appStore.ts — ThemeId, THEME_OPTIONS, DARK_BASED_THEMES, isDarkTheme, themeClass.
  3. src/styles/app.css — the :root / .light-theme / .theme-aurora / .theme-crimson token blocks (copy the nearest one).

Intake Questions

Ask the user:

  1. Theme id (lowercase, e.g. indigo) and display label (e.g. Indigo)?
  2. Dark-based or light-based? (Determines DARK_BASED_THEMES membership and which block to copy.)
  3. Accent / signature color (used for the picker swatch and --ms-blue* / --info)?
  4. Any specific surface, text, or graph colors, or should they be derived from the accent?

Procedure

Make all edits in src/store/appStore.ts and src/styles/app.css. The guide's "Add a theme in six steps" section has copy-paste snippets.

  1. Add the id to the ThemeId union.
  2. Add a THEME_OPTIONS entry: { id, label, swatch } (swatch = accent hex).
  3. If dark-based, add the id to DARK_BASED_THEMES. If light-based, leave it out.
  4. Add a themeClass() case:
    • dark-based → return 'theme-<id>';
    • light-based → return 'light-theme theme-<id>'; (layer over the light base).
  5. Add a .theme-<id> block in app.css by copying .theme-aurora (dark) or .theme-crimson (light) and retuning the tokens.
  6. Verify (see below).

Critical Rules

  • Opaque canvas base for light themes. --chess-square-light is the graph canvas's solid backdrop. The theme class sits on .app-container, not <body>, and <body> stays dark (#1B1B1B). A translucent --chess-square-light lets the dark body bleed through → dark canvas + unreadable labels. Use an opaque light color (e.g. #FBF7F8), not rgba(..., 0.03). (Guide → Gotcha 1.)
  • Graph colors are CSS-driven. Define --graph-bg, --graph-node-text, --graph-edge-color, --graph-edge-text, --graph-edge-label-bg in the block; the graph and designer read them at runtime. No .tsx edits.
  • Meet WCAG 2.1 AA contrast. Text and labels need 4.5:1; graph edge lines and other non-text need 3:1. Set --on-accent (label color on accent fills) to a dark value for a light accent (white fails on Aurora's mint) and white for a dark accent. Edge text must clear 4.5:1 against --graph-edge-label-bg. Stat-tile icons/values (--stat-blue/green/purple) need 3:1 over the tint and cascade automatically (bright from :root, dark from .light-theme). Amber text/icons use --ms-yellow-fg (bright #FFB900 on dark, dark gold #8A6A00 on light); the .progress-fill stops --progress-from/--progress-to each need 3:1 on the --bg-tertiary track. npm run test:a11y enforces this for every theme. (Guide → Accessibility.)
  • Register dark themes in DARK_BASED_THEMES so darkMode is correct (graph fallback, label backplate, PNG export bg).
  • Don't introduce brand names in ids, labels, comments, or commits. Use generic palette names (e.g. Aurora, Crimson, Indigo, Sand).

Person Names

If any example data, docs, or sample instances need person names, use the name-generator skill — do not invent names.

Validate

npm run dev          # switch to the theme in the header; check graph, designer, learn pages
npm run test:a11y    # WCAG 2.1 AA contrast for every theme (also a CI gate)
npx tsc --noEmit     # the ThemeId union change is type-checked here
npm run build        # full build

If npm run build only changed public/learn.json (a timestamp), revert it: git checkout -- public/learn.json.

Done Criteria

  • New swatch + label appear in the picker; selection check mark tracks state.
  • Theme persists across reload (localStorage['theme']).
  • Main graph, designer preview, and learn pages are legible in the new theme; the graph canvas backdrop matches the theme (Gotcha 1 satisfied).
  • Dark, Light, Aurora, Crimson unchanged.
  • npm run test:a11y passes (WCAG 2.1 AA contrast for the new theme).
  • tsc --noEmit and npm run build pass; no brand references introduced.

来自 microsoft 的更多技能

oss-growth
microsoft
OSS增长黑客角色
agent-framework-azure-ai-py
microsoft
使用Microsoft Agent Framework Python SDK(agent-framework-azure-ai)构建Azure AI Foundry代理。在创建使用AzureAIAgentsProvider的持久化代理、使用托管工具(代码解释器、文件搜索、网络搜索)、集成MCP服务器、管理对话线程或实现流式响应时使用。涵盖函数工具、结构化输出和多工具代理。
development
airunway-aks-setup
microsoft
在AKS上设置AI Runway——从裸集群到运行模型。涵盖集群验证、控制器安装、GPU评估、提供商设置和首次部署。适用场景:“设置AI Runway”、“接入AKS集群”、“安装AI Runway”、“airunway设置”、“将模型部署到AKS”、“在AKS上进行GPU推理”、“在AKS上配置KAITO”、“在AKS上运行LLM”、“在AKS上使用vLLM”、“在AKS上设置模型服务”、“AI Runway控制器”。
devops
appinsights-instrumentation
microsoft
使用Azure Application Insights对Web应用进行插桩的指南。提供遥测模式、SDK设置和配置参考。适用场景:如何对应用进行插桩、App Insights SDK、遥测模式、什么是App Insights、Application Insights指南、插桩示例、APM最佳实践。
devops
applicationinsights-web-ts
microsoft
使用Application Insights JavaScript SDK(@microsoft/applicationinsights-web)为浏览器/Web应用添加检测。用于真实用户监控(RUM)——页面视图、点击、AJAX/fetch依赖项、异常、自定义事件,以及与后端OpenTelemetry追踪关联的浏览器端GenAI代理追踪。涵盖SDK加载器脚本和npm设置、框架扩展(React、React Native、Angular)、点击分析、遥测初始化器,以及从浏览器发出的代理/工具/模型跨度所遵循的OTel GenAI语义约定。
devops
azure-ai-anomalydetector-java
microsoft
使用适用于 Java 的 Azure AI 异常检测器 SDK 构建异常检测应用程序。在实现单变量/多变量异常检测、时间序列分析或 AI 驱动的监控时使用。
development
azure-ai-language-conversations-py
microsoft
使用azure-ai-language-conversations Python SDK实现对话语言理解(CLU)。当使用ConversationAnalysisClient分析对话意图和实体、构建NLP功能或将语言理解集成到应用程序中时使用。
development
azure-ai-ml-py
microsoft
Azure Machine Learning SDK v2 for Python。用于机器学习工作区、作业、模型、数据集、计算资源和管道。 触发词:“azure-ai-ml”、“MLClient”、“工作区”、“模型注册表”、“训练作业”、“数据集”。
development