mirror of
https://github.com/nexu-io/open-design.git
synced 2026-09-20 06:15:06 +08:00
f1a0b60c6c
* chore: unify product name display to OpenDesign repo-wide Rename the user-facing product name from "Open Design" to "OpenDesign" across documentation, web/desktop UI strings, i18n locales, prompts, plugin/skill/design-system content, changelogs, and specs, matching the landing-page rename already in flight. Deliberately excluded so installed-app identity stays untouched: - packages/release PRODUCT_NAME and everything derived from it (app bundle names, installer/registry identity, updater feeds) - tools/pack, tools/release, apps/packaged, landing page (PR #6983) - mocks/ recorded traces and LICENSE - test fixtures and comments that encode real on-disk install paths (Open Design.app, Program Files\Open Design, AppData paths) Validated with pnpm guard, pnpm typecheck, and targeted web/desktop/host test runs over the renamed strings. * fix(web): keep two-letter author monogram for CamelCase brand names authorInitials split words on whitespace only, so the renamed single-token author name "OpenDesign" produced a one-letter monogram. Treat lower-to-upper CamelCase boundaries as word breaks so the avatar fallback stays "OD". * fix(release): restore spaced Windows source artifact names in win.ps1 tools/pack still derives builder outputs from the unchanged PRODUCT_NAME ("Open Design"), so the asset script must look for the spaced filenames. Matches the mac/mac-intel/linux asset scripts, which were already kept on the original names. --------- Co-authored-by: Joey <236967869+joeylee12629-star@users.noreply.github.com>
109 lines
4.1 KiB
JSON
109 lines
4.1 KiB
JSON
{
|
||
"$schema": "https://open-design.ai/schemas/plugin.v1.json",
|
||
"specVersion": "1.0.0",
|
||
"name": "example-html-ppt-tech-sharing",
|
||
"title": "Give an Engineering Tech Talk like a Staff Developer-Advocate",
|
||
"title_i18n": {
|
||
"en": "Give an Engineering Tech Talk like a Staff Developer-Advocate",
|
||
"zh-CN": "像 Staff DevRel 一样做工程分享",
|
||
"zh-TW": "像 Staff DevRel 一样做工程分享"
|
||
},
|
||
"version": "0.1.0",
|
||
"publishedAt": "2026-05-12T07:18:16Z",
|
||
"description": "OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Built as a decision-grade AI literacy deck for engineers, dev community.",
|
||
"description_i18n": {
|
||
"en": "OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Built as a decision-grade AI literacy deck for engineers, dev community.",
|
||
"zh-CN": "像 Staff DevRel 一样做工程分享——一份可商业交付的AI 素养 Deck,围绕真实主题、证据链与决策目标组织。",
|
||
"zh-TW": "像 Staff DevRel 一样做工程分享——一份可商业交付的AI 素养 Deck,围绕真实主题、证据链与决策目标组织。"
|
||
},
|
||
"license": "MIT",
|
||
"author": {
|
||
"name": "OpenDesign",
|
||
"url": "https://github.com/nexu-io"
|
||
},
|
||
"homepage": "https://github.com/nexu-io/open-design/tree/main/plugins/_official/examples/html-ppt-tech-sharing",
|
||
"tags": [
|
||
"example",
|
||
"first-party",
|
||
"deck",
|
||
"engineering",
|
||
"web",
|
||
"tech-sharing",
|
||
"tech-talk",
|
||
"untitled",
|
||
"engineering-talk",
|
||
"conference-talk",
|
||
"dev-talk",
|
||
"ai",
|
||
"copilot",
|
||
"workflow",
|
||
"html-ppt-tech-sharing",
|
||
"enterprise-ai-literacy",
|
||
"ai-literacy",
|
||
"enterprise-ai-copilot-rollout-brief",
|
||
"decision-deck",
|
||
"commercial-slide-agent"
|
||
],
|
||
"compat": {
|
||
"agentSkills": [
|
||
{
|
||
"path": "./SKILL.md"
|
||
}
|
||
]
|
||
},
|
||
"od": {
|
||
"kind": "scenario",
|
||
"taskKind": "new-generation",
|
||
"mode": "deck",
|
||
"scenario": "ai",
|
||
"surface": "web",
|
||
"preview": {
|
||
"type": "html",
|
||
"entry": "./example.html"
|
||
},
|
||
"useCase": {
|
||
"query": {
|
||
"en": "Create \"Give an Engineering Tech Talk like a Staff Developer-Advocate\" as a decision-grade AI literacy deck in this template's own visual system. Subject: OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Audience: engineers, dev community. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce the slide plan, written slides, visual direction, speaker-ready structure, and a critic pass against this rubric: does the deck make AI implementation concrete enough to fund.",
|
||
"zh-CN": "像 Staff DevRel 一样做工程分享。像 Staff DevRel 一样做工程分享——一份可商业交付的AI 素养 Deck,围绕真实主题、证据链与决策目标组织。 主题:OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. 先确认受众、决策目标、素材来源、截止时间和必须保留的数据,再输出叙事主线、页面规划、逐页文案、视觉方向和按评审标准自检的版本。"
|
||
},
|
||
"exampleOutputs": [
|
||
{
|
||
"path": "./example.html",
|
||
"title": "Give an Engineering Tech Talk like a Staff Developer-Advocate",
|
||
"title_i18n": {
|
||
"en": "Give an Engineering Tech Talk like a Staff Developer-Advocate",
|
||
"zh-CN": "像 Staff DevRel 一样做工程分享",
|
||
"zh-TW": "像 Staff DevRel 一样做工程分享"
|
||
}
|
||
}
|
||
]
|
||
},
|
||
"context": {
|
||
"skills": [
|
||
{
|
||
"path": "./SKILL.md"
|
||
}
|
||
],
|
||
"assets": [
|
||
"./example.html"
|
||
]
|
||
},
|
||
"pipeline": {
|
||
"stages": [
|
||
{
|
||
"id": "generate",
|
||
"atoms": [
|
||
"file-write",
|
||
"live-artifact"
|
||
]
|
||
}
|
||
]
|
||
},
|
||
"capabilities": [
|
||
"prompt:inject",
|
||
"fs:write"
|
||
],
|
||
"category": "ai-literacy"
|
||
}
|
||
}
|