test-development
Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- test-development
- description
- Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.
02 资源文件 3
- 参考文档displayed-types.md593 B
- 参考文档runtime.md617 B
- 参考文档types.md1.1 KB
03 SKILL.md 正文
Choose branches from the task's acceptance criteria before editing:
- Runtime behavior: The intended result is observable when code executes. Read runtime.md.
- Compiler behavior: The intended result is TypeScript accepting, rejecting, or inferring a consumer expression in a particular way. Read types.md.
An exported signature alone is validated by pnpm check; it enters the compiler
branch only when its inference, assignability, rejection, overload selection, or
displayed type is part of the task. Some changes require both branches because
they independently change runtime and compiler behavior.
The task is complete when each intended behavior in scope has the relevant focused coverage, targeted tests pass, and applicable root checks pass or are reported as not runnable.
04 同仓库更多 Skills
vendored-assets
Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.
pull-requests
Pull request finalization. Use when a change works and is about to be opened as a pull request, or when updating or continuing an existing one.
performance-analysis
Performance analysis. Use for runtime throughput or latency benchmarks, TypeScript compiler cost, performance regressions, comparison harnesses, or thresholds.
package-development
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
migration-guidance
Use when changing how a v3 public API maps to v4, editing migration annotations, or regenerating migration/v3-to-v4.md.
jsdocs
Public API JSDoc. Use when authoring or reviewing Effect API documentation, refining a module's documentation, or fixing documentation related diagnostics.