launch-identity

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

launch-identity

Nothing signals "unfinished" like a browser tab that says "Vite + React" with a purple lightning-bolt icon. This skill makes the product's name and icon the same everywhere a visitor could see them.

浏览器标签页标题写着“Vite + React”，旁边还配着紫色闪电图标，这种组合最能让人一眼看出网站尚未完成。这个 skill 会让产品名称和图标在所有访客可能看到的位置保持一致。

Activate when

何时启用

Titles, favicons, app names, manifest, or emails still show starter or template values, or names differ across the site.
Before launch, or after a rename/rebrand.
Not for designing identity, and not for legal entity naming (
```
legal-identity-notices
```
).

标题、favicon、应用名称、manifest 或电子邮件中仍显示初始值或模板值，或者网站各处的名称不一致。
上线前，或完成重命名或品牌重塑后。
不用于设计身份标识，也不用于法律实体命名（
```
legal-identity-notices
```
）。

Working alone

独立运行

This skill is self-contained. Its companions (declared in its metadata) are skills whose method it may need to do its own promised work. Use of a companion can be conditional: declaring one does not mean running it. When a companion's lane applies, use the skill if it is installed; if not, follow its short entry in references/companion-methods.md and say in your report which lanes ran inline at reduced depth. Never skip an applicable lane silently. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.

Companions:

design-system-reconnaissance

此 skill 是自包含的。它的 companions（在其 metadata 中声明）是指其方法在完成自身承诺工作时可能需要用到的 skills。使用 companion 可以是有条件的：声明某个 companion 并不代表一定会运行它。当某个 companion 的工作环节适用时，如果该 skill 已安装，请使用它；如果未安装，则按照 [references/companion-methods.md] 中的简短说明操作，并在报告中说明哪些工作环节以较低深度在当前流程中内联完成。绝不静默跳过任何适用环节。这里提到的 skills 仅用于升级处理、转介、文档记录或可选的后续深入工作，并不属于依赖项：应报告交接情况，并如实完成工作。

Companions：

design-system-reconnaissance

。

Inspect

检查

Canonical identity from the owner (DECLARED): product name, tagline (if any), logo files, brand colors. Find it in README, docs, logo assets, existing copy; ask once if genuinely absent.
Starter/template residue (search rendered output and source): "Vite + React", "Create Next App", "React App", "Astro", "Document", "Untitled", "My App", "Your Company", "Acme", "Lovable/bolt/v0 App", default
```
vite.svg
```
/
```
next.svg
```
/
```
favicon.ico
```
from the template,
```
logo192.png
```
/
```
manifest.json
```
from CRA, generator meta tags, placeholder author fields in
```
package.json
```
and metadata (
```
author
```
,
```
description
```
,
```
name
```
).
Where identity appears:
```
<title>
```
and site name pattern; OG
```
site_name
```
; header/logo alt text; footer name and copyright; manifest
```
name
```
/
```
short_name
```
; app-store-ish fields; email "From" names and template headers; error pages; PWA/splash; docs/README;
```
package.json
```
name.
Icons: favicon (
```
.ico
```
or
```
.svg
```
),
```
apple-touch-icon
```
(180×180), manifest icons (192, 512, maskable if a PWA), theme color; all files exist, load (200), are square/appropriately sized, look right on light and dark tab backgrounds, are not the framework's.
Consistency: the same product name spelling and casing everywhere; no old names after a rename; the domain matches the name in metadata.

Run

node scripts/inspect-metadata.mjs --url <site>

