Skill

tooling-and-quality

Use when the task involves tsconfig strictness, linting, formatting, CI quality gates, testing posture, or broader TypeScript code quality governance.

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 clean-code and quality-governance 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

Tooling and Quality

Purpose

This bridge skill routes TypeScript work into the canonical clean-code and quality-governance lane.

Use it when the task is about:

tsconfig strictness or compiler posture as team policy

linting or formatting governance

CI quality gates and reproducibility

testing posture as governance rather than only local implementation

anti-pattern debt and staged hardening

deciding whether the real issue is toolchain, testing, runtime validation, or foundations drift

Reading Path

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

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

Read ../../references/clean-code/quality-gates-governance.md, ../../references/clean-code/toolchain-posture.md, and ../../references/clean-code/runtime-boundaries.md.

If testing or CI confidence is central, also read ../../references/clean-code/typescript-testing-strategy-and-type-boundaries.md.

If the problem is migration or recurring debt, also read ../../references/clean-code/typescript-anti-patterns-and-migration-ladders.md.

If the supposed tooling problem is really weak baseline type truth, route back to ../../references/foundations/INDEX.md.

Use ../../rules/tooling/INDEX.md only after the doctrine lane is clear.

Pressure Classification

Determine whether the problem is mainly about:

compiler or tsconfig posture

lint or format governance

CI or quality gates

testing infrastructure or proof posture

runtime-boundary support versus doctrine placement

migration or debt hardening

Output Contract

Return:

primary tooling or quality lane

key weakness or risk

strongest truth surface (tsc, lint, tests, CI, or doctrine)

one anti-pattern to avoid

the next exact doctrine file to read

Core Rule

A weak TypeScript toolchain silently trains weak architecture. Keep type safety, quality gates, testing posture, and runtime-boundary doctrine aligned instead of letting each surface drift into its own local habits.