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>
129 lines
7.1 KiB
JSON
129 lines
7.1 KiB
JSON
{
|
||
"$schema": "https://open-design.ai/schemas/plugin.v1.json",
|
||
"specVersion": "1.0.0",
|
||
"name": "example-pm-spec",
|
||
"title": "Pm Spec",
|
||
"title_i18n": {
|
||
"zh-CN": "产品规格文档",
|
||
"zh-TW": "產品規格文件",
|
||
"ja": "プロダクト仕様書",
|
||
"ko": "제품 명세서",
|
||
"de": "Produktspezifikation",
|
||
"fr": "Spécification produit",
|
||
"ru": "Спецификация продукта",
|
||
"es": "Especificación de producto",
|
||
"pt-BR": "Especificação de produto",
|
||
"it": "Specifica prodotto",
|
||
"vi": "Đặc tả sản phẩm",
|
||
"pl": "Specyfikacja produktu",
|
||
"id": "Spesifikasi produk",
|
||
"nl": "Productspecificatie",
|
||
"ar": "مواصفات المنتج",
|
||
"tr": "Ürün spesifikasyonu",
|
||
"uk": "Специфікація продукту",
|
||
"en": "Pm Spec"
|
||
},
|
||
"version": "0.1.0",
|
||
"publishedAt": "2026-05-12T07:18:16Z",
|
||
"description": "Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions \"PRD\", \"spec\", \"product spec\", \"feature brief\", or \"需求文档\".",
|
||
"description_i18n": {
|
||
"zh-CN": "单页产品规格文档/PRD——包含问题定义、成功指标、范围、用户故事、设计笔记、上线计划、待解决问题。适用于需求文档、产品规格、功能说明等场景。",
|
||
"zh-TW": "單頁產品規格文件/PRD——包含問題定義、成功指標、範圍、使用者故事、設計筆記、上線計畫、待解決問題。適用於需求文件、產品規格、功能說明等場景。",
|
||
"ja": "1ページのプロダクト仕様書/PRD——課題、成功指標、スコープ、ユーザーストーリー、デザインノート、ロールアウト計画、未解決の質問を記載。仕様書や要件定義書の作成に使用。",
|
||
"ko": "단일 페이지 제품 명세서/PRD — 문제 정의, 성공 지표, 범위, 사용자 스토리, 디자인 노트, 출시 계획, 미해결 질문 포함. 제품 명세 또는 기능 문서 작성 시 사용.",
|
||
"de": "Einseitige Produktspezifikation/PRD mit Problem, Erfolgsmetriken, Umfang, User Stories, Design-Notizen, Rollout-Plan und offenen Fragen. Für Produktspezifikationen und Feature-Briefs.",
|
||
"fr": "Spécification produit/PRD sur une page — problème, métriques de succès, périmètre, user stories, notes de design, plan de déploiement, questions ouvertes. Pour les specs produit et briefs fonctionnels.",
|
||
"ru": "Спецификация продукта/PRD на одной странице — проблема, метрики успеха, границы, пользовательские истории, заметки по дизайну, план внедрения, открытые вопросы. Для продуктовых спецификаций и фич.",
|
||
"es": "Especificación de producto/PRD en una página: problema, métricas de éxito, alcance, historias de usuario, notas de diseño, plan de lanzamiento, preguntas abiertas. Para especificaciones y briefs de funcionalidades.",
|
||
"pt-BR": "Especificação de produto/PRD em página única — problema, métricas de sucesso, escopo, histórias de usuário, notas de design, plano de lançamento, questões em aberto. Para specs de produto e briefs de funcionalidades.",
|
||
"it": "Specifica prodotto/PRD su singola pagina — problema, metriche di successo, ambito, user story, note di design, piano di rilascio, domande aperte. Per specifiche prodotto e brief funzionali.",
|
||
"vi": "Đặc tả sản phẩm/PRD trên một trang — vấn đề, chỉ số thành công, phạm vi, user stories, ghi chú thiết kế, kế hoạch triển khai, câu hỏi mở. Dùng cho tài liệu đặc tả và yêu cầu tính năng.",
|
||
"pl": "Jednostronicowa specyfikacja produktu/PRD — problem, metryki sukcesu, zakres, user stories, notatki projektowe, plan wdrożenia, otwarte pytania. Do specyfikacji produktowych i briefów funkcjonalności.",
|
||
"id": "Spesifikasi produk/PRD satu halaman — masalah, metrik kesuksesan, cakupan, user stories, catatan desain, rencana peluncuran, pertanyaan terbuka. Untuk spesifikasi produk dan brief fitur.",
|
||
"nl": "Productspecificatie/PRD op één pagina — probleem, succesmetrics, scope, user stories, ontwerpnotities, uitrolplan, openstaande vragen. Voor productspecificaties en feature briefs.",
|
||
"ar": "مواصفات المنتج/PRD في صفحة واحدة — المشكلة، مقاييس النجاح، النطاق، قصص المستخدم، ملاحظات التصميم، خطة الإطلاق، الأسئلة المفتوحة. لمواصفات المنتج وملخصات الميزات.",
|
||
"tr": "Tek sayfa ürün spesifikasyonu/PRD — problem, başarı metrikleri, kapsam, kullanıcı hikayeleri, tasarım notları, yayın planı, açık sorular. Ürün spesifikasyonları ve özellik brifleri için.",
|
||
"uk": "Специфікація продукту/PRD на одній сторінці — проблема, метрики успіху, масштаб, користувацькі історії, нотатки дизайну, план впровадження, відкриті питання. Для специфікацій продукту та брифів функцій.",
|
||
"en": "Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions \"PRD\", \"spec\", \"product spec\", \"feature brief\", or \"需求文档\"."
|
||
},
|
||
"license": "MIT",
|
||
"author": {
|
||
"name": "OpenDesign",
|
||
"url": "https://github.com/nexu-io"
|
||
},
|
||
"homepage": "https://github.com/nexu-io/open-design/tree/main/plugins/_official/examples/pm-spec",
|
||
"tags": [
|
||
"example",
|
||
"first-party",
|
||
"prototype",
|
||
"product",
|
||
"web",
|
||
"desktop",
|
||
"prd",
|
||
"spec",
|
||
"product-spec",
|
||
"feature-brief",
|
||
"feature-doc",
|
||
"untitled"
|
||
],
|
||
"compat": {
|
||
"agentSkills": [
|
||
{
|
||
"path": "./SKILL.md"
|
||
}
|
||
]
|
||
},
|
||
"od": {
|
||
"kind": "scenario",
|
||
"taskKind": "new-generation",
|
||
"mode": "prototype",
|
||
"platform": "desktop",
|
||
"scenario": "product",
|
||
"surface": "web",
|
||
"preview": {
|
||
"type": "html",
|
||
"entry": "./example.html"
|
||
},
|
||
"useCase": {
|
||
"query": {
|
||
"en": "Write me a PRD for adding two-factor auth to our SaaS app — problem, scope, milestones, open questions.",
|
||
"zh-CN": "使用这个插件完成以下任务:Write me a PRD for adding two-factor auth to our SaaS app — problem, scope, milestones, open questions."
|
||
},
|
||
"exampleOutputs": [
|
||
{
|
||
"path": "./example.html",
|
||
"title": "Pm Spec"
|
||
}
|
||
]
|
||
},
|
||
"context": {
|
||
"skills": [
|
||
{
|
||
"path": "./SKILL.md"
|
||
}
|
||
],
|
||
"designSystem": {
|
||
"primary": true
|
||
},
|
||
"assets": [
|
||
"./example.html"
|
||
]
|
||
},
|
||
"pipeline": {
|
||
"stages": [
|
||
{
|
||
"id": "generate",
|
||
"atoms": [
|
||
"file-write",
|
||
"live-artifact"
|
||
]
|
||
}
|
||
]
|
||
},
|
||
"capabilities": [
|
||
"prompt:inject",
|
||
"fs:write"
|
||
]
|
||
}
|
||
}
|