Back to Details

trust-all

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

trust-all

trust-all

Owns launch family C (checks 19–26). Trust is broader than badges: it is whether the product does what it visibly promises and looks like a real business. Visitors decide in seconds, and dead controls, lorem ipsum, invented metrics, and 404s in the footer are what they notice.
负责发布家族 C（检查项 19–26）。信任不仅关乎徽章，更在于产品是否切实履行其可见承诺，以及整体是否像一家真实企业。访客会在几秒内作出判断，而失效控件、lorem ipsum 占位文本、虚构指标，以及页脚中的 404 页面，恰恰是他们最容易注意到的问题。

Activate when

何时启用

  • The site is public and about to be shown to real users, investors, press, or customers.
  • launch-all
    routes here, or the user says "it feels unfinished / fake / sketchy".
  • Not for legal-page authoring (
    compliance-all
    ) or visual redesign (this repairs broken trust surfaces in the existing design).
  • 网站已公开，并即将展示给真实用户、投资者、媒体或客户。
  • launch-all
    路由到此处，或用户表示“它感觉未完成／虚假／可疑”。
  • 不适用于法律页面编写（
    compliance-all
    ）或视觉重新设计；本技能用于在现有设计中修复失效的信任界面。

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. The lanes this bundle can activate are companions because it promises to run them when they apply: consider them all, activate only the ones that fit. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.
Companions: 
content-trust
, 
faq-readiness
, 
error-pages
, 
link-integrity
, 
failure-resilience
, 
public-support
, 
launch-identity
, 
legal-navigation
.
此 skill 完全独立。其 companions（在元数据中声明）是本 skill 在履行自身承诺时可能需要借助其方法的各项技能。使用 companion 可以是有条件的：声明 companion 并不意味着一定会运行它。当某个 companion 的工作范围适用时，如果已安装该 skill，则应使用它；如果未安装，则按照 references/companion-methods.md 中的简要说明执行，并在报告中说明哪些工作范围以较低深度在当前流程中完成。绝不静默跳过任何适用工作范围。本 bundle 可激活的 lanes 之所以属于 companions，是因为它承诺在适用时运行这些技能：应考虑全部候选项，但仅激活真正匹配的技能。此处提及但仅用于升级、转交、文档说明或可选后续深入处理的技能并非依赖项：应如实报告转交情况并完成任务。
Companions：
content-trust
、
faq-readiness
、
error-pages
、
link-integrity
、
failure-resilience
、
public-support
、
launch-identity
、
legal-navigation
。

Route

路由

  1. Sweep once (paths relative to this skill's folder; 
    --render
    for client-rendered apps):
    bash
    node scripts/check-links.mjs  --url <site> --render     # broken links, dead hrefs, placeholders, mailto/tel
node scripts/audit-markup.mjs --url <site> --render     # unlabeled/no-name controls, empty headings
  2. Walk the product as a first-time visitor, on desktop and a phone-size viewport: land, find the primary action, use it, hit a wrong URL, look for how to reach a human. Note what fails before any tool says so.
  3. Select specialists:
FindingSpecialist
unclear primary action, dead-end pages, placeholders, fake controls, fake social proof, misleading claims (19, 23, 26)
content-trust
predictable questions unanswered where visitors decide, or an FAQ/help section is wanted (20)
faq-readiness
unknown URLs return 200, framework default 404, no recovery paths (21)
error-pages
broken nav/footer/CTA/content links, dead hrefs (22)
link-integrity
infinite spinners, blank empty states, swallowed API errors (24)
failure-resilience
no reachable contact, invented email, inconsistent contact details (25)
public-support
product name/branding inconsistent or starter branding left (supports 26)
launch-identity
footer legal links missing or pointing nowhere
legal-navigation
  1. 全面扫描一次（路径相对于此 skill 的文件夹；客户端渲染应用需使用 
    --render
    ）：
    bash
    node scripts/check-links.mjs  --url <site> --render     # 断链、无效 href、占位内容、mailto/tel
node scripts/audit-markup.mjs --url <site> --render     # 缺少标签或名称的控件、空标题
  2. 以首次访问者的方式体验产品，同时检查桌面端和手机尺寸视口：进入网站、寻找主要操作、执行该操作、访问错误 URL，并查找联系真人的方式。在任何工具报告问题之前，先记录实际遇到的失败。
  3. 选择专项技能：
发现的问题专项技能
主要操作不明确、死胡同页面、占位内容、虚假控件、虚假社会证明、误导性声明（19、23、26）
content-trust
在访客作出决定的关键环节，常见问题未得到解答，或需要 FAQ／帮助板块（20）
faq-readiness
未知 URL 返回 200、使用框架默认 404、缺少恢复路径（21）
error-pages
导航、页脚、CTA 或内容链接损坏，href 无效（22）
link-integrity
无限加载动画、空白空状态、被吞掉的 API 错误（24）
failure-resilience
无法联系到真人、虚构邮箱、联系信息不一致（25）
public-support
产品名称或品牌不一致，或仍保留初始品牌元素（支持检查项 26）
launch-identity
页脚缺少法律链接，或链接无有效目标
legal-navigation

Evidence discipline

证据规范

Label each claim OBSERVED, SOURCE-INDICATED, DECLARED, INFERRED, UNKNOWN, or REVIEW REQUIRED. UNKNOWN is never a pass and never a failure.
  • "Button exists" is not "button works": click it, or read its handler and say which you did.
  • A claim is not fake because you cannot verify it; it is UNVERIFIED and needs the owner's source. It is fake only when evidence shows it (identical "customers" copy from a template, counters that increment on a timer, logos of companies the owner has no relationship with, avatars from stock sets).
  • An unreachable external link may be a transient failure; do not call it broken without a 404/410.
将每项声明标记为 OBSERVED、SOURCE-INDICATED、DECLARED、INFERRED、UNKNOWN 或 REVIEW REQUIRED。UNKNOWN 既不能视为通过，也不能视为失败。
  • “按钮存在”不等于“按钮可用”：应实际点击按钮，或阅读其处理函数，并说明采用了哪种验证方式。
  • 无法核实某项声明，并不意味着它是虚假的；此时应标为 UNVERIFIED，并向所有者索取证据来源。只有证据表明存在虚假时，才能判定其为 fake，例如从模板复制的相同“客户”文案、按计时器递增的计数器、所有者与相关公司并无关系却展示其 logo，或使用素材库中的头像。
  • 无法访问的外部链接可能只是暂时性故障；在未出现 404/410 前，不要将其判定为断链。

May change

可更改

Broken internal links, dead hrefs with an obvious intended target, placeholder text that has an owner-supplied replacement, custom 404, loading/empty/error states, non-legal navigation. Per specialist limits.
按照各专项技能的限制，可修复损坏的内部链接、目标明确但无效的 href、所有者已提供替换内容的占位文本、自定义 404 页面、加载／空／错误状态，以及非法律类导航。

Must not claim

不得声称

"Trustworthy", "verified", "secure", or any badge/certification the owner has not earned. Never invent testimonials, customer logos, user counts, ratings, press mentions, awards, or "as seen in" strips. Never invent contact details. If proof is missing, remove the fake element or ask the owner for real proof.
不得声称网站“值得信任”“已验证”“安全”，也不得添加所有者未曾获得的任何徽章或认证。绝不编造用户评价、客户 logo、用户数量、评分、媒体报道、奖项，或“as seen in” 展示栏。绝不编造联系信息。如果缺少证明材料，应移除虚假元素，或向所有者索取真实证明。

Verify

验证

Repeat the first-visitor walk. Re-run 
check-links
: broken and dead-href counts for nav, footer, and CTAs must be zero or explained. Trigger a 404, a failed request, and an empty state and confirm each behaves sensibly.
再次执行首次访问者检查流程。重新运行 
check-links
：导航、页脚和 CTA 中的断链及无效 href 数量必须为零，或已给出合理解释。分别触发 404、失败请求和空状态，确认每种情况均表现合理。

Escalate

升级处理

  • Fake or unverifiable claims that are factual, financial, or health-related (revenue, guarantees, medical outcomes): REVIEW REQUIRED, and possibly a legal/advertising review. Remove or soften if the owner cannot support them.
  • Payment, auth, or signup CTAs that cannot be exercised here: UNVERIFIED with what would settle it.
  • 虚假或无法核实的声明涉及 事实、财务或健康（例如收入、保证或医疗结果）：标记为 REVIEW REQUIRED，并可能需要法律／广告审查。如果所有者无法提供支持，应移除或弱化相关声明。
  • 无法在此实际测试的支付、身份验证或注册 CTA：标记为 UNVERIFIED，并说明需要哪些证据才能确认。

No change is valid when

何时无需更改才是合理的

The product is a simple page whose one action works, there are no claims to substantiate, and the 404 and contact path are fine. Do not add an FAQ, trust strip, or extra CTAs to fill space.
如果产品只是一个简单页面，其唯一操作可以正常使用，没有需要佐证的声明，并且 404 页面和联系路径均正常，则无需更改。不要为了填充空间而添加 FAQ、信任展示栏或额外 CTA。