Use when the task involves trust boundaries, schema posture, parsing external input, IPC/config/storage validation, or deciding when TypeScript's compile-time guarantees are not enough.
How this skill is triggered — by the user, by Claude, or both
Slash command
/typescript-coding-engine:runtime-validationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This bridge skill routes TypeScript work into the canonical runtime-validation and boundary-truth doctrine.
This bridge skill routes TypeScript work into the canonical runtime-validation and boundary-truth doctrine.
Use it when the task is about:
../../SKILL.md for the engine boundary.../../references/clean-code/INDEX.md.../../references/clean-code/typescript-runtime-validation-decision-matrix.md.../../references/clean-code/runtime-boundaries.md.../../references/architecture/INDEX.md and ../../references/architecture/typescript-architecture-decision-trees.md.../../references/interop/INDEX.md.../../commands/route/choose-runtime-validation.md.Classify the boundary first:
Then name the dominant pressure:
Return:
TypeScript is compile-time power. Boundary trust still needs runtime discipline.
Do not turn every boundary into heavyweight schema theater. Do not let compile-time confidence pretend to be runtime proof. The right move is to validate exactly where trust changes, then let stronger internal types carry the rest.
npx claudepluginhub joysusy/violet-plugin-place --plugin typescript-coding-engineAudits codebases for validation libraries, maps trust boundaries, detects unvalidated inputs, and verifies type-runtime alignment for data contracts.
Validates all external data (HTTP, files, env vars, DB reads, queues) at process boundaries to reject malformed or malicious input before business logic runs.