(paths relative to this skill's folder):

META_TITLE_STARTER

FAVICON_MISSING

FAVICON_STARTER

FAVICON_BROKEN

规范身份（DECLARED）：从所有者处获取产品名称、tagline（如有）、logo 文件和品牌颜色。可在 README、docs、logo 资产和现有文案中查找；如果确实缺失，则询问一次。
初始模板或模板残留（在渲染输出和源代码中搜索）：“Vite + React”、“Create Next App”、“React App”、“Astro”、“Document”、“Untitled”、“My App”、“Your Company”、“Acme”、“Lovable/bolt/v0 App”、模板自带的默认
```
vite.svg
```
/
```
next.svg
```
/
```
favicon.ico
```
、来自 CRA 的
```
logo192.png
```
/
```
manifest.json
```
、生成器 meta tags，以及
```
package.json
```
和 metadata（
```
author
```
、
```
description
```
、
```
name
```
）中的占位 author 字段。
**身份信息的出现位置：
```
<title>
```
和网站名称格式；OG
```
site_name
```
；header/logo 的 alt text；footer 中的名称和版权信息；manifest 的
```
name
```
/
```
short_name
```
；类似应用商店的字段；电子邮件的“发件人”名称和模板 header；错误页面；PWA/splash；docs/README；
```
package.json
```
的 name。
**图标：**favicon（
```
.ico
```
或
```
.svg
```
）、
```
apple-touch-icon
```
（180×180）、manifest 图标（192、512，如果用于 PWA 则还需 maskable）、theme color；确认所有文件均存在、可以正常加载（200）、为正方形或尺寸适当、在浅色和深色标签页背景中显示正常，并且不是框架自带的图标。
**一致性：**所有位置使用相同的产品名称拼写和大小写；重命名后不再残留旧名称；metadata 中的名称与域名一致。

运行

node scripts/inspect-metadata.mjs --url <site>

（路径相对于此 skill 所在文件夹）：

META_TITLE_STARTER

、

FAVICON_MISSING

、

FAVICON_STARTER

、

FAVICON_BROKEN

。

Evidence that counts

有效证据

Label each claim OBSERVED, SOURCE-INDICATED, DECLARED, INFERRED, UNKNOWN, or REVIEW REQUIRED. UNKNOWN is never a pass and never a failure.

The rendered
```
<title>
```
and icon links are OBSERVED; source strings are SOURCE-INDICATED.
The product name is DECLARED by the owner. Do not infer a name from a repo folder or package name if they conflict with visible copy; ask.

将每项结论标记为 OBSERVED、SOURCE-INDICATED、DECLARED、INFERRED、UNKNOWN 或 REVIEW REQUIRED。UNKNOWN 既不算通过，也不算失败。

渲染后的
```
<title>
```
和图标链接属于 OBSERVED；源代码中的字符串属于 SOURCE-INDICATED。
产品名称由所有者 DECLARED。如果 repo 文件夹名或 package name 与可见文案冲突，不要据此推断名称；应进行询问。

May change

可以更改的内容

Design first. Before creating or changing anything visible, inspect the project's existing design system (

design-system-reconnaissance

) and build from its tokens and components, by the component ladder: reuse, compose, extend, and only then create a matching component. Never impose a ReadyVibe look on the user's site.

Replace starter titles/descriptions with product-specific values derived from owner-provided identity and visible content; swap the favicon and icons for the owner's logo (resize/convert existing brand assets; do not redraw); add missing

apple-touch-icon

and manifest icons; fix names in metadata, manifest, package fields; update copyright name to the owner-supplied one. If no logo exists, a neutral text-monogram icon in the brand color (clearly a placeholder) is acceptable only if the owner agrees; otherwise ask.

**设计优先。**在创建或更改任何可见内容之前，先检查项目现有的设计系统（

design-system-reconnaissance

），并按照 component ladder 基于其 tokens 和 components 进行构建：依次执行复用、组合、扩展，只有之后才创建匹配的 component。绝不能将 ReadyVibe 风格强加给用户的网站。

使用根据所有者提供的身份信息和可见内容得出的产品专属值，替换初始标题和描述；将 favicon 和图标替换为所有者的 logo（可调整或转换现有品牌资产的尺寸和格式；不要重绘）；添加缺失的

apple-touch-icon

和 manifest 图标；修正 metadata、manifest 和 package 字段中的名称；将版权信息中的名称更新为所有者提供的名称。如果不存在 logo，只有在所有者同意时，才可以使用采用品牌颜色的中性文字组合图标（并明确标记为 placeholder）；否则应询问。

Must not claim

不得声称

That branding is "final" or "trademarked". Do not invent a company/legal name, tagline, logo, or brand colors.

不得声称品牌是“最终版本”或“已注册商标”。不得虚构公司或法律实体名称、tagline、logo 或品牌颜色。

Verify

验证

Re-run

inspect-metadata

; view the tab title/icon on the running site (light and dark); load each icon URL; search rendered pages for the starter strings and confirm none remain; confirm manifest validity if present.

重新运行

inspect-metadata

；查看运行中网站的标签页标题和图标（浅色与深色模式）；加载每个图标 URL；在渲染后的页面中搜索初始字符串并确认没有残留；如果存在 manifest，则确认其有效性。

Escalate

升级处理

Missing brand assets, conflicting names among owner materials, or possible trademark conflicts: ask the owner; recommend a clearance search before a commercial launch.

如果缺少品牌资产、所有者提供的资料之间存在名称冲突，或可能存在商标冲突：询问所有者；建议在商业上线前进行 clearance search。

No change is valid when

无需更改的情况

Identity is consistent, no starter residue remains, and icons are the owner's. Do not restyle a working favicon.

身份信息一致、没有初始模板残留，且图标归所有者所有时，无需进行更改。不要为可正常工作的 favicon 重新设计样式。