Skill

runtime-validation

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.

Install

npx claudepluginhub joysusy/violet-plugin-place --plugin typescript-coding-engine

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This bridge skill routes TypeScript work into the canonical runtime-validation and boundary-truth doctrine.

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

MCP Integration

6 files

Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.

plugin-dev

83.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

Runtime Validation

Purpose

This bridge skill routes TypeScript work into the canonical runtime-validation and boundary-truth doctrine.

Use it when the task is about:

external input or payload trust

config, env, form, API, storage, or IPC validation

deciding whether compile-time types are sufficient

schema or validator choice pressure

clarifying whether the issue is really runtime validation, architecture, or interop

Reading Path

Read ../../SKILL.md for the engine boundary.

Read ../../references/clean-code/INDEX.md.

Read ../../references/clean-code/typescript-runtime-validation-decision-matrix.md.

Read ../../references/clean-code/runtime-boundaries.md.

If the boundary affects system shape, also read ../../references/architecture/INDEX.md and ../../references/architecture/typescript-architecture-decision-trees.md.

If the boundary is Rust/Tauri/WASM-facing, also read ../../references/interop/INDEX.md.

If posture is still unclear, use ../../commands/route/choose-runtime-validation.md.

Pressure Classification

Classify the boundary first:

API or webhook input

form or user input

config or env loading

storage or rehydration

IPC or cross-language payload

generated/shared contract with remaining runtime trust risk

Then name the dominant pressure:

trust establishment

schema ownership

runtime error shape

architectural boundary placement

interop boundary coordination

Output Contract

Return:

primary validation posture

why it fits

whether the issue is architectural, operational, or interop-driven

what anti-pattern to avoid

the next exact doctrine file to read or runtime surface to use

Core Rule

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.