Skill

core-types

Use when the task needs TypeScript foundations: strict typing, widening vs narrowing, baseline type-system behavior, or first-line mental models.

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 foundations lane.

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

Core Types

Purpose

This bridge skill routes TypeScript work into the canonical foundations lane.

Use it when the task is about:

strictness posture

baseline inference and narrowing

widening loss

first-line type correctness

deciding whether the problem is foundational before escalating into advanced or runtime-boundary doctrine

Reading Path

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

Read ../../references/foundations/INDEX.md.

Read ../../references/foundations/strict-type-system-posture.md.

If the problem is a concrete type failure, also read ../../references/foundations/typescript-type-error-diagnosis-and-recovery.md.

If the issue looks trust-boundary driven, also read ../../references/clean-code/typescript-runtime-validation-decision-matrix.md.

If the issue clearly exceeds baseline strictness and inference, route upward into ../../references/advanced/INDEX.md.

Pressure Classification

Classify the problem first:

strictness or compiler posture

widening or narrowing baseline

inference loss at ordinary API boundaries

foundational type-error diagnosis

trust-boundary leak masquerading as a type issue

Output Contract

Return:

primary foundational class

why it belongs in foundations first

whether the issue should stay in foundations or escalate into advanced or clean-code

one anti-pattern to avoid

the next exact doctrine file to read

Core Rule

Prefer foundational type reasoning over ad-hoc assertions. If the problem can be explained by weak baseline truth, fix that before reaching for advanced machinery.

Core Types

Purpose

This bridge skill routes TypeScript work into the canonical foundations lane.

Use it when the task is about:

strictness posture
baseline inference and narrowing
widening loss
first-line type correctness
deciding whether the problem is foundational before escalating into advanced or runtime-boundary doctrine

Reading Path

Read ../../SKILL.md for the engine boundary.
Read ../../references/foundations/INDEX.md.
Read ../../references/foundations/strict-type-system-posture.md.
If the problem is a concrete type failure, also read ../../references/foundations/typescript-type-error-diagnosis-and-recovery.md.
If the issue looks trust-boundary driven, also read ../../references/clean-code/typescript-runtime-validation-decision-matrix.md.
If the issue clearly exceeds baseline strictness and inference, route upward into ../../references/advanced/INDEX.md.

Pressure Classification

Classify the problem first:

strictness or compiler posture
widening or narrowing baseline
inference loss at ordinary API boundaries
foundational type-error diagnosis
trust-boundary leak masquerading as a type issue

Output Contract

Return:

primary foundational class
why it belongs in foundations first
whether the issue should stay in foundations or escalate into advanced or clean-code
one anti-pattern to avoid
the next exact doctrine file to read

Core Rule

Prefer foundational type reasoning over ad-hoc assertions. If the problem can be explained by weak baseline truth, fix that before reaching for advanced machinery.