Files
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

24 lines
772 B
Markdown

---
name: refine-critique-loop
description: Use this plugin when the user has an existing OpenDesign artifact and wants targeted critique, patching, brand tightening, responsive fixes, or quality improvement without starting over.
license: MIT
metadata:
author: open-design-spec
version: "0.1.0"
---
# Refine Critique Loop
## Workflow
1. Read the existing artifact and identify the user's refinement goal.
2. Run a structured critique for hierarchy, fit, accessibility, responsiveness, and artifact-specific quality.
3. Apply the smallest useful patch.
4. Re-run critique and stop when quality converges or the iteration limit is reached.
5. Return a diff summary and what changed.
## Output Contract
Patch the existing artifact and produce `refine-summary.md`.