Files
open-design/plugins/_official/examples/replit-deck/open-design.json
f1a0b60c6c chore: unify product name display to OpenDesign repo-wide (#6998)
* 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>
2026-08-18 07:09:45 +00:00

138 lines
5.8 KiB
JSON

{
"$schema": "https://open-design.ai/schemas/plugin.v1.json",
"specVersion": "1.0.0",
"name": "example-replit-deck",
"title": "Write a Feature Business Case like a Principal PM",
"title_i18n": {
"en": "Write a Feature Business Case like a Principal PM",
"zh-CN": "像 Principal PM 一样写功能商业论证",
"zh-TW": "像 Principal PM 一样写功能商业论证"
},
"version": "0.1.0",
"publishedAt": "2026-05-12T07:18:16Z",
"description": "For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query \"pm-feature-business-case-deck\", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident follow-up.",
"description_i18n": {
"en": "For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query \"pm-feature-business-case-deck\", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident follow-up.",
"zh-CN": "产品/技术管理场景:围绕 core query「pm-feature-business-case-deck」把粗糙材料整理成“像 Principal PM 一样写功能商业论证”这类可购买、可复用的专业 Deck;突出受众、决策目标、证据链、风险取舍和评审标准。",
"zh-TW": "产品/技术管理场景:围绕 core query「pm-feature-business-case-deck」把粗糙材料整理成“像 Principal PM 一样写功能商业论证”这类可购买、可复用的专业 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/replit-deck",
"tags": [
"example",
"first-party",
"deck",
"product",
"web",
"replit-deck",
"replit-slides",
"replit-ppt",
"replit-style-deck",
"helix-deck",
"holm-memo",
"atlas-chapter",
"bluehouse",
"bevel-campaign",
"product-management",
"pm-feature-business-case-deck",
"roadmap",
"architecture",
"decision-deck",
"commercial-slide-agent",
"product-and-technical-management"
],
"compat": {
"agentSkills": [
{
"path": "./SKILL.md"
}
]
},
"od": {
"kind": "scenario",
"taskKind": "new-generation",
"mode": "deck",
"scenario": "product",
"surface": "web",
"preview": {
"type": "html",
"entry": "./index.html"
},
"useCase": {
"query": {
"en": "Create \"Write a Feature Business Case like a Principal PM\" as a Product and technical management deck in the Replit Deck visual system. Scene: pm-feature-business-case-deck. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce a commercial-grade slide plan, written slides, visual direction, speaker-ready structure, and critic pass against this rubric: can cross-functional reviewers agree on the next irreversible step.",
"zh-CN": "像 Principal PM 一样写功能商业论证。产品/技术管理场景:围绕 core query「pm-feature-business-case-deck」把粗糙材料整理成“像 Principal PM 一样写功能商业论证”这类可购买、可复用的专业 Deck;突出受众、决策目标、证据链、风险取舍和评审标准。 先确认受众、决策目标、素材来源、截止时间和必须保留的数据,再输出叙事主线、页面规划、逐页文案、视觉方向和按评审标准自检的版本。"
},
"exampleOutputs": [
{
"path": "./example.html",
"title": "Write a Feature Business Case like a Principal PM",
"title_i18n": {
"en": "Write a Feature Business Case like a Principal PM",
"zh-CN": "像 Principal PM 一样写功能商业论证",
"zh-TW": "像 Principal PM 一样写功能商业论证"
}
}
]
},
"inputs": [
{
"name": "theme",
"type": "string",
"required": true,
"default": "helix",
"values": [
"helix # Modern minimal · light grey · ink + electric blue · SaaS metrics / board",
"holm # Editorial serif · cream · ink + deep chestnut · legal / finance memo",
"vance # Gallery · cream · cream serif on black bars · art catalog / showcase",
"bevel # Y2K editorial · black · display type + product photo grid · campaign",
"world-dark # Finance green dark · deep green · mint + neon yellow · policy report",
"world-mint # Finance green light · mint · deep green + neon yellow · policy report",
"atlas # Museum · black · serif + vermilion · long-form narrative / chapter deck",
"bluehouse # Consumer card · deep navy · gradient cards + peach → coral · product showcase"
]
},
{
"name": "slide_count",
"type": "number",
"default": 6,
"min": 3,
"max": 20
}
],
"context": {
"skills": [
{
"path": "./SKILL.md"
}
],
"assets": [
"./assets/template.html",
"./references/checklist.md",
"./references/components.md",
"./references/layouts.md",
"./references/themes.md"
]
},
"pipeline": {
"stages": [
{
"id": "generate",
"atoms": [
"file-write",
"live-artifact"
]
}
]
},
"capabilities": [
"prompt:inject",
"fs:write"
]
}
}