Menu
Use when retikz release-candidate work needs API-freeze enforcement, bug convergence, docs completion, migration guidance, packaging validation, or rc/stable readiness checks.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when changing any retikz apps/docs content, route data, i18n, demo, SourceLinks, or schema reference before loading the matching page-type skill.
Use when retikz needs multiple independent LLMs to review the same fixed code, ADR, implementation plan, test contract, commit, or working-tree snapshot before a gate or delivery decision.
Use when an Alpha ADR needs a pre-implementation capability gate, or a Beta milestone needs code-based completeness and package-boundary auditing.
Use when planning a retikz architecture direction, version roadmap, or alpha feature that may need a long-lived ADR before implementation.
Use when retikz work is primarily refactoring, reorganization, renaming cleanup, modularization, or internal simplification and should start from a reviewed implementation plan before code changes.
Use when retikz implementation, adversarial testing, and docs are complete, and an ADR or beta TODO needs changelog, contract consistency review, roadmap status updates, or final human acknowledgement.
| name | flow-rc |
| description | Use when retikz release-candidate work needs API-freeze enforcement, bug convergence, docs completion, migration guidance, packaging validation, or rc/stable readiness checks. |
rc 是公开 API 冻结后的验收窗口。目标是让外部用户能从 npm 安装、按文档写图，并预期后续 patch 不破坏现有代码。
package-publish；发布前 package.json 目标版本必须已进入 HEAD。调用前确认：
0.x.y-rc.N，npm dist-tag 为 next。若用户要求“再改 API 名 / 换 schema 字段 / 加 prop”，立即 halt，并建议登记到后续 alpha / beta 窗口。
| Level | 范围 | 允许程度 | 验证 |
|---|---|---|---|
| docs | apps/docs/**、导航、i18n、demo、changelog、迁移指南 | 主路径 | docs typecheck / build + 页面确认 |
| bugfix | 不改变公开契约的 core / react / plot bug 修复 | 允许 | 回归测试 + lint / tsc / test |
| packaging | metadata、exports、tarball、安装 smoke | 允许 | build + dry-run + 外部安装验证 |
| compat-risk | 可观察行为调整但声称兼容 | 谨慎，需人工裁定 | 回归测试 + changelog / 用户影响说明 |
| breaking | 公开 API / IR schema / 组件名 / prop 名 / export 变化 | 禁止 | halt |
| feature | 新公开能力 / 新 schema 字段 / 新 DSL 行为 | 禁止 | halt |
git status --short，识别已有改动归属，不覆盖用户改动。当前发布组路径以 package.json 为准。kernel 组在 packages/kernel/{math,core,render,vanilla,react,tex}；plot 组在 packages/viz/{plot,plot-vanilla,plot-react}。
docs-doc-principle，按页型再读 component / example / group / concept / blog skill。zh 是 source of truth，en 同步。默认验证受影响模块；RC 发布候选、跨包契约或用户要求时扩大到发布组 / 全仓。
普通结构化改动：
pnpm --filter @retikz/<pkg> exec eslint . --fix
pnpm --filter @retikz/<pkg> exec tsc --noEmit
pnpm --filter @retikz/<pkg> exec vitest run
docs 改动：
pnpm --filter @retikz/docs exec tsc --noEmit
pnpm --filter @retikz/docs build
packaging / rc 发布候选：
pnpm --filter @retikz/<pkg> publish --dry-run --no-git-checks --access public --tag next --registry https://registry.npmjs.org/rg --files packages | rg "packages/.*/src/.*\.(d\.ts|d\.ts\.map|js)$"汇报：
需要 commit 时，按逻辑块 stage，展示文件清单和建议 commit message，等待授权。
只有用户明确要求“发布 rc / publish rc / 发版”时才进入，细节走 package-publish。本 skill 只补 rc 约束：
0.x.y-rc.N。next。v0.x.y-rc.N；plot 组按发布 skill 的 tag 规则。发布成功并完成 npm registry 反查后、宣布 RC 完成前，必须检测当前工作区构建出的文档站：
node .agents/skills/docs-doc-principle/scripts/check-doc-integrity.mjs
pnpm --filter @retikz/docs exec tsc --noEmit
pnpm --filter @retikz/docs build
pnpm --filter @retikz/docs preview
ComponentPreview 已挂载，页面和浏览器 console 均无错误。页面渲染异常、Demo ... not found、Failed to compute IR、Unknown schema、Runtime / React 未捕获错误。Layout、Node、Path、Step、Draw、Text、Coordinate。单条任务：
rc 阶段整体：
next 包可在独立项目安装并运行。flow-beta 完成并发布 beta 后进入。package-publish 发布 stable；正式版不带预发布 dist-tag，默认 latest。