typescript-coding-engine

Route TypeScript tasks into doctrine lanes covering types, validation, architecture, and interop.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/joySUSY/violet-plugin-place --skill typescript-coding-engine-joysusy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typescript-coding-engine
Source: https://github.com/joySUSY/violet-plugin-place/tree/main/plugins/typescript-coding-engine
Command: npx skills add https://github.com/joySUSY/violet-plugin-place --skill typescript-coding-engine-joysusy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? TypeScript work often drifts between scattered advice, donor repositories, and ad-hoc fixes, making it hard to apply consistent strictness, runtime validation, and architecture decisions. This Skill provides a governed doctrine tree and routing system that classifies each TypeScript task by its real pressure and directs you to the correct canonical guidance. ## Core Features & Use Cases - Doctrine Lane Routing: Classifies tasks into foundations, advanced typing, clean-code/runtime, architecture, or interop lanes via a pressure router and reference indexes. - Runtime Shell Surfaces: Provides bridge skills, prime/check/route commands, bounded specialist agents (type diagnostician, architecture reviewer, tooling auditor, interop reviewer), and conservative lifecycle hooks. - Governance Controls: Inventory, absorption matrix, trigger scope, and source-reservoir map keep donor material separate from canonical doctrine. - Use Case: When facing a confusing type error, a runtime validation choice, or a Rust↔TypeScript contract boundary, activate this engine to route to the correct doctrine page, command, or specialist agent instead of guessing. ## Quick Start Ask the assistant to diagnose a TypeScript type error or choose a runtime validation approach, and it will route the task through the appropriate doctrine lane.

Frequently Asked Questions about typescript-coding-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a TypeScript type error systematically?▼

Type error diagnosis starts in the foundations lane, which treats errors as information-flow problems rather than syntax failures. Use the check/types command or the type-diagnostician agent for bounded analysis of complex failures.

How do I choose a runtime validation approach for TypeScript?▼

Runtime validation selection is a routing problem handled by the choose-runtime-validation command and the runtime-validation decision matrix in the clean-code lane. The choice depends on where your trust boundaries sit, not on library popularity.

Does this engine handle Rust and TypeScript interop with Tauri?▼

Yes, the interop lane covers Rust↔TypeScript contract boundaries, Tauri IPC bridges, and WASM boundaries. It enforces ownership rules: Rust owns structural truth when it generates contracts, while TypeScript owns consumer ergonomics and local validation.

What is the difference between the references tree and the modules directory?▼

The references tree is the canonical doctrine and the default reading path. The modules directory holds staged complexity that is too large or donor-shaped to flatten yet, and it must never become the default reading path.

When should I use the specialist agents instead of reading doctrine?▼

Use agents only for bounded specialist reasoning such as complex type diagnosis, architecture review, tooling audits, or interop review. Ordinary conceptual questions should be answered by doctrine pages first, keeping agents from becoming default responders.