Skill

type-level-programming

Use when the task involves conditional types, mapped types, template literal types, infer patterns, opaque or brand types, or advanced type-level composition.

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 advanced doctrine for information-preserving type-level programming.

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

Type-Level Programming

Purpose

This bridge skill routes TypeScript work into the advanced doctrine for information-preserving type-level programming.

Use it when the task is about:

conditional, mapped, or template-literal types

branded or opaque typing

advanced contract transformation

deciding whether a type-level construction is justified or merely clever

selecting the right advanced pattern under real pressure

Reading Path

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

Read ../../references/advanced/INDEX.md.

Read ../../references/advanced/type-level-programming-patterns.md.

If narrowing, branding, or overload choice is central, also read ../../references/advanced/typescript-narrowing-branding-and-inference-cookbook.md.

If the problem is really about trust boundaries or runtime data, also read ../../references/clean-code/INDEX.md.

Use ../../rules/types/INDEX.md only when exact doctrine routing is needed after the lane is clear.

Pressure Classification

Classify the advanced pressure first:

contract transformation

branded or semantic separation

template-literal protocol shaping

inference-preserving composition

complexity-budget question

Output Contract

Return:

primary advanced type-level pattern family

why it is justified here

what simpler pattern to reject first

one anti-pattern to avoid

the next exact doctrine file to read

Core Rule

Advanced TypeScript should clarify architecture and contracts, not hide them behind wizardry. If the pattern does not preserve meaningful truth, it is probably too expensive.