菜单
Build and smoke-test the @parity/truapi TypeScript package (tsc + bun test). Use after regenerating the client or after touching js/packages/truapi/.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Boot the local TrUAPI dev stack (dotli host + playground) in a tmux `servers` window so the playground can be tested in a real browser. Auto-trigger on "run the playground locally", "test locally", "let me try it", "open the playground locally", "boot the stack", or any equivalent phrasing in this repo.
Write an RFC document based on user-provided notes and context. Use when the user wants to create, draft, or write an RFC.
Regenerate the @parity/truapi TypeScript client and playground metadata from the truapi crate's rustdoc JSON. Use whenever the Rust trait surface changes.
The full local end-to-end checklist before declaring a TrUAPI change done. Chains the layered skills in order. Invoke when the user says "is this ready", "definition of done", or asks to verify a Rust→codegen→TS→playground change end-to-end.
Run the playground end-to-end inside the dotli host iframe, either via the automated Playwright suite or by driving it manually in a browser. Use to verify the wire protocol after Rust/codegen/transport changes.
Static verification of the playground (Next.js build + ESLint). Use after changing playground/ sources or after refreshing the @parity/truapi snapshot.
| name | ts-client-checks |
| description | Build and smoke-test the @parity/truapi TypeScript package (tsc + bun test). Use after regenerating the client or after touching js/packages/truapi/. |
@parity/truapi build + smoke testsMirrors step 3 of docs/local-e2e-testing.md.
cd js/packages/truapi
npm run build
npm test
npm test runs the bun test suite
(src/**/*.test.ts) directly against the source .ts files (no build step
required), so bun must be installed.
Expected:
tsc (the build step) exits cleanly with no diagnostics.bun test reports N pass / 0 fail across the src/**/*.test.ts files.src/wire-table.test.ts emits one round-trips <method>.<kind> case per
generated frame id. The case count tracks WIRE_TABLE: adding a method
grows it by 2 (request + response) or 4 (subscribe).tsc errors here usually mean codegen was skipped or out of sync.
Re-run the regen-codegen skill, then retry.src/wire-equality.test.ts failure (golden hex mismatch) is a
wire-breaking change. That is a protocol decision, not a regression to
"fix" by tweaking the test.src/wire-table.test.ts count drop means a versioned wrapper variant is
missing, not extra. V0.2-only methods (e.g. host_get_user_id,
host_chat_create_simple_group, all EntropyDerivation, all
Payment) intentionally lack a V1 variant.