shipping-artifacts
补齐 AI 写码后缺失的架构、权限与测试覆盖记录，便于人工或自动审查。
为 AI 生成应用提供一套可审计的核心交付文档模板与清单。
把 AI 生成的应用变成可审计的交付文档集：画架构图、梳理用户/权限流程、列出 secrets/变量并给出测试覆盖地图。用于代码交接、梳理信任边界或准备安全/性能审计时。只提供核心必需文档，按需再补邮件、定时任务、SEO 等，方便审阅者快速判断是否能放心上线。
▸ 展开 SKILL.md 英文原文
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
帮我安装这个 skill：https://raw.githubusercontent.com/phuryn/pm-skills/main/pm-ai-shipping/skills/shipping-artifacts/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/phuryn/pm-skills/main/pm-ai-shipping/skills/shipping-artifacts/SKILL.md"# Shipping Artifacts: The Docs That Make AI-Built Code Reviewable ## Purpose AI agents write code fast, but they leave no durable record of *intent* — what the system is supposed to do, who is allowed to do what, where the secrets live, which rules are actually verified. Without that record, no human (and no auditing agent) can tell whether the code is safe to ship. This skill defines the small set of documents that restore reviewability. These docs live in `documentation/` at the repo root and are written for two readers: a human reviewer and the next AI coding agent. They are the **intended-state** half of every later audit — a security or performance review is only as good as the inten