
Claude Skills by VincentChuWaiChow
github.com/VincentChuWaiChowUse this skill to statically review MCP tool-contract fidelity in TypeScript servers against the 2026-07-28 specification revision: `inputSchema`/`outputSchema` fidelity against handler behavior, JSON Schema dialect correctness, `structuredContent` vs `content`, protocol-version negotiation and the `-32022` mismatch error, `server/discover`, and protocol vs tool-execution error classification. Reads tool definitions, handler source, and SDK/package metadata only; it never hosts or contacts a ...
Use this skill to statically review whether a TypeScript package resolves, imports, and emits correctly for every consumer mode it claims to support: the `module`/`moduleResolution` matrix, `exports`/`imports` condition ordering, `.mts`/`.cts` handling, and the dual-package hazard. Reads `package.json`, every `tsconfig.json`, and emitted output only; it never tunes bundler performance and never runs a build.
Use this skill to statically review whether TypeScript code runs on the stated target Node version and is type-checked somewhere before production: type-stripping limits, runtime-unsupported syntax, proof of a separate `tsc --noEmit` gate, `paths`-alias and import-extension requirements, and Node version/API gating. Reads source, the run command, CI configuration, and every `tsconfig.json` only; it never executes code and never assumes a Node version.
Use this skill to statically review npm package publication integrity: whether publish authority relies on OIDC-based trusted publishing rather than a long-lived token, whether the published artifact carries provenance a consumer can verify, whether the release-automation trust path resists compromise, whether the packed tarball and its declarations/source maps expose only what is intended, whether publish-time lifecycle scripts are justified, and whether registry/scope configuration resists ...
Use this skill to statically review a published TypeScript type surface: `.d.ts` correctness and emit strategy (`declaration`, `isolatedDeclarations`, rollups, API reports), public-versus-accidental exports, breaking-change classification and the semver decision, the consumer compilation matrix, and compile-time type-contract tests (`expectTypeOf`/`assertType` under `--typecheck`, `@ts-expect-error`). Reads declarations and configuration only; it never compiles, publishes, or runs the package.
Use this skill to statically review whether every value entering a TypeScript program from outside it — HTTP, queue, environment/configuration, database reads, third-party SDKs, webhooks, `JSON.parse`, files, and agent/tool calls — is parsed against a schema rather than asserted. Covers `unknown`-first ingestion, schema/type single-source-of-truth, generated-type drift, and validation error leakage. Reads source and sanitized configuration/schema files only; it never designs a validator in th...
Use this skill to statically review TypeScript static-enforcement policy: strict-family flag policy and silent loosening across a program graph (strict defaults true since TypeScript 6.0), per-package divergence, typed-lint rule selection and Project Service configuration, editor-versus-CI parity, `@ts-ignore`/`@ts-expect-error`/lint-disable suppression policy, lint-versus-typecheck duplication, and the typescript-eslint supported-version window. Reads configuration and lint config only; it n...
Use this skill to statically review whether a type-level abstraction in shared or published TypeScript code actually proves what its signature claims: generic variance, conditional and mapped type correctness, dishonest type predicates, unsound narrowing, `satisfies` versus annotation, branded/nominal modelling, and `unknown`-first discipline. Reads source and sanitized `tsconfig.json` only; it never reviews a frontend application diff and never compiles or runs code.
Use this skill when guarding Velero backup schedule changes, restore operations, BackupStorageLocation mutations, or volume snapshot configuration. Trigger on any request to run a velero restore, delete a Schedule, change a BSL default, or modify backup retention.
Use this skill for a specific cloud workflow. Mention provider, trigger phrases, expected inputs, and when not to use it